This line:
00433A91 mov dword_510F08, eax

is what causes the problem.

I think there's an overflow there with the multiple shifts and multiplies.

In particular dword_510F08 has the wrong value.

This value is written to 4753A4, which is what it's compared to.

[EDIT] Nope this is pretty much always zero.

RReady 26 November 2023

https://1drv.ms/u/s!As-dKk-N73dSlwkMo-Zu9Ad0nTvO
MD5: 62d506951ec1d9f2adc50d829d422b32

- Auto-downloader now downloads modified ref_v1k which support native fullscreen on modern Windows. Existing users will need to delete the existing ref_v1k, remove Quake 2 from the apps list and add it back in. Alternatively directly downloading the file from the link and manually patching it will be required. Force fullscreen and will no longer be required in rendition.cfg along with 'set vid_fullscreen "0" 'in baseq2/config.cfg. The change in ref_v1k is only 1 byte.

@Raven-05, I've sent you 3 PMs about VH2. Not entirely sure when you'll get them.

Your patched version of Vh2 for the golems. Does demo rr2 run at fullspeed with it?

When the VH2/vQ2 underwater res is higher than the full screen res, the pixel alignment goes out on the last row, when screen/HUD size is at default. This leaves a messy miscoloured row. Will have to sort out the pixel alignment. Affects everything from Quake AA, polygons to QSpans. The Rendition docs mention line rendering being subpixel based.

The underwater rendering renders to the top-left part of the screen and uses it as a texture and draws line starting at the bottom of the screen. Quake 2 uses integer y-coords, vH2 uses float y-coords with a fractional part of 0.5.

nCubed and nFinal also have issues with pixel alignment with the line rendering part.

Wasted a significant chunk of yesterday arguing about licensing with the dosbox staging guys.

The dosbox staging guys are threatening to sue me:

https://github.com/dosbox-staging/dosbox-stag … iscussions/3156

AAArgh! GliDOS already does this. Just say no to 'freemium' dosbox.

@Raven-05, on original hardware with vh2 underwater res set to 800x600 and fullscreen res set to 800x600 and screen size set to default with the background (wallpaper?) showing is there a boundary when underwater between the underwater section and the background?

sharangad wrote on 2023-12-01, 00:42:

The dosbox staging guys are threatening to sue me:

https://github.com/dosbox-staging/dosbox-stag … iscussions/3156

AAArgh! GliDOS already does this. Just say no to 'freemium' dosbox.

I don't know how the conversation turned from "debug dump skip instructions" to "we don't want to lose staging sales" to "read rules, we want money". (explains why staging is banned here)

Anyways what path are you following now?

BEEN_Nath_58 wrote on 2023-12-01, 05:58:

sharangad wrote on 2023-12-01, 00:42:

The dosbox staging guys are threatening to sue me:

https://github.com/dosbox-staging/dosbox-stag … iscussions/3156

AAArgh! GliDOS already does this. Just say no to 'freemium' dosbox.

I don't know how the conversation turned from "debug dump skip instructions" to "we don't want to lose staging sales" to "read rules, we want money". (explains why staging is banned here)

Anyways what path are you following now?

I didn't know staging was banned on Vogons.

I don't know now. I'm fixing a few minor issues with RReady and clearning up the vh2, vquake 2 high res options in Rlauncher. Got fed up after asking those guys for help.

Maybe I'll try another dosbox. Dosbox, vanilla dosbox is allowed here and I think Glidos uses it (as one of its dos interfaces). I should've gone with that to begin with.

sharangad wrote on 2023-12-01, 06:19:

I didn't know staging was banned on Vogons. […]
Show full quote

BEEN_Nath_58 wrote on 2023-12-01, 05:58:

sharangad wrote on 2023-12-01, 00:42:

The dosbox staging guys are threatening to sue me:

https://github.com/dosbox-staging/dosbox-stag … iscussions/3156

AAArgh! GliDOS already does this. Just say no to 'freemium' dosbox.

