save folder need to be in baseq2
so baseq2/save/save1/* files should be visible.

More Speedy3D games on Steam Deck:
https://youtu.be/GvbbyhdjasI

There're problems with keyboard handling in the latest Dosbox builds.

Someone hacked my nirvtek.com account and changed the password. There was an account set up called henry_ward@.... Got back control. Now I have to check the MD5 checksums of everything.

[EDIT] Or just reupload everything. There was a German fitness website on one of the subdomains.

Omg I hope everything will be OK

RaVeN-05 wrote on 2025-08-25, 12:15:

Omg I hope everything will be OK

Reuploaded the wrapper binaries. Not entirely sure how they got in. This is scary.

Also looked at the qspan bug with the save. Z seems to be zero at both edges for the missing wall. On original hardware it works fine. Loading the save is difficult, I think the save has checksums of all loaded dlls, which means when I change something in the wrapper I get the dreaded function pointers have moved bug. Fiddling around resaving an existing failed load back into the same save slot allows it to load again sometimes. Sometimes it involves more fiddling.

I fixed the broken keyboard logic. The problem cases appear to work now and once again it's stable. Just need to fix the qspan bug and the next release will be ready for testing.

There're other places where QSpans have the wrong z-coordinate:
https://youtu.be/DIggxu0QuPA

It works on a Pentium 4/V1000 (not on Ryzen or Core 2 Duo final gen on WIndows 10/11).

I'm hoping this is a CPU x87 unit bug, but it doesn't look like it, unless x87 behaves differently under Win98 than it does on Windows 10/11 (clutching at straws).

Riverside is now Rendition Ready:
https://youtu.be/qPEIBbLnnsw

Road Atlanta is too big even when reduced to just the largest MIP map per texture. I need to push out the next release and get back to ICR2 ASAP.

RaVeN-05 wrote on 2025-08-24, 11:05:

Scorched Planet, tried windowed and so many various video settings and intro doesn't get rendered.

I've tested this on Intel HD, Radeon R270, GTX660 Win 10 and nvidia on Win 11. It works. I think it needs all the latest windows updates., including drivers and OS patches.

RaVeN-05 wrote on 2025-08-24, 11:05:

i included save game where a lot of polygons skipped (not rendered) didn't remember if original HW have same bug, need to be checked on actual hardware first.

maybe QSPANS can be rendered as whole frame to some specially allocated buffer than got upscaled by OpenGL (with or without bilinear filtering) to rready resolution.
OpenGL's is faster than manual blending of QSPANS

This happens on original hardware as well. But works at 320x240 on both RReady and original hardware. I was running in software mode like an idiot on Verité. I'll post a short video when I get a chance.

Here it is on RReady and original hardware. Sorry about the aspect ratio, I was desperately trying all sorts of things to see if I could get non-zero qspan z coords:

https://youtu.be/ZLF0pYkkNVU

I was testing on the retro machine in software mode, completely unaware what was going and wasted quite a bit of time pfaffing about with the QSpan code.

It does work when vquake2's internal resolution is set to 320x240 (v1k_mode 0).

this looks like exceeded view distance

robertmo3 wrote on 2025-08-26, 11:06:

this looks like exceeded view distance

But it works at 320x200. The z-depth is always in [0, 65536).

[edit] maybe it's less at a lower res?

[OT] It looks lie someone's been trying to hack my reddit account from Russia. It's been locked.

My server's being hacked. The provider namecheap is being useless. I can't block specific ips because the hackers are using different IPs each time. Just be wary of anything you download.

My last download was on 22/08. Was it still safe?

filipetolhuizen wrote on Today, 00:40:

My last download was on 22/08. Was it still safe?

Check the MD5 checksum. If you open a cmd prompt (Start->type CMD [ENTER]) and type:
certutil -hashfile <full path to file> md5

(for instance certutil -hashfile c:\downloads\RReady.Alpha.001.7z md55) . If it matches the MD5 in the download link you should be ok. As far as I can tell, the downloads are OK. THey seem more interested in running a separate website on an unused subdomain. But I will re-upload all the binaries.

[EDIT] The Alpha release's auto-downloader for SDK demos does check the MD5 automatically.

RaVeN-05 wrote on 2025-08-24, 11:05:

Water surfaces in game alpha tested and alpha blended , should be only alpha blended (do not have strong cut edges)
Underwater resolution is better to be used at default 320x240 value, other resolutions can distort graphics.

This worked before I added GPU filtering to fix particle edges in the expansion packs. I need to tweak the GPU filtering parameters here.

https://nirvtek.com/downloads/RReady.Alpha.20250828.001.7z
MD5: e8c3fefce2413c04f5f0fee98820c06f

vQuake 2
- Corrects chroma keyed water not working with transparent textures.
- Particle sizes not perspective corrected (both square and anti-aliased)

For the last time, I think this can go into testing now.

Just to get my mind off things here're 3 tracks which are already Rendition Ready (Rio,Red Rock and Paradise Resort). These are Nascar 1999 conversions:
https://youtu.be/FoBDbI8-jLQ

I'm in a bit of a quandry as to what to do. Raven-05 is testing the wrapper against a bunch of games so more bugs will be found. My question is do I do monthly releases fixing these things or wait until everything's done before the next release. I also have other things to do like dealing with ICR2 and CGL support. There are no showstopper bugs for ICR2 at the moment other than [ALT+B] support and the internal frame rate indicator. The 60 fps capture failing/not working bug is there as well. The next release fixes those but hasn't been extensively tested yet and I don't want to break anything.

Is the next release necessary right now or can it wait a few more months? I do need to test my fixes to make sure nothing's broken.