#1661 posted by mh on 2017/06/26 18:09:40
The main engine-breaker in Sepulcher appears to be the leafs count; this is used for several hard-coded arrays in the engine and even the extended max in Fitz or earlier versions of QuakeSpasm is insufficient for Sepulcher, which needs 73755 leafs.
Personally I think that engines should be dynamically allocating these instead of using big static arrays, because otherwise it's an arms race: an engine will bump the max, a map will overflow it, an engine bumps it again and so on.
Anyway, the latest MarkV bumped MAX_MAP_LEAFS to 65535 for the Rubicon Rumble Pack, so it too is insufficient to run Sepulcher.
Other Ad_sepulcher Limits
#1662 posted by ericw on 2017/06/26 18:44:06
1375 models
368 sounds
193 lightmaps (assuming 128x128)
2877 static ents
4743 efrags
For QS I made efrags dynamic, and was going to do the same with static ents (although 3k is about the upper limit with protocol 666 because of 64k signon)
Sky Visible Through Water
#1663 posted by sakamoto on 2017/08/03 12:39:09
Very nice engine. Just one thing. When you set the water to be opaque like the original, the sky is partly visible through it in the hardware renderer. But not in the software renderer. This seems to be the only noticeable discrepancy between the two, apart from affine mapping not being possible in hardware either. How hard would it be to fix this?
@sakamoto
#1664 posted by Baker on 2017/08/03 16:51:56
Here is me on E1M2 looking at the sky with opaque water using the hardware renderer. The sky isn't partly visible.
Hardware renderer, opaque water, looking at sky -- none seen
Maybe a screenshot of what you are referring to would help?
#1665 posted by Gunter on 2017/08/17 07:15:43
I believe he's referring to the same issue some of us have reported before: shadows and the sky are visible through models (and water surfaces it seems) in the DX9 version. (see #1098 #1206 -- mh knows about it: #1109 ).
I jumped in the pool on e2m1 and saw the effect he's describing.
#1666 posted by Zaratul on 2017/08/22 23:14:46
Hello i have problem with Dissolution of Eternity HUD.
https://www.quaddicted.com/forum/viewtopic.php?id=421
"The armour / ammo icons displayed do not match the actual armour or weapon you have equipped."
This person has the same problem,he is using a PSP port,im using a Mark V.Is the problem on my side or Mark V? How do i fix this?
#1667 posted by Joel B on 2017/08/23 15:47:23
What command line are you using to launch it?
#1668 posted by Baker on 2017/08/25 09:28:29
Using -hipnotic the command line? Yes/No?
Probably your problem. Let me know.
@gunter - ok, r_shadows 3 option. Maybe a week later after his post I realized that was likely the issue he was experiencing.
#1669 posted by Baker on 2017/08/25 09:29:30
I meant -rogue, not -hipnotic.
:(
No More Vsync In Mark V WinQuake?
#1670 posted by jayoo on 2017/08/26 16:26:14
WinQuake runs with constant stutter but I couldn't find any way to turn on vsync. Can anyone help?
#1671 posted by Baker on 2017/08/26 21:15:52
I don't know of any WinQuake that ever vsync since that is a Open GL feature.
That being said, if you really want a WinQuake with vsync ... here is a slightly older beta with vid_vsync 0|1 capability:
http://quakeone.com/markv/builds/1025_mark_v_beta.zip
It is the WinQuake-GL.exe in that .zip that has vid_vsync because it renders the buffer to an texture and then draws it on the screen through Open GL.
#1672 posted by jayoo on 2017/08/27 09:53:05
Thanks Baker, I found that build last night and it's fantastic for playing Quake as authentically as possible.
Is there a reason why this .exe is no longer included or being worked on? It's really the best of both the GL and software modes, since it has no graphic glitches and z-fighting like the GL version, while retaining it's best features such as UI scaling and vsync.
It just makes no sense to me at all.
#1673 posted by Baker on 2017/08/27 10:32:16
The regular WinQuake can hit higher frames per second, doesn't matter much for small resolutions but if someone decides to max out in a very large resolution there is a gap.
It is actually maintained because the Linux and Mac versions of Mark V WinQuake are WinQuake-GL builds, I just don't put a Windows one in the Windows .zip because it would confuse most people.
#1674 posted by jayoo on 2017/08/27 13:42:07
Are you planning to put WinQuake_GL.exe's in future builds?
#1675 posted by Baker on 2017/08/27 14:03:58
I could make it available somewhere on the page in the future when new releases happen.
#1676 posted by jayoo on 2017/08/27 14:48:16
Also, there have been two longstanding bugs to do with monster spawns that have been around since the original WinQuake - one in e3m3 where the fiend spawns midway in the air in the circular lava room when the final bridge activates and another in e4m7 where the zombies spawn after killing all the underwater zombies in the first circular room. In both cases the monsters are stuck in the air after spawning when they should fall to the ground/water and start attacking. Could you look into fixing these issues?
@jayoo
#1677 posted by mh on 2017/08/27 18:35:51
Are you sure that these are engine and not QC bugs? My recollection is that they happen in all engines, not just WinQuake. If QC bugs it would be inappropriate to modify this behaviour in the engine.
#1678 posted by jayoo on 2017/08/27 18:57:09
There's definitely source ports out there that fix these issues, but I admit that most I've seen don't.
Why would it be inappropriate to modify this behaviour in the engine? They are gameplay bugs after all so shouldn't they be fixed?
Compaibility
#1679 posted by Preach on 2017/08/27 21:38:52
If the bug is due to bad QC code or mapping errors, then changing the behaviour of the engine to work around the bug does carry a risk: some mods may be using this behaviour of the engine intentionally to create a desirable effect. The fix for the bug in vanilla will break those mods in your engine. Which isn't to say that it's never the right choice to make those kinds of change, but you have to be thinking about the potential cost as well.
@jayoo
#1680 posted by Baker on 2017/08/27 22:03:50
QuakeC is game logic in a progs.dat, found in Quake pak0.pak. It exists outside the engine and is the game logic program. It can be compiled with a QuakeC compiler like fteqcc.
Some people (like preach) are really into QuakeC, he is the main author of Quoth and was involved in Arcane Dimensions.
Concise version: QuakeC behavior isn't related to the engine.
#1676
#1681 posted by mankrip on 2017/08/27 23:18:22
Quake Info Pool - Currently not researched Quake bugs
"Right in the beginning on E4M7 some Zombies start spawning after you kill the ones in the water. If you stay under water as you kill them, the new ones will spawn above you, and fall down into the water. However, if you kill the ones already there under water, and get back up on the ground level, the Zombies will spawn in the ceiling, and just hang there."
Reported by Alexander "Prodigy" Møller
Demo is available for download (e4m7zombie.zip)
QIP lives!
#1682 posted by mankrip on 2017/08/27 23:20:59
I bet it's a bug in the map itself. Some trigger misfiring or something.
@mankrip
#1683 posted by Baker on 2017/08/28 00:15:23
#1684 posted by Gunter on 2017/08/29 01:41:25
The zombies' teleport entry points in e4m7 are just too close to the ceiling.
But if you have an online server with a sys_ticrate of 0.1 then they fall just fine, because the server doesn't check their position fast enough to know they are stuck before they fall far enough to not be stuck. sys_ticrate .05 or faster and they get hung up.
It can be fixed directly in the map or with QuakeC by altering the locations of the teleport points.
#1685 posted by Baker on 2017/08/29 04:05:29
Sounds like a mapper or advanced user could make an external .ent file if that is what is going on.
|