I don't know how the conversation turned from "debug dump skip instructions" to "we don't want to lose staging sales" to "read rules, we want money". (explains why staging is banned here)

Anyways what path are you following now?

I didn't know staging was banned on Vogons.

I don't know now. I'm fixing a few minor issues with RReady and clearning up the vh2, vquake 2 high res options in Rlauncher. Got fed up after asking those guys for help.

Maybe I'll try another dosbox. Dosbox, vanilla dosbox is allowed here and I think Glidos uses it (as one of its dos interfaces). I should've gone with that to begin with.

Vanilla is allowed, the devs are here as well. Maybe you'll miss some feature the forks provide, but it's better than a irrelevant headache

RReady December 01 2023

https://1drv.ms/u/s!As-dKk-N73dSlwwMo-Zu9Ad0nTvO
MD5: 3f280c6df107d21dbbec54891bbfe0d4

RLauncher fixes:
- All vQuake 2 and vHexen II binary hacks in their own section along with warning about not being thoroughly tested each release).
- Corrects vQuake 2 unlocked resolutions (1280x1024 is selectable for underwater resolutions. 1152x864 is the highest full screen resolution.) For vQuake 2 unlocked resolutions, the underwater resolution should be higher than the game's internal full screen resolution. For vHexen II it should be at or below the game resolution. Rendering issues may otherwise arise.
- Adds vHexen II 72/144 max fps limit and 11/22 kHz audio selection
- Existing Redline.dll and verite.dll rebuilt with latest compiler update. Hopefully nothing should break.

sharangad wrote on 2023-10-28, 17:48:

filipetolhuizen wrote on 2023-10-28, 17:39:

BEEN_Nath_58 wrote on 2023-10-28, 16:33:

What do you mean by "other cards"?

Others than Rendition (I believe only nVidia and AMD are our choices for the daily PC, now).

RReady listed on the first page will run Rendition apps on nvidia and amd gpus., though at the moment only Windows Rendition apps.

Wow! It does work great already. Just tried it with SODA Off Road Racing and it works out of the box. Is it possible to remove the overlay text?

filipetolhuizen wrote on 2023-12-04, 04:10:

sharangad wrote on 2023-10-28, 17:48:

filipetolhuizen wrote on 2023-10-28, 17:39:

Others than Rendition (I believe only nVidia and AMD are our choices for the daily PC, now).

RReady listed on the first page will run Rendition apps on nvidia and amd gpus., though at the moment only Windows Rendition apps.

Wow! It does work great already. Just tried it with SODA Off Road Racing and it works out of the box. Is it possible to remove the overlay text?

Just out of curiosity, what kind of GPU did you run it on? Most testers are on nvidia.

You need the Windows Store build for $9.99 (sorry about that) to get rid of the text. Just go to the store and type RReady Rendition Verite and it should pop up.

There's a major difference with the store build and the alpha build.

The store build doesn't have an auto-downloader (to download demos and ref_v1k/vh2.exe for vQuake2/vHexen2 and MDKRed.exe). This is because of store rules on bundleware. I don't have the rights to distribute these things with my app so they're downloaded from public sources (and checksum verified). For the store release click the help button and the resulting PDF file will have download links along with the MD5 checksums. You'll have to download them yourself.

sharangad wrote on 2023-12-04, 04:23:

filipetolhuizen wrote on 2023-12-04, 04:10:

sharangad wrote on 2023-10-28, 17:48:

RReady listed on the first page will run Rendition apps on nvidia and amd gpus., though at the moment only Windows Rendition apps.

Wow! It does work great already. Just tried it with SODA Off Road Racing and it works out of the box. Is it possible to remove the overlay text?

Just out of curiosity, what kind of GPU did you run it on? Most testers are on nvidia.

Mine's a rather old card now, the GTX460 (nVidia).
BTW, nothing happens when I try to get it from the MS Store. I believe it's not supported on Win7.

filipetolhuizen wrote on 2023-12-04, 04:36:

sharangad wrote on 2023-12-04, 04:23:

filipetolhuizen wrote on 2023-12-04, 04:10:

Wow! It does work great already. Just tried it with SODA Off Road Racing and it works out of the box. Is it possible to remove the overlay text?

Just out of curiosity, what kind of GPU did you run it on? Most testers are on nvidia.

Mine's a rather old card now, the GTX460 (nVidia).
BTW, nothing happens when I try to get it from the MS Store. I believe it's not supported on Win7.

RReady supports Win 7, the store doesn't. Recently the store stopped supporting Win8.1 as well.

What I suggest you do is buy it on a Win 10/11 machines (if you have access to one) and copy redline.dll and verite.dll from the installation. The store DLLs will work with the alpha launcher. I don't mind where you run it. You may have to install a game (or try RTest https://1drv.ms/u/s!As-dKk-N73dSlmafg4OhhQ3_osXs) add it to RLauncherm run it and then copy the DLLs from the RTest folder to your Win7 machine. There's no DRM.

I tried to release this on Steam/Epic but they refused to carry it. Apparently the policy now is "Non-games" not allowed. The weird things is some support guy from Epic actually told me it would be allowed and after I signed up and paid the entry fee and they pretty much said no, not allowed. So sorry about that.

How well does SODA run on a GTX 460?

sharangad wrote on 2023-12-04, 05:10:

How well does SODA run on a GTX 460?

Runs excellent, even at forced max res.

RReady supports Win 7, the store doesn't. Recently the store stopped supporting Win8.1 as well.

That's what I actually meant, the Store, not the wrapper itself.

New year new test app.

Could someone with an actual Rendition board run this from DOS:
https://1drv.ms/u/s!As-dKk-N73dSlw0Mo-Zu9Ad0nTvO
MD5: a72664f0a813d0d7886fea1938f33ae4

It should create a text file with a numeric name. Just attach it it here.

Thanks.

sharangad wrote on 2024-01-04, 10:06:

New year new test app. […]
Show full quote

New year new test app.

Could someone with an actual Rendition board run this from DOS:
https://1drv.ms/u/s!As-dKk-N73dSlw0Mo-Zu9Ad0nTvO
MD5: a72664f0a813d0d7886fea1938f33ae4

It should create a text file with a numeric name. Just attach it it here.

Thanks.

Hello) Wish you happy new year)

Happy new year to you and Vogons users everywhere!

That test app just broke one of my assumptions. Expect another shortly.

RaVeN-05 wrote on 2024-01-05, 09:55:

sharangad wrote on 2024-01-04, 10:06:

New year new test app. […]
Show full quote

New year new test app.

Could someone with an actual Rendition board run this from DOS:
https://1drv.ms/u/s!As-dKk-N73dSlw0Mo-Zu9Ad0nTvO
MD5: a72664f0a813d0d7886fea1938f33ae4

It should create a text file with a numeric name. Just attach it it here.

Thanks.

Hello) Wish you happy new year)

Ok Raven-05, can you try this:

https://1drv.ms/u/s!As-dKk-N73dSlw4Mo-Zu9Ad0nTvO
MD5: 5237f0119abc2541ddf19b5fbcc75218

All this time I think I was getting back garbage data. It actually looks like it's working now. CX returns an address and DX the segment.

Previously DX was 0. Now it's C000, which is in the video BIOS. If this returns what I think it'll return I'll knock something up to do a dump of your video BIOS. It should be from C000:0000 to C000:FFFF. Not sure if all those addresses will be accessible.

I think it's safe to say my Turbo C is a little rusty. Getting used to using long int for 32 bit values takes a bit of getting used to after Visual Studio.

Some of the Verite BIOSes on this site are supplied as a DOS binary. I don't know if they attempt to flash the BIOS or just extract the data.

What's your board Raven-05 ? V2k of which make?