Beer for Baker! 

I'm rather relieved that this obscure problem is resolved.

I hate it when I can't experience an issue. And this one ranked up there in the obscurity department. Fucking delayload.

Beer for MH! 

http://www.quaketastic.com/files/tools/windows/engines/Direct3D9-Wrapper-2017-01-19.zip

It's just the underwater warp stuff so no sweat if you can't get it in. 

I'll be integrating it here in a few minutes. Probably within an hour I'll post 1035. Need to update a zips, installer, etc.

This issue being resolved gives me great peace of mind! 

 

@dwere - Awesome!

@fifth - Is there is any particular reason you want the WinQuake GL build? The pure WinQuake performs better. 

1034 works for me. 

beer for MH and Baker ++ 

I dont think it did when I checked it last, weird...

You dont need to support it on my behalf tbh, I'm not likely to use it anyway 

I forced 640x480 stretch in WinQuake GL for higher fps than it would have had otherwise to somewhat compensate.

Still killpixel said every once in a rare while that it would stutter a little. 

one thing i have noticed recently on almost all Quake engines, is if I specify a full-screen resolution that is not the monitors native (1920x1080) there is a black border around the screen. So it looks like a 640x480 window ontop of completely black desktop. At first I thought it was a Qrack issue, but MarkV does this too. So i think it's an nVidia/Windows 10 thingy. My windows xp machine doesnt have this effect.

Any ideas? 

almost all Quake engines

Which ones don't have the issue? 

http://i.imgur.com/KpBMXGz.jpg

its a setting in the control panel now, why they changed the default behavior i have no idea... :S 

Download at normal location:

http://quakeone.com/markv

The Mac build remains version 1.20.

New Features vs. Mark V 1.20

- Very fast "triple the fps" DirectX 9 build courtesy of MH
- WinQuake looking water warp in Open GL/DX9 (MH again)
- Volumetric shadows - r_shadows 3 (MH again)
- Sky speed up in Open GL/DX8/DX9 (Yeah, MH)

- Linux Open GL build (thanks to JimBob for testing, Spike for debug tips)
- Linux WinQuake build

- Resize on-the-fly windowed mode in all builds (except DX8). Yes, even Linux. Tried to make the Linux build fancy. May have succeeded.

- QMB enforcer lasers available video

- Improved NVidia cards experience (killpixel, Kinn, johnny law, pulsar)
- 2 Extra options in video menu for convenience.

- Automatically bypasses GOG.com's ancient opengl32.dll (Syrion)
- Warpspasm correct startdemos by overriding Quoth 2.2 (path0gen)
- MH solved context creation issue in version 1.25 (dwere, breezep, ...)
- MH added extra control over r_waterwarp in 1.35. Type "find r_waterwarp" in console for details.

Next update hopefully some time in the spring! All feedback, comments, etc eventually get considered, a nice thing about the Func_Msgboard layout. 

Should have noted Gunter, railmccoy did a lot of testing of DX9. Maybe others. I've been updating page, installers, .zips, etc -- if missed someone who helped beta test it sure wasn't on purpose. 

Instant crash when attempting to launch any form of 1035. dx8,9 and good ole mark_v.

Apologies if I missed something in this bustling thread regarding this.

You two deserve many beers. 

Other reporting issues or feedback during latest development spree:

Fifth, Damage Inc, mugwump, nightfright, pritchard, adib (hope I didn't miss anyone, had to glance through hundreds of posts).

@damage - Sorry, if I couldn't implement true rotation. Ran out of time. Will have to hit that up next development period (likely the spring). You can always use the RMQ engine or presumably DarkPlaces or FTE for such experiments in the mean time. 

Can you add -developer to the command line and then post a quake\id1\qconsole.log? 

https://www.dropbox.com/s/n62r7wi8au2ruwj/qconsole.log?dl=0 

then remember to delete your .cfg file. I've had this happen to me a few times with new builds and deleting the cfg has sorted it out. 

Thanks. Can I get a copy of your autoexec.cfg, okcam.cfg and config.cfg so I can examine them? 

I'd still like to know what settings would cause the engine to actually crash.

If there are settings that can cause the engine to crash, I would want to make the engine handle that without crashing. 

https://www.dropbox.com/s/mb4a66rlt2lge5t/configs.zip?dl=0 

Do you have to okcam.cfg? I'm looking through things. I can say I don't crash with the config.cfg and autoexec.cfg you provided, but the okcam.cfg wasn't in your download.

/Is looking through settings 

Does the following:

cl_bob "0.012"
cl_bobcycle "0.55"
cl_bobup "0.7"

Just a cosmetic tweak.