The 3dfx guys had something more functional at this stage.

try turning off everything in quake1
https://quake.fandom.com/wiki/Console_C ... c_Commands:

Quake doesn't run yet. Terminates with a microcode error. Need to fix the texturing. I think they've got the wrong size.

Whiplash locks up , same with splanet. Haven't tried nascar 2 in a while. These 3 are probably waiting for a status register change which hasn't been implemented yet. Probably the same with quake. I'll try turning everything off in quake but I don't think it'll run.

Quake actually has 3 engine specific commands that're used only for vquake and vquake2. V_fifo_qspan, v_fifo_qzaaedge. These two work with rredline. For vquake there's another call v_fifo_qlight., which also exists in rredline but isn't used by vquake2 and vhexen2.

Of these I think qspan is critical this is used to render the world (background including some objects like crates). It works in windows because I have a buffer size. In dos land I have to wait for an end marker. The end marker exists in windows, but it isn't necessary because rredline supplies the size of the buffer so it acts an extra buffer overrun guard.

The slow speed is mainly because of my logging, unoptimized single mem writes.

There's also the overhead of converting register parameters back into high level RRedline parameters. Usually redline.dll and verite.dll take the command buffers and convert them into low register writes. This time around we're going the other way., Fortunately the command blocks are the same, whether they're written 32 bits at a time into fifo registers OR passed en mass into a DMA blocks. The internal syntax of the commands is the same. The issue is that memory addresses need to be converted back into RReady compatible address ranges.

Actually that gives me an idea about optimising the address lookup.

@robertmo3, cycles=105% is what I need right?

Nascar 1999 uses:
V_FIFO_MEM_WRITE_SPRITE which RReady doesn't support in Windows. I guess now it'll have to.

no,
cycles=max 105%

Thanks.

Could someone post a screenshot of the ICR2 app RR.exe?

It's supposed to flash a "Rendition Ready" logo, I think. I get something else (a monochrome F1 logo at the top of the screen).

Can you please upload this file

EDIT: video https://fex.net/s/mtykz5z

Thanks.

Rr.exe is problematic. It uses the 256 colour palette in 16 bit colour modes.

I think I'll ignore that for now. I'll need to come back to it later.

@Raven-05, do you know at what resolution RR.exe runs?

From the logs it looks to be running at 1024x768/

Verite owners, I need the non VESA modes. I don't know if the VESA query will return this, but it's worth a shot:

https://1drv.ms/u/s!As-dKk-N73dSmGXaUjIV04rOEvoj?e=Uq8VUS
MD5: 4ddee13fef29241af63548e6b7c48508

I need all the BIN files i the folder as well as the fifo.txt file.

Thanks.

sharangad wrote on 2024-03-28, 09:31:

From the logs it looks to be running at 1024x768/

yes its 1024x768

done on v2100 cureently installed , it is ok?

V2100 is fine. Thanks!

This should do nicely for now.

There're 2 more vesa calls I might need to test, but not right now. I need to fully implement the modes list first. This should let me work out the current speedy 3d res.

Also what res does icr2/cr run? I think it's 640x480.

Haven't actually checked.

yes its 640x480

Thanks.