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.