Thanks Agentbsod. Still playing around with dosbox.

Does anyone know if Verité boards used the same io ports under dos as windows?

I suppose there's no way of knowing under dos.

I recall you once told that the latest Nvidia driver has issues with RReady, has it been fixed?

my friend discovered one of two undocumented vquake console cvars:

d_amip 1/0 (default 1) 1-use mipmaps on models, 0-dont use which is better quality .
d_sync 1/0 (default 1) - still unknown , maybe its vsync , seems nothing changes.

BEEN_Nath_58 wrote on 2023-11-15, 18:43:

I recall you once told that the latest Nvidia driver has issues with RReady, has it been fixed?

It was because Steam was running. Shutting it down magically fixed RReady/DxWnd with Interstate '76/Nitro/Mech Warrior 2. I think I posted it on the DxWnd thread on SourceForce.

BTW I fixed a lock up issue with Interstate '76 with RReady/DxWnd. It should crash now instead of locking up at a black screen. At least it does on my problem UHD 620 laptop. Still doesn't run though on this specific machine, runs on 3 others though. You could try it to see if it works for you. I was capturing SEH exceptions in a thread to try and shutdown gracefully. It wasn't shutting the game down.

The main thread had an option to produce crash dumps when detected. RReady/DxWnd wouldn't work with this enabled. Like I said you could try i76 again to see if it work now.

RaVeN-05 wrote on 2023-11-15, 18:50:

my friend discovered one of two undocumented vquake console cvars:

d_amip 1/0 (default 1) 1-use mipmaps on models, 0-dont use which is better quality .
d_sync 1/0 (default 1) - still unknown , maybe its vsync , seems nothing changes.

Nice. I can't see a difference in those two screenshots at 640x480.

sharangad wrote on 2023-11-13, 18:07:

That's the same. Now vidmode 0x15 = 21. Need to look that up and what CX=09CF is;

Thanks guys! What does a V2k return?

v2200 results

1
2Pre-entry AX 0000, BX 0030, CX 0006, DX DB43, ES 1337, DI 00F9
3
4On exit AX 0015, BX 0000, CX 0A2C, DX C000, ES 1337, DI 00F9
5
6ES:DS+01 = FF00
7
8ES:DS+02 = B036
9
10ES:DS+03 = 6866
11
12ES:DS+04 = 6310
13
14ES:DS+05 = BCE8
15
16ES:DS+06 = 833D
17
18ES:DS+07 = 04C4
19

click on screenshoots to load larger image, look as head and body at distance

is there a TSR which needs to be installed for Speedy3D? If you create a fresh Win98 install on a Rendition system and try to run a game does it run or is there a config.sys element to it?

nothing , you can run dos speedy3d games without installing drivers

RaVeN-05 wrote on 2023-11-15, 20:01:

v2200 results […]
Show full quote

sharangad wrote on 2023-11-13, 18:07:

That's the same. Now vidmode 0x15 = 21. Need to look that up and what CX=09CF is;

Thanks guys! What does a V2k return?

v2200 results

Copy code to clipboard

1
2Pre-entry AX 0000, BX 0030, CX 0006, DX DB43, ES 1337, DI 00F9
3
4On exit AX 0015, BX 0000, CX 0A2C, DX C000, ES 1337, DI 00F9
5
6ES:DS+01 = FF00
7
8ES:DS+02 = B036
9
10ES:DS+03 = 6866
11
12ES:DS+04 = 6310
13
14ES:DS+05 = BCE8
15
16ES:DS+06 = 833D
17
18ES:DS+07 = 04C4
19

click on screenshoots to load larger image, look as head and body at distance

is there a TSR which needs to be installed for Speedy3D? If you create a fresh Win98 install on a Rendition system and try to run a game does it run or is there a config.sys element to it?

nothing , you can run dos speedy3d games without installing drivers

That's an older binary, the one that's needed is this:

https://1drv.ms/u/s!As-dKk-N73dSlne9NrazjMm8uqpt?e=qHy6bd
MD5: 0dcdd7b0451aff80aefaba49e9053cc1

RaVeN-05 wrote on 2023-11-15, 20:01:

click on screenshoots to load larger image, look as head and body at distance

That's quite a bit a better.

[EDIT] Mispost.

VHexen II Bronze Golem Fix:

Caused by having too much VRAM. The build below lets you set MaxVRAM=<nn> in Rendition.cfg (megabytes/floating point value). For any type of golem to change colour during beam/projectile attacks MaxVRAM=14 or below must be set. VRAM must be capped at 14 MB or below. The framerate does drop quite a bit in some sections and there may be HUD rendering issues. These can be fixed, possibly including the constant texture loading (no promises).

The colour change delays or doesn't happen at all beyond 14 MB and trails off until 15 MB where it completely stops.

https://1drv.ms/u/s!As-dKk-N73dSlwIMo-Zu9Ad0nTvO
MD5: 79f3fefbf6b58f06a25782a0cfcd9cf4

It would be nice it this worked with full 128 MB of VRAM.

@Raven maybe there's something you can do to fix this?

[EDIT] There's a whole lot of memory safety changes, which may break things.

Will try, sounds not trivial .

WIth 4 MB of RAM, in demo RR1, the fountain has a reduced particle count.

Partially tested (all games should run. )

https://1drv.ms/u/s!As-dKk-N73dSlwMMo-Zu9Ad0nTvO
MD5: 06430b0e6c37761875430acc86f9f04b

- VH2 bronze and Egyptian golems will change colour during particle attack when MaxVRAM=14 is set in Rendition.cfg (or any value beween [4,14] is set). Do not use this option with any other applications. It is untested against all those. Game performance will be poor when VRAM is restricted. This doesn't affect gaming resolution, only texture storage capacity. Running at the default VRAM capacity (128MB) will prevent the golems from changing colour. This appears to be an issue with the application.
- RRosetta can toggle between renderers by using F1-F3 (for F3 to work dgvoodoo's directdraw/3d files (4 files) must be placed in the same folder as RRosetta)
- UseMSAA=3 enables the experimental (and incomplete) vh2 and vq2 AA. RReady defaults to MSAA (UseMSAA=0).
- Memory safety measure are in place, so performance may dip by 1-2 fps.

sharangad wrote on 2023-11-20, 06:59:

Partially tested (all games should run. ) […]
Show full quote

Partially tested (all games should run. )

https://1drv.ms/u/s!As-dKk-N73dSlwMMo-Zu9Ad0nTvO
MD5: 06430b0e6c37761875430acc86f9f04b

- VH2 bronze and Egyptian golems will change colour during particle attack when MaxVRAM=14 is set in Rendition.cfg (or any value beween [4,14] is set). Do not use this option with any other applications. It is untested against all those. Game performance will be poor when VRAM is restricted. This doesn't affect gaming resolution, only texture storage capacity. Running at the default VRAM capacity (128MB) will prevent the golems from changing colour. This appears to be an issue with the application.
- RRosetta can toggle between renderers by using F1-F3 (for F3 to work dgvoodoo's directdraw/3d files (4 files) must be placed in the same folder as RRosetta)
- UseMSAA=3 enables the experimental (and incomplete) vh2 and vq2 AA. RReady defaults to MSAA (UseMSAA=0).
- Memory safety measure are in place, so performance may dip by 1-2 fps.

Just wanted to enquire even though this is far away: is there a possibility that we see a D3D11/12/Vulkan version of RReady considering how buggy OpenGL ICDs are nowadays?

Porting to Vulkan I don't think will be massively difficult, the same shaders can be used (glsl), possibly with a wrapper (code wrapper library).

D3D is a massive change.

But neither of these are happening anytime soon.

Can someone dump BIOS ROMs from a V1000 and a V2000?

I'll be needing that next.

from this site you can download bioses:
https://vgamuseum.info/index.php/component/k2 … on-verite-v2100
https://vgamuseum.info/index.php/component/k2 … on-verite-v2200

direct link hope they will work:
https://vgamuseum.info/index.php/component/k2 … 5c37535e6208c14
https://vgamuseum.info/index.php/component/k2 … fc15b0dd49002e7

https://vintage3d.org/verite1.php#sthash.hYWO … a.x1KrEhIZ.dpbs
this is https://vintage3d.org/data/phx2105.com v1000 bios

also BIOSES available at http://vogonsdrivers.com/index.php?catid=18

Thanks.

The golem texture sizes are 196x118 and 392x 237. Dunno if you can spot anything in the assembly. There are other textures of this size.

The functions used for this VL_Lookup, VL_InstallTextureMap (possibly the basic variant), and sometimes VL_SetSrcBase though this might be carried out a direct command buffer write (VL_AddToCmdList(2) with 4096 and then the VRAM address of the surface poked into the resulting buffer). VL_Lookup(0, 0, texwidth, texheight) is a dead giveaway and VL_PointSurface with the dimensions of the texture.

VL_Lookup is called even if r_surfacelookup is disabled for this texture. Behaviour's altered after calling V_GetLargestBuffer which has a size parameter for the largest buffer possible. This returns a v_buffer_group pointing to allocated memory and the size of the buffer. By altering the size you can control whether the golems are rendered.

I'll finish my testing of the next build and do an alpha and store release before moving on.

DOS Test with Rendition board:
https://1drv.ms/u/s!As-dKk-N73dSlwQMo-Zu9Ad0nTvO
MD5: b07048c3ab55f6772d8881fe9fa97444

Run IDT in MS-DOS mode. It should dump the location within the ROM BIOS that the INT 10h calls redirect to (address F000:F065).