Since the resurrection bug returned to Ne_Ruins for some reason, I guess I will test all the addons again which I had reported in the past to see what happened to them. I know that the "view warping" bug at the end of Malice had never been fully addressed, too.
Malice And Ne_Ruins
Ok, my first check with latest DX9 build revealed that Malice and Altar of Storms are still not running flawlessly.
1) In "Showdown!" (d15), the FOV warping issue during the boss fight is still there and occurs when saving and loading after being pulled towards the boss at least once. It can be kinda fixed if you get hit by the same attack again afterwards, but that isn't a satisfying solution, ofc.
2) During the boss fight I had a random crash to console with the message "Host_Error: SOLID_BSP with a non bsp model", but couldn't reproduce it.
3) Statusbar remains active during cutscenes (not so severe)
1) Requires -heapsize 512000 on startup (crash when leaving start map otherwise). This shouldn't be necessary in a modern port IMHO.
2) Winged succubus resurrection crash (incorrect handling of entities with alpha=0) is definitely back, as annoying as ever.
3) "impulse12" crash when switching between Super Shotgun and Quad Super Shotgun with MWHEELDOWN is also definitely back. I see that the game uses two variables for this, sv_gameplayfix_no_impulse12_override (set to "1") and sv_gameplayfix_no_impulse12_exceptions ("ne_ruins"). If you change the first one to 0, the crash does not happen any more, but this is just a workaround and needs to be addressed.
Xmas Jam 2018
"Chapel Perilous" (xmasjam2018_sham) crashes when exiting the level since it expects Start.map (capital S) instead of start.map. This is something that can be fixed by changing the map, but maybe Mark V should be more tolerant with such things, unless there's a good reason for it being the way it is.
Later on, I will take a look at the problems I had reported for Nehahra, Rapture, RRP, Shrak and Soul of Evil again to see if any other fixed problem returned.
WinQuake Version Crashes On Launch
Whenever I launch the WinQuake version, it immediately crashes and the qconsole log doesn't tell me anything important. I've even removed the config files and the engine still crashes. Any idea what's going on?
Good news: No other addon that I had previously tested for Mark V shows any of the bugs that were addressed. Thank God.
Bad news: Malice and Ne_Ruins. See above.
Hardcoded ALT-M Mute
I'd be delighted if there weren't hardcoded binds. This is currently messing up my gaming overlay/recording software binds that I have gotten very used to.
No Music On Mark V Linux?
I tried to load mp3 music on Fitzquake Mark V on Linux but it doesn't seem to load at all. I put them on the music folder and named the tracks appropriately. I also tried to use the external_music command on console but such a command doesn't exist at all. How can I have music on Fitzquake on Linux? Quakespasm has it, why doesn't Fitzquake Mark V?
Should I switch FTEQW or are you coming back to Mark V eventually?
When Baker Says He Is On A Break
Then he is on a break. It's not his first time off. There's still unfinished business before 2.0 and I am sure he'll get back to it.
I'm aware of his time off. I was under the impression he worked on Mark V during the winter months. Fingers crossed.
i've tried the hd textures, they work fine but skies remains the same. how do i enable hd skies?
you mean skyboxes?
no standard skies, in the hd pack linked in this thread all textures work except for skies.
AFAIK MarkV doesn't support replacement of the standard skies.
How is that true? Fourth line down in the original post states:
"* Full external texture support, DP naming convention"!
ummm so yeah... I couldn't get it to load my custom sky1.tga(jpg) replacement. Odd that is.
Skies in Quake are not regular textures.
Big Maps Related Performance
I'm having issues with fps on big maps like 1st and 3rd maps of "Unforgiven". FPS drops to 20 and there are delays in mouse work like i press "fire" button - it fires 2 seconds after and keeps firing when i unpressed the button. Tried to run these maps with default config and there is no change in the situation. Meantime DirectQ 1.9.2 runs these maps flawlesly (97-100 fps). Also checked different graphic setup. No result.
Windows XP Pro 32bit
Intel Core 2 Duo 1.86 GHZ
Nvidia GeForce 250 GTS 1024MB
RAM 3 GB
Big Maps Related Performance #2
Utilized Mark V v1.99 DirectX.
Even bigger problems with fps occur at Rubicon Rumbke Pack. Same mouse delays , fps down to 20-30 in some areas.
External HD Skies
External scrolling sky textures are usually comprised of two images, not one:
sky1_trans.tga (transparent overlay)
sky1_solid.tga (opaque underlay)
There are another two possible suffixes in some engines, but I don't remember the name.
MarkV Direct3D is not the same as DirectQ, and you shouldn't expect the same performance.
To be specific: the reason DirectQ gets good performance is not Direct3D. It's batching, vertex buffers, multitexturing, shaders, etc, and this is all stuff that can be done in OpenGL too, if the engine author is willing to do so.
In the case of MarkV, Baker is not willing to do this. So in order to run in Direct3D, it needs to store out vertex data per frame, then try to mangle unoptimized OpenGL calls into something that works in Direct3D. You shouldn't be surprised if it doesn't always work well.
If you want an engine that has good performance in big maps by using the right kind of code, MarkV is not that engine. Use QuakeSpasm instead.
Speaking of which, any chance QuakeSpasm will ever support Nehahra?
Quakespasm is not in active development ATM. So there's that little issue.
True, but FWIW folks shouldn't read that as "dead project". Updates were still landing in the codebase through the end of 2018. So nothing going at the moment, but Quakespasm development seems to come in spurts.
Dunno if those developers have ever commented on the likelihood of Nehahra support though.
If You Keep Accusing
Poor Baker of inefficient coding, he might never return, man. :P We need him!
Someone said somewhere that Nehahra is too much of an oddball to support properly. Too bad for me, haven't played it yet and Mark V doesn't run well on my system.