I take it it locks up?

ow sorry , yes it lockups where video ended

https://1drv.ms/u/s!As-dKk-N73dSmAwMo-Zu9Ad0nTvO
MD5: 910dfe978a65d0ca1fa971f78ab26b86

if this works as before (black screen at 3D), let's call it quits for now.

I'll post the source to sourceforce and someone sharper than me can take a look.

now mouse cursor on top of game, goes to black screen, unfortunately

Do the menus render?

yes

https://1drv.ms/u/s!As-dKk-N73dSmA0Mo-Zu9Ad0nTvO
MD5: d80995aa1e278a5a99a10d0118b0959f

This adds a 10 ms sleep to V_QueryCmdBuffer if the buffer's in use. This should make the logs (slightly smaller) and maybe prevent the lock up.

Command buffer processing is done in parallel on the Verite, so this should test to see if the added overhead of the wrapper prevents the board from updating the buffer status, i.e. memory lock starvation. I *don't* think this is the problem, but at this stage it's worth a shot.

Something I noticed, there're other periods in the logs where the buffers are locked in the opening logo sequence. VL_FIllBuffer to blit an alpha blended white rectangle on to the F1 logo to make it fade in is bandwidth intensive, because it fill the screen. So for a while the buffer stalls, but it does recover.

done

https://1drv.ms/u/s!As-dKk-N73dSmA4Mo-Zu9Ad0nTvO
MD5: cfbd542a4d9f47962f7d0e35e1f702d9

No sleep, VL_Tristrip disabled. See if it crashes.

done

Source:

https://1drv.ms/u/s!As-dKk-N73dSmA8Mo-Zu9Ad0nTvO
MD5: 9001e9e0c02b9fe1710ff6f392bb22b8

I'm going to pause work on this for a while and focus on Speedy3D. I never expected to spend this much time on V2000 support.

When everything fails, fresh tactics:

https://1drv.ms/u/s!As-dKk-N73dSmBAMo-Zu9Ad0nTvO
MD5: 58aec0d64b4a10e94a5368e33fc51a57

Delete redline.dll and verite.dll fromt eh Formula 1 folder.

Copy V1rite.dll and R1dline.dll and f1red.v2k.exe to the formula 1 folder. (Refresh.txt should be still valid (untested)).
Run f1red.v2k.exe.

See if it works and attach the logs if it crashes.

I think the problem was a memory allocation issue. Each dll had its own heap. With this build they all use system verite.dll's heap.

unfortunately , black screen before race
can we be somehow sure it's not exe or OS fault?

Just to be clear, you deleted redline.dll and verite.dll from forumula1 folder and copied in V1rite.dll and R1dline.dll and then ran f1red.v2k.exe?

[EDIT] From the logs it does look like you ran it correctly.

Don't know. But it works with a custom (semi-F1 mode) build of RReady.

OK, this is now on the backburner.

yes done it right way

Something in the cmd buffer causes problems. It does something which might not have an immediate effect.

RReady had problems with paletted textures and crashed as soon as the race started without rendering anything.

I might have to resurrect the custom texture loader.

I can't let sleeping dogs lie:

https://1drv.ms/u/s!As-dKk-N73dSmBUMo-Zu9Ad0nTvO
MD5: c7c0dc5692a61a814fdc0a52ea2360a4

The menus should be corrupted, but see if the demo starts up.

[EDIT] Oh and run f1red.v2k.exe.