Ah yes, that pesky driver update that failed on three different occasions is fucking me in the ass, thanks for the insight...
Hm. Baker... I found something you did and I don't like it :D
I was re-assigning some buttons so now I can use ALT to +attack (I was using the button on my trackpad with my thumb to +attack, but I've found it's less of a stretch -- physically -- to just hit the ALT key with my thumb instead).
So then I hit ALT + M to do a certain key combo that I occasionally use, and the console starts spitting this out at me:
Mute: ON --- ALT-M to Toggle
Mute: OFF --- ALT-M to Toggle
Sure enough, ALT + M puts Quake on Mute....
But I don't want that!
If you want a Mute feature, just make it a console command: "mute" and we can assign it to whatever key we choose.
As it is now, it's interfering with a key combo that I want to do something else....
Ya know, while I'm talking about ALT key combos, I remember suggesting in the past to allow key combos to be bound, so if I actually wanted ALT + M to do MUTE (if MUTE were a console command) I could do it like:
Bind @m mute
(if you made @ designate the ALT key combination)
Ah, on the Old Page #1352 I was thinking about "shift" keys for gamepad binding, but it could also work for keyboards. I suggested allowing any key to be designated at the "shifting" key for combinations....
Do any other Quake engines allow fancy binding of key combos?
Anyway, key combo binding is a "possible wishlist" kind of thing.
Whereas ALT+M = MUTE is a "NOOOOOOOOOOOO!!!" kind of thing :D
And probably a "Only Gunter would discover that undocumented feature and take issue with it" kind of thing ;)
Do any other Quake engines allow fancy binding of key combos?
FTE allows you to bind alt+m "echo ALT+M was pressed"
(ctrl+alt+shift modifiers and variations thereof are supported. Note that if you use a key as a modifier then you should probably not bind it to something else at the same time - it'll work, you'll just get unwanted binds.)
A workaround for DP would be to write some csqc that looks for modifier keys and then reconfigures DP's bindmaps, which isn't user friendly for multiple reasons.
Yes, confirmed that MarkV has Alt-M hard-coded to toggling mute on/off.
Other hard-coded key combos:
Alt-Enter: switch between fullscreen and windows.
Alt-Tab: switch between different applications on the OS.
That FTE functionality wold be something really (really) good to import.
I hadn't thought about those other hard-coded combos, since they are standardized Windows behaviors.... so they behave as most people would already expect.
I suppose you don't need to have CTRL+C and CTRL+V function when the console isn't down though. Those would be the only other combos I would think that might potentially interfere with something someone might bind. Few people are going to mess with the TAB or ENTER key, since they already have commonly-used functions in Quake (scoreboard and entering messages or menu navigation).
On the subject of Mute, if I use my media keys on my keyboard to change system volume or mute, it causes a little display window to pop up on screen notifying me of whatever I changed, and that causes Quake to minimize. I wonder if there's a way for Quake to ... not be forced to minimize in this situation....
Huh, well, I'm testing it again today and my media keys aren't forcing Quake to minimize.... Well, not consistently. The first time I tried it, Quake minimized but then it restored itself. After that (even after closing and restarting Quake) it doesn't minimize at all, and the overlay flickers in front or Quake for a moment.
So I don't know. It's inconsistent. Probably a Windows thing.
On the subject of Copy/Paste, I guess even if the console isn't down, you'd want CTRL+V to function if someone was entering a chat message too.
I have often wanted to Copy test from the console, but you can only select text from the line you are currently typing on (by using shift + left/right), but that's never what I want to do. There should be some way to select text that has already been printed in the console, either with mouse select or by pressing shift+up to select previous console lines.
I end up having to use the "copy" command, which copies the entire console contents.
How To Build On Linux Myself?
Source code only contains project files for building on Windows. No makefile, cmake, etc.
There's a project file for codeblocks.
In Futute Versions
Would there be a way to have more that just three cycling autodemos? I test a lot of maps for newbs and like to use Mark V's cl_autodemo. But much of the time I die a lot! Which obv overwrites the dems.
I know I asked for the map name to be added before, I figured heck why not ask for this too.
Weapon Animation Interpolation
Animations of Weapons and Super nailgun in particular still look choppy when firing, though these cvars are enabled :
How to make 'em smooth like in DirectQ, for instance?
Animations of Weapons and Super nailgun in particular still look choppy when firing ... How to make 'em smooth like in DirectQ, for instance?
This is a content issue.
FitzQuake (which both Quakespasm and MArkV are derived from) works around it in one way, DirectQ works around it in a different way, and both ways have their pros, cons and trade-offs.
First of all, the issue.
The Quake weapon models have polygons for the muzzle flash animation embedded in them, and when the gun fires the flash polygons are moved into the correct position.
When interpolation is switched on, what this causes is for these polygons to move with interpolation, which causes them to swim into view, and dance back-and-forth across the space between the nailgun barrels.
FitzQuake and derivatives work around this by temporarily switching off interpolation if the gun is in a muzzle flash state.
DirectQ works around it by measuring the delta between vertices in the two frames to be interpolated, and if the delta is sufficiently large (above some arbitrary value that was tweaked until it gave the correct result) assume a muzzle flash motion and don't lerp, on a per-vertex basis.
DirectQ used vertex shaders for everything so it could do this quickly and easily, and it really wasn't much more than an extension of the same kind of thinking as the "assume a teleport and don't lerp" check elsewhere in the engine. It should be obvious that this approach is vulnerable to both false positives and false negatives, however.
The correct way to fix this is new content. A set of weapon models that don't include the flash polygons, a separate generic muzzle-flash model, and the QC code to stitch them together.
Meanwhile, FitzQuake allowed disabling it's behaviour by setting r_lerpmodels to 2 - not sure if MarkV and QS do likewise.
Big thanks for an explanation MH !
"r_lerpmodels 2" works just as intended in Mark V either :)
I've actually wanted to ask you a DirectQ related question since 2013 but was unable to contact you.
You've probably been informed about "sinking into ground" bug that occurs after about an hour of playing in DirectQ. Most of the corpses around the map blow up and the player starts sinking into ground. The only way to solve an issue (temporarily) was to save a game, restart the engine and load it again. I've wondered since then, has there ever been a solution found for eleminating this nasty issue or not? As it is the only major problem I found while playing DirectQ. That source port satisfied me in every aspect of gameplay and gave a really nice old-fashioned feeling of quake experience.
I was running v1.9.0
You've probably been informed about "sinking into ground" bug that occurs after about an hour of playing in DirectQ...
I fucked-up the physics code somewhere, but never was able to determine where.
Yeah... it's a pity.
Apart from that terrible bug, DirectQ is still great
startdemos demo1 demo2 demo3 demo3 etc up to 32 demos
or edit your autoexec.cfg and add :
demos demo1 demo2 demo3 demo4 demo5 demo6 demo7 etc..
Oops! That's Not Right
startdemos assigns the order demos is the console command to skip to the next one in sequence.
so just use startdemos either in the .cfg or console
I wasn't too clear in my request.
Currently Mark V records 3 autodemos per session: autodemo_0, 1 & 2. If I die a 4th time (happens too often!) autodemo_0 will start from that point in the game, erasing my prior demos. What I'd like is to just keep recording demos 3, 4, 5 and so on.
And would love to have the demo be named the same as the mapname. So e1m3_0, e1m3_1 and so on.
Anti-funky Weapon Interpolation Models
I have a set of view models that someone fixed to work better with interpolation, by hiding the muzzle flash under the gun between the frames where it should appear, so it don't look as weird when fully interpolated. This doesn't make it look perfect (there is still some small movements visible), but it is a definite improvement (most notably for the standard nailgun).
I have no idea where I got these.... I've had them for many years.
Uhh, to use those in Mark V, you'll have to make a mod folder and put them in a "progs" folder in there, and run that game folder (but then they'll only work when you run using that game folder), or go to the hassle of sticking them in an extra pak file to drop in your id1 folder so they will always be used... which I'm sure is what you want.
This is a overly-difficult because Baker doesn't have Mark V (like the other advanced Quake engines) give preference to user-inserted drop-in content outside of pak files. But it really should do that, for reasons such as this! ;)
Qrack has cl_autodemo which names demos automatically.
using mapname_date_time as the filename.
cl_autodemo 1 starts recording at mapload and stops at intermission.
Qrack also has bsp2 support with protocol 666 so it will load any map that markv can load.
if that helps for the time being
Downloaded - will play with it for sure. Looks like you are still updating this regularly. I wasn't aware.
let me know if there are any config issues i can
help you set it up.
Dwere Did Some Really Nice Weapon Models
Thank you, mate :)
I will surely give it a try.
MH wrote a nifty ‘hack’ to remove muzzle flash polygons
from the original models.
look for gl_clip_muzzleflash here in gl_mesh
This hack, IIRC, is pretty much what I described above. It's a good few years ago so I don't remember details, but I'm pretty certain it uses the same logic.
Quake Giblets: Mark V
Enjoy! Feedback welcome. I can always do a sequel with more features.
NE_Ruins (Custom Map)
A terrible freeze occurs if I use "LAST WEAPON" command bound to MWHEELUP, especially when I picked up the Quad Super Shotgun (Looks like super shotgun from Quake 2). Once I use "bind "MWHEELUP" impulse 12" it freakin' freezes. Only task manager helps to shut the game.
Also Mark V shut down once I entered the bridge with Death Knights.
NE_Ruins (Custom Map) 2
It's impossible complete this one with Mark V.
I've solved an issue with a freeze glitch discribed above by setting the following cvar :
"sv_gameplayfix_no_impulse12_override" to "0"
but the enemy which uses yellow shield (some sort of a witch) around itself causes the engine to crash. Once it starts to use that kind of attack the engine instantly crashes.
An emergence of this bug was also tested with a default cfg to eliminate a suspicion that something is wrong with setup.
Mark V Mouse Input Issues
Hi guys! New to Mark V, but really enjoying it. The only problem is the mouse input issues that others have touched upon recently, and I have a few things to add:
1. My mouse1 button does tend to get stuck not firing or stuck continuously firingas mentioned before, however it doesn't just extend to mouse1:
-mouse2 also tends to have the problem sometimes in the rare circumstance I use it to scope in. It's difficult to recreate by accident but I can do it sometimes if I purposefully mash it.
-mouse4 and mouse5 also seem to be affected. I use them for next and previous weapon, and they often just don't respond at all.
2. These problems only happen in Mark V, like others have experienced. It cannot ever be recreated in any other game, application, or circumstance. It doesn't seem to matter which mouse I use, either.
3. The most interesting thing is the fact that this doesn't seem to affect other types of keys. I never experienced the issue once after remapping my left click to Ctrl in my mouse software. Furthermore, I had previously mapped the side buttons to 1 and 2 instead of mouse4 and mouse5 in my mouse software and until I changed it back to normal I had never had a problem with those buttons in Mark V.
4.It doesn't seem to be a Windows 10 only issue, as I'm running Windows 7.
Hopefully this can get fixed, because I am really enjoying this engine a lot otherwise. It's difficult to discuss issues like this online without others immediately blaming your mouse despite all the evidence to the contrary or just telling you to switch to another engine like Quakespasm :P
Re: Post 2476
Errr... that crash bug with the witch resurrecting fallen enemies in NE_Ruins was fixed years ago. I had reported the issue and delivered hints to fix the problem back then. Are you sure you are using a recent build for Mark V? If it's crashing with a new version, then the issue was accidentally reintroduced and requires fixing again.
I'm using v1.99 (Revision 4)
From the section "Download Windows .Zip"
"DirectX / GL / WinQuake''
It seems that this bug bug emerges on the newest version...
Re: Post 2476
Yay, that means that Baker must have reverted these fixes in one of his last updates. Try using a previous snapshot and see if it works with those. We need to find the build that broke it.
Ne_Ruins was fixed back then in beta 14 of pre-v1.0:
As you can see, that was back in 2015. The problem back then was "incorrect handling of entities with alpha=0" according to Baker. If he did anything in the meantime that undid this, it's clear why the crashes occur (again).
I am not sure if I had reported the impulse12 issue as well, but when I played Ne_Ruins with that beta build back then, I know I had zero crashes.
Re Post 2481
"Mark V - Version 1.99 - Revision 2 (Stable?)
#2092 posted by Baker on 2018/05/08 23:25:05"
Have just tried "Revision 2" from post #2092
Same issue, same occasion.
You will probably need to go back further. It's possible it broke last year or even earlier again... I never checked it a second time after the fix since I assumed it would not break twice. Makes me wonder which of my reported issues are still solved. Gulp.
Ne_Ruins Crash Reproduction
So I have tried builds dating back to 1001 (Nov 21, 2016) and it still crashes. This needs investigation.
Please download this savegame for testing purposes (zipped, 66 KB)
and copy it into your ne_ruins directory, then load it with F9 ingame.
How to reproduce the issue:
- Go around the corner
- Kill ONLY the Death Knights
- Let the succubus with wings alive and let it resurrect the Death Knights
- Stay in FOV of the succubus, crash will occur eventually
Sad that this problem returns to the stable builds. However, couldn't reproduce the impulse12 crash. I can go back and forth through my weapon inventory without issues.
RE Ne_Ruins Crash Reproduction
I have just checked it out following your instructions.
The crash occured immediatly right after the succubus started resurrecting those guys. Yeah, that's pretty inconvenient to have this stuff emerging in stable builds.
Concerning "impulse12" related crash. You gotta have super shotgun and quad super shotgun in your possession.
Try to scroll previous/last/next weapon with any button you assigned to execute that action. The game freezes then.
Couple Of Things To Mention
1) When I press "load game" then load the savegame and then press ESC button it shows me "load game" menu instead of Main Menu of Quake. That's a bit inconvinient because I usually accidentally press "Enter" button and load a save game while forgetting to save the game after updating my game progress thus it results in loading an old savegame :D
Is there an option to disable this kind of a "Remember last menu" feature ?
2) If you run across a nailgun ammo box while firing the nailgun - it stops firing for a half a second. Really strange. Same applies for Supernailgun.
I think the impulse12 in Ne_ruins would need to be fixed within the mod. It wasn't made with impulse12 support and since that quad shotgun is an extra weapon, it causes problems. I believe s.o. actually made a patch for that, but I could be wrong. The succubus resurrection crash is definitely to blame on Mark V, though.
I also cannot run Ne_Ruins without assigning more memory to it via -heapsize 512000. Otherwise I get a crash right after leaving the intro map (Hunk_Alloc).
One More Thing To Mention (#2486)
At the introdution map of Quake, if you don't move your mouse and you go forward (move forward command) the player starts to look down at ladder a bit and if you go back (move back command) to the top the player centers his view back. If you move your mouse at the beginning - this behavior disappears.
Strange stuff, I think there must be a console command to disable such a behavior, but I can't find one.
When I go to multiplayer section of Dissolution Of Eternity (or any other mission pack) I don't see any maps of this expansion available for deathmatch or cooperative gameplay. There are only original Quake SP and DM maps displayed. Same for Scourge Of Armagon. Is there any way to make the maps displayed in multiplayer? Because it's impossible to play mission packs in coop or dm modes.
Is there any specific command line to enable creation of directories called "Save" and "Screenshots" inside a corresponding mod folder or main ID1 directory? It would be nice to have Mark V storing savegames and screenshots inside these particular folders.
A Note To Baker
You shouldn't remove this command since it is actually used. For example I change my refresh rate between my laptop and stationary PC. On laptop I'm running 60 hz and 100 hz on PC. So I use this - "vid_refreshrate" to set it up.
It would be nice if Mark V had more than 20 save slots for savegames. 50-100 would be great.
Should be implemented :)
Is It Sorta Trolling
i dont think i have ever saved a game. then again quake is kinda easy by today's standards why do you need more points of continue from point another to during any one map?
One simple way to gain more save points is to simply use console command "save".
For example, you can easily type "save 111" in the console and save your progress up to that point in the save file named 111.sav.
Likewise, if you need more save points, simply type another name for the new save file.
Though I must admit that remembering all those save file names can be a hassle. I don't remember if MarkV still allows for "dir" command in console for listing the file names.
So I'm stuck with Windows 10, and I guess you are already aware of the audio problems. Having several second lag on all sounds, so havn't been able to work much with MarkV lately.
My most recent map uses a lot of new mdls some with alpha masking. MarkV can handle all except for one. There is a seahorse with masking on the wings and fullbrights intentionally painted on the stomach for glowing effect.
QS and QSS can render it properly:
But MarkV will display the fullbrights as solid black:
Its a shame, as its the only one it won't handle.
Here's hoping that a fix comes along one day.
Windows 10 Audio Latency
Seems like MarkV is probably detecting palette index 255 as fullbright rather than as alpha.
Who Cares If
everybody's running qs
shitbler and its minions
detecting or not detecting
DirectQ/ QuakeSpasm Style Coloured Lighting
Hi devs, i have 2 questions/requests:-
1) Is it possible to have a tweak(config) for the intensity of coloured lighting in Mark V to match that of DirectQ/ QS. The colour lighting in Mark V is not as intense and vibrant as it is other two ports. I am using lit and vis file from here:
2) Is it possible to tweak settings to get DirectQ style coloured dynamic light effects without QMB effects. Maybe u can add another effect preset that matches DirectQ effects.
Although QMB effects are cool but they do feel out of place of 90's. But the coloured dynamic lights alone feel perfect.
Is it possible to have a tweak(config) for the intensity of coloured lighting in Mark V to match that of DirectQ/ QS. The colour lighting in Mark V is not as intense and vibrant as it is other two ports.
The lighting in MarkV and QS should be identical; they both effectively use the same 2x modulate blend which is capped-off (and saturates to white) at double intensity.
There are areas in even stock ID1 maps where this is a significant factor.
DirectQ used a custom HDR texture format which required unpacking in pixel shader code, and which had neither capping nor saturation. The idea was to store some extra data in the (otherwise unused) alpha channel of lightmap textures to fill in the extra dynamic range. Typically you'd see examples storing an exponential or multiplicative factor in there; I put a division in because I tried everything else and that was what looked best (in the context of Quake lightmaps, that is).
In a fixed pipeline engine it would be possible to trade an extra bit of precision and do a 4x modulate, capping at quadruple intensity. That's actually OK because 4x in 8 bits still beats software Quake's 2x in 6 bits. However it would rule out support for single TMU cards (you could gracefully drop back to 2x via glBlendFunc (GL_ONE, GL_ONE) however, but the very first generation of consumer cards may not support that blend mode). Other texture formats such as RGB10A2 would also work well, assuming you were happy to set OpenGL 1.4 as a minimum requirement.
Personally I think these would be all reasonable tradeoffs - there comes a point at which continued support for dead hardware contributes a net negative - but I'm not the developer of Mark V.
I'm more a fan of e5bgr9, as it can also be used by a fixed-function pipeline (although requires a gl3ish gpu) without extra scalers, doesn't require any manual interpolation, still allows for up to 4000-fold overbright (ish), has higher precision than rgbx8, and uses the same ammount of gpu memory as rgbx8 (half as much as half-floats would). etc. If you're lazy you can just hardcode the exponent and get 4x overbright with the same precision as rgbx8 would get with 2x overbright. And if you're not lazy then you can get more precise dark areas alongside insanely bright areas.
does anyone still use a gpu older than gl3?..
I personally consider D3D11 to be entry level these days, it's a ~10-year old API. GL versions do lag for some vendors, however. GL3.2 is probably a reasonable minimum.
I find it better to do lightstyle animations on the GPU, and dynamics with extra additive blending passes. I've coded it up in GL1.5 assembly shaders, GL 2..4 GLSL, D3D9 HLSL and D3D11 HLSL for Q1, Q2 and H2 so I'm quite satisfied that the approach is solid.
The difference in lit rendering between MarkV and QuakeSpasm, DirectQ could be the LightNormalize function which does:
lit = lit * (greyscale / max(lit.r, lit.g, lit.b));
so max(lit.r, lit.g, lit.b) needs to be equal to the greyscale value, or the final rendering will be different from engines that don't do this. If the lit files from https://quakewiki.org/wiki/External_Lit_And_Vis_Files
don't have that property, this will be causing the difference you're seeing.
i've just installed Mark_V using the Steam installer and it works great!
i've had one issue where for some reason when i bind mwheelup or down to anything besides next/previous weapon (either through the console or in the options menu) it just doesn't work.
I get no errors, but when I bind it to jump, for example, nothing happens
anyone have any idea what the cause may be?
Flagged the spam but one contained a very nice compliment which i will past here:
I feel like all your ideas are incredible!
I Feel Like The Return Of Baker Is Much Needed.
Is there a way to increase the music volume? The cd music volume doesn't change the external mp3 file music volume.
PS: Love the engine, its the only one I have been able to find that lets me play the game like its meant to look at 320x240 with external music.
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.
Water Brush Bug
In mark_v.exe (not _winquake), if a water brush is not at least overlapped by at least one unit by a non-water brush on one face, it will not render as transparent unless you activate r_novis 1. With developer 1, it claims that the level is not vised. In mark_v_winquake.exe, it does see the vis information and properly renders the water.
Nehahra With Mark V
I've played through Nehahra recently with Mark V and had no personal issues at all, just specify -nehahra in the command line. The fog and pretty much all graphical features work, the cutscenes do not mess up the HUD afterwards unlike the original executable, the custom music will not play however, maybe it doesn't support xm files but the cool outro music on epilogue texts between chapters does play.
There's some funky things Nehahra does that technically work, but that it really shouldn't do. In other words, the kind of thing that normally comes back to bite you in the ass at some later date.
Two of the big ones will be that it uses a modified protocol but doesn't change the protocol version number, and that it relies on sending stuffcmd every frame for certain things rather than the built-in messaging or reading options from worldspawn.
If you use winquake with vid_stretch 1 or 2, water in dopa has a bunch of lines through it.
To correct this you can set r_wateralpha to 1.
Figured I'd mention this in case it hasn't already been brought up.
is normal behaviour on those maps which support it (the original game doesn't as standard)
Ahh I see. Shouldn't winquake default this cvar to 1 automatically though since it doesn't support transparency?
The lines you are seeing are
the transparency. It's exactly the same transparency method used in old games such as Sonic 1 for the Sega Genesis
However, I agree that it doesn't look good in MarkV. A stippled pattern would look better, as implemented in old versions of Makaqu.
Shouldn't winquake default this cvar to 1 automatically though since it doesn't support transparency?
Stock WinQuake doesn't support translucency, but several engine mods have added it, of which MarkV is one.
Thread Closed Due To Spam.
Thread Re-opened So People Can Read The Spam
This place... I was just curious as to why a particular thread was closed.
Didn't mean to be arsey, but it has been annoyingly persistent on this thread recently.
Wonder what the the target words are that the bot is using to to focus on this thread?
I was wondering if the bots keep chasing their most recently spammed threads?? Tho, obviously the browser / mobile thread was targetted by words.