Rendition widescreen, unlocked the viewport beyond the top 308 rows of pixels and fixed the aspect ratio weirdness. 16:9's doable. but 32:9 needs a camera offset:
https://youtu.be/4S6X4glexTg
https://www.patreon.com/posts/indycar-racing- … ntent=join_link

Gona wrote on 2025-11-16, 21:12:

I hope Windows 95 is also suitable: […]
Show full quote

sharangad wrote on 2025-09-15, 18:22:

@Gona, could you post the resources used in Windows 98 by your 3DBlaster VLB? I'm interested in ports and address ranges. I hope these are listed in device manager.

I hope Windows 95 is also suitable:

Copy code to clipboard

1I/O range: 03E0 - 03E3
2IRQ: 05
3Memory Range: C8000000 - C8000FFF
4Memory Range: D9000000 - D9FFFFFF

@Gona, could you try running this, it should dump to the screen and produce a log file?
https://nirvtek.com/downloads/3DBVLB.20251123.001.7z
MD5: 8d6f67dea2c45800eb4abbda959845ec

The 3DB blaster initialisation software appears to be reading a byte from IO port 0x20B to 0x303 until it finds what it's looking for. It's looking for a non 0xFF value, but simply returning something other than 0xFF doesn't appear to work.

sharangad wrote on 2025-11-23, 12:00:

@Gona, could you try running this, it should dump to the screen and produce a log file? https://nirvtek.com/downloads/3DBVLB.202 […]
Show full quote

Gona wrote on 2025-11-16, 21:12:

I hope Windows 95 is also suitable: […]
Show full quote

sharangad wrote on 2025-09-15, 18:22:

@Gona, could you post the resources used in Windows 98 by your 3DBlaster VLB? I'm interested in ports and address ranges. I hope these are listed in device manager.

I hope Windows 95 is also suitable:

Copy code to clipboard

1I/O range: 03E0 - 03E3
2IRQ: 05
3Memory Range: C8000000 - C8000FFF
4Memory Range: D9000000 - D9FFFFFF

@Gona, could you try running this, it should dump to the screen and produce a log file?
https://nirvtek.com/downloads/3DBVLB.20251123.001.7z
MD5: 8d6f67dea2c45800eb4abbda959845ec

The 3DB blaster initialisation software appears to be reading a byte from IO port 0x20B to 0x303 until it finds what it's looking for. It's looking for a non 0xFF value, but simply returning something other than 0xFF doesn't appear to work.

OK, here it is.

1...
2[Unknown] Port 02F7, input value FF
3[Match] Port 02FB, input value 03
4[Unknown] Port 02FF, input value FF
5...

Gona wrote on 2025-11-23, 20:07:

OK, here it is. […]
Show full quote

sharangad wrote on 2025-11-23, 12:00:

@Gona, could you try running this, it should dump to the screen and produce a log file? https://nirvtek.com/downloads/3DBVLB.202 […]
Show full quote

Gona wrote on 2025-11-16, 21:12:

I hope Windows 95 is also suitable: […]
Show full quote

I hope Windows 95 is also suitable:

Copy code to clipboard

1I/O range: 03E0 - 03E3
2IRQ: 05
3Memory Range: C8000000 - C8000FFF
4Memory Range: D9000000 - D9FFFFFF

@Gona, could you try running this, it should dump to the screen and produce a log file?
https://nirvtek.com/downloads/3DBVLB.20251123.001.7z
MD5: 8d6f67dea2c45800eb4abbda959845ec

The 3DB blaster initialisation software appears to be reading a byte from IO port 0x20B to 0x303 until it finds what it's looking for. It's looking for a non 0xFF value, but simply returning something other than 0xFF doesn't appear to work.

OK, here it is.

Copy code to clipboard

1...
2[Unknown] Port 02F7, input value FF
3[Match] Port 02FB, input value 03
4[Unknown] Port 02FF, input value FF
5...

Thanks Gona! I'll have another test app soonish.

Gona wrote on 2025-11-23, 20:07:

OK, here it is. […]
Show full quote

sharangad wrote on 2025-11-23, 12:00:

@Gona, could you try running this, it should dump to the screen and produce a log file? https://nirvtek.com/downloads/3DBVLB.202 […]
Show full quote

Gona wrote on 2025-11-16, 21:12:

I hope Windows 95 is also suitable: […]
Show full quote

I hope Windows 95 is also suitable:

Copy code to clipboard

1I/O range: 03E0 - 03E3
2IRQ: 05
3Memory Range: C8000000 - C8000FFF
4Memory Range: D9000000 - D9FFFFFF

@Gona, could you try running this, it should dump to the screen and produce a log file?
https://nirvtek.com/downloads/3DBVLB.20251123.001.7z
MD5: 8d6f67dea2c45800eb4abbda959845ec

The 3DB blaster initialisation software appears to be reading a byte from IO port 0x20B to 0x303 until it finds what it's looking for. It's looking for a non 0xFF value, but simply returning something other than 0xFF doesn't appear to work.

OK, here it is.

Copy code to clipboard

1...
2[Unknown] Port 02F7, input value FF
3[Match] Port 02FB, input value 03
4[Unknown] Port 02FF, input value FF
5...

Another one for you Gona. I've trapped more ports this time:
https://nirvtek.com/downloads/3DBVLB.20251124.001.7z
MD5: c2e16fec67952415e29dbee22adc73d5

sharangad wrote on 2025-11-24, 07:44:

Another one for you Gona. I've trapped more ports this time:
https://nirvtek.com/downloads/3DBVLB.20251124.001.7z
MD5: c2e16fec67952415e29dbee22adc73d5

OK, here it is.

Gona wrote on 2025-11-24, 16:49:

sharangad wrote on 2025-11-24, 07:44:

Another one for you Gona. I've trapped more ports this time:
https://nirvtek.com/downloads/3DBVLB.20251124.001.7z
MD5: c2e16fec67952415e29dbee22adc73d5

OK, here it is.

Thanks. That unfortunately didn't do quite what I expected. There'll be another test soon.

Gona wrote on 2025-11-24, 16:49:

sharangad wrote on 2025-11-24, 07:44:

Another one for you Gona. I've trapped more ports this time:
https://nirvtek.com/downloads/3DBVLB.20251124.001.7z
MD5: c2e16fec67952415e29dbee22adc73d5

OK, here it is.

I think the initial port writes configure a DMA command buffer and actual apps loop until the IRQ is triggered. I mirrored the initial port writes, but it didn't work. Probably because the data I need to send to the VLB needs to present in memory or interrupts need to be enabled, which my app doesn't have. I think the IRQ for the VLB is 3 (I'm probably wrong. Yes I am, it's 5), which might be what the port read returns. I think you listed the DOS config earlier.

Yup in the test app, interrupts are disabled in dosbox at least. I could get you a build to test this on the VLB, but I think it would be mostly pointless. I need to think about this for ab it.

Ok got the offsets for sprites and cars, but the player's wheels (but not the actual position of the car for collision and physics) and the sky still need correcting:
https://youtu.be/JaVuKsKqxkc

I ran a test yesterday to grab an execution trace. Took all day and ran out of disk space at many many hundreds of gigs. Trawling through assembler is painful. Unfortunately it's hard to find these things in ghidra. By passing know values for the aspect ratio in the projection matrix and tracing them, it's possible to find the rendering pipeline. Unfortunately I can't capture this for an actual practice session, to get the player car, because with core=simple and debug logging it takes forever and produces a massive amount of logs.

Attempt to test EuroFighter 2000:
installing EuroFighter 2000 than installing TATCOM is ok, the stage on patching to v2.0 fails here, always asks to place patch in tatcom directory.

if you happen to have EF2000 V2.0 CDROM there is installation for rendition and it win16 only.
to resolve it copy entire rend folder to HD and then put inside a win32 installer, so you could install this game on win64
https://community.pcgamingwiki.com/files/file … eric-installer/

and then , only FIFO , DMA is hangs.

after playing a some time, polygons starts to disappear (solid gray color )

excerpt from readme: "

Rendition V1000 based cards.
----------------------------

The Rendition V1000 version of the game utilizes the Windows 95 display drivers.
Some older versions of these drivers fail when used by a DOS program. Always ensure that
the most recent drivers are installed and selected.

ALT F10
Cycle gamma correction mode. Initially gamma correction affects red, green and
blue simultaneously. By changing the gamma correction mode, subsequent presses of
ALT F7 and ALT F8 can be made to affect red, green and blue components individually.
The available modes are RGB(simultaneously), R(individually), G(individually), and
B(individually).

ALT F9
Toggle shape anti-aliasing on/off. This results in mobile shapes such as planes and tanks
having their external smoothed.

PLEASE NOTE:
If you are using the rendition version of EF2000 V2.0, Installation of DirectX 3
may cause the error:
"Couldn't open Verite card. Error 50 code 1"
when trying to play the game. This problem is rectified by installing the Rendition
video drivers again.

"

by trying change game or RGB components its not affected in main game 3D Scene, only menu is about to change gamma/colors. (not tried on real HW trough. Its new discovery for me)

by trying to activate Anti-Aliasing you get a huge amount of black lines on screen. (again not tried on real HW, and curious how it will looks like)

No deep tests done, game slow , low fps.

RaVeN-05 wrote on 2025-11-30, 18:40:

Attempt to test EuroFighter 2000: installing EuroFighter 2000 than installing TATCOM is ok, the stage on patching to v2.0 fails […]
Show full quote

Attempt to test EuroFighter 2000:
installing EuroFighter 2000 than installing TATCOM is ok, the stage on patching to v2.0 fails here, always asks to place patch in tatcom directory.

if you happen to have EF2000 V2.0 CDROM there is installation for rendition and it win16 only.
to resolve it copy entire rend folder to HD and then put inside a win32 installer, so you could install this game on win64
https://community.pcgamingwiki.com/files/file … eric-installer/

and then , only FIFO , DMA is hangs.

after playing a some time, polygons starts to disappear (solid gray color )

excerpt from readme: "

Rendition V1000 based cards.
----------------------------

The Rendition V1000 version of the game utilizes the Windows 95 display drivers.
Some older versions of these drivers fail when used by a DOS program. Always ensure that
the most recent drivers are installed and selected.

ALT F10
Cycle gamma correction mode. Initially gamma correction affects red, green and
blue simultaneously. By changing the gamma correction mode, subsequent presses of
ALT F7 and ALT F8 can be made to affect red, green and blue components individually.
The available modes are RGB(simultaneously), R(individually), G(individually), and
B(individually).

ALT F9
Toggle shape anti-aliasing on/off. This results in mobile shapes such as planes and tanks
having their external smoothed.

PLEASE NOTE:
If you are using the rendition version of EF2000 V2.0, Installation of DirectX 3
may cause the error:
"Couldn't open Verite card. Error 50 code 1"
when trying to play the game. This problem is rectified by installing the Rendition
video drivers again.

"

by trying change game or RGB components its not affected in main game 3D Scene, only menu is about to change gamma/colors. (not tried on real HW trough. Its new discovery for me)

by trying to activate Anti-Aliasing you get a huge amount of black lines on screen. (again not tried on real HW, and curious how it will looks like)

No deep tests done, game slow , low fps.

Thanks RaVeN-05, the slowness is because of fifo mode. The antialiasing isn't capturing the screen properly, hence the black lines and the gamma issues are probably because I haven't enabled ramdac based palette support (like in vquakes and vhexen 2).

Really need to fix the fifo slowness.

Thanks for the thorough testing!

Thanks .
Correction :
activating AA in game actually kills some polygons, grays out it.
and Bottom most line and Rightmost line on 3d Scene screen is garbage lines, often white

RaVeN-05 wrote on 2025-11-30, 18:58:

Thanks . Correction : activating AA in game actually kills some polygons, grays out it. and Bottom most line and Rightmost line […]
Show full quote

Thanks .
Correction :
activating AA in game actually kills some polygons, grays out it.
and Bottom most line and Rightmost line on 3d Scene screen is garbage lines, often white

This should speed up FIFO mode in the Nascar games, Eurofighter 2000 and Scorched Planet (HUD won't render in FIFO mode for some reason) with Dosbox-Rendition:
https://nirvtek.com/downloads/RReady.Alpha.20251201.001.7z
MD5: e72c41d7e97bc8fad19c7d4cfd5913e4

- FIFO mode improvements. The Nascar games should be a lot closer to DMA mode in terms of framerate.
- Hidden broken widescreen support (flag to enable and modified binary not supplied, yet).
- No other Eurofighter bugs are fixed, yet.

RaVeN-05 wrote on 2025-11-30, 18:40:

Attempt to test EuroFighter 2000:
by trying change game or RGB components its not affected in main game 3D Scene, only menu is about to change gamma/colors. (not tried on real HW trough. Its new discovery for me)

by trying to activate Anti-Aliasing you get a huge amount of black lines on screen. (again not tried on real HW, and curious how it will looks like)

https://youtu.be/84xwbe7y-70

On that note I should probably get some sleep.

new build in FIFO mode:
Nascar Racing 1999 Black Screen.
Scorched Planet (Confirm no HUD and + to that issue a level descriptions have extremally huge font size)
Speedup +

RaVeN-05 wrote on 2025-12-01, 19:44:

new build in FIFO mode: Nascar Racing 1999 Black Screen. Scorched Planet (Confirm no HUD and + to that issue a level description […]
Show full quote

new build in FIFO mode:
Nascar Racing 1999 Black Screen.
Scorched Planet (Confirm no HUD and + to that issue a level descriptions have extremally huge font size)
Speedup +

I'll fix those.

RaVeN-05 wrote on 2025-12-01, 19:44:

new build in FIFO mode: Nascar Racing 1999 Black Screen. Scorched Planet (Confirm no HUD and + to that issue a level description […]
Show full quote

new build in FIFO mode:
Nascar Racing 1999 Black Screen.
Scorched Planet (Confirm no HUD and + to that issue a level descriptions have extremally huge font size)
Speedup +

I used otvdm to install Eurofighter and a ton of other 16 bit apps. Once it's installed 16 bit apps can be double clicked and run natively from file explorer on modern Windows.

The Scorched Planet problem was caused by the ICR aspect ratio code. That should now only kick in when ICR2 is being used with an aspect ratio corrected build. Nascar 1999 needs to have the nr1999.prf edited like this (witht he rem before the NODMA removed) to run in FIFO mode. The game ignores the SPEEDY3D_DMA=0 setting.

1; Rendition specific preferences
2NODMA
3rem 4BIT:

https://nirvtek.com/downloads/RReady.Alpha.20251202.001.7z
MD5:7de5da636e200fd83bb54d3c942aacfe

- ICR2 aspect ratio correction code should not affect Scorched Planet or any other Rendition app.
- Eurofighter 2000 + (Rendition) Gamma can be increased for white, red, green and blue but darkening is a bit difficult at the moment. I'll look at fixing this at a later time. AA lines only work in HUD, but not for external view and objects such as aircraft. I can't disable AA lines, because the in-cockpit HUD uses it. Both this game and ICR have issues with AA lines. This is probably a bug in the wrapper which breaks the rendering.
- FIFO mode performance should be greatly improved.

[EDIT] If NR1999R locks up, can you zip up the logs and attach it to your reply? Thanks Raven!

Tested , thank you very much , great job!!!
i think mentioning otvdm and maybe installshield 32 bit un pdf is good idea.
Thank you very much!

RaVeN-05 wrote on Yesterday, 16:05:

Tested , thank you very much , great job!!!
i think mentioning otvdm and maybe installshield 32 bit un pdf is good idea.
Thank you very much!

Thanks RaVeN, is FIFO mode actually faster for you in Scorched Planet?

yes old build is 26 fps max at starting position of Scorched planet vs 33 fps max at last build.
DMA still faster