Cleaned up. This should be faster because error message generation is gone. Even though the messages weren't being logged, they were being generated. This build eliminates the most severe of them.

A few more safety checks can be eliminated if this works:
https://1drv.ms/u/s!As-dKk-N73dSmD71pdtgE96Cvmfg?e=pNa8jn
MD5: 4bf8924d9a6bf51b021ccff175793bdb

If this works, I'll remove all runtime checks (they should be checked during load and not everytime a functions is called) and post the source..

Completely logging and runtime safety check free build:
https://1drv.ms/u/s!As-dKk-N73dSmD8r15pQIiWe_Ck1?e=Uj9cgP
MD5: c2f3619f0b91d45288054bd9d9f866628e73070b

Source:

Alternate link:
https://1drv.ms/u/s!As-dKk-N73dSmECyo30Wel1htHIJ?e=shxNTH
MD5: da10af09fd5e75151d7d19a564f982f8

And once again, apologies Chucky,

Also @Raven-05, you asked what microcode does.

It's a more powerful form of a shader. On a modern GPU a shader can control geometry generation,/calculation, texturing, tesselation and that sort of thing. Shaders can't really do subroutines and bunches of them have to run the same code (Compilers allow limited subroutines to be written but when compiled they're not really subroutines). If one of them takes branches differently (i.e. if, else) the entire run of the shader cluster has to be repeated for every branch in every single individual shader. Results from shaders which didn't take the branch are discarded using a mask. They're what's known as SIMT (single instruction/multiple thread) because entire clusters of shaders share the same program counter.

Verité microcode is single shader (single core) but supports dynamic branching and can communicate with the CPU directly including generating hardware interrupts (forcing the CPU to stop what it's doing and dealing with something. Once it's done execution will resume from the point of interruption).

o wow, i always thinks Verite is advanced, and i feel its capable of shaders.
beside of missing tires, credits also glitchy https://fex.net/s/somn9dd
thank you very much! Great , well done =0

Do the credits and tyres work with the previous version?

[EDIT] NO they don't. It's probably a bug in the wrapper, possibly z buffering mode.

Z-buffering's done differently on V1000 and V2000.

Z buffering looks correct. Not sure why it doesn't work. Will check in abit.

Try this:
https://1drv.ms/u/s!As-dKk-N73dSmEJtb1xypjNmxBCj?e=3HQuwO
MD5: b8221c703d71e0ffbc435531a89e17ea

I disabled the VL_Tristrip_ command during testing:

1__declspec(naked) __declspec(dllexport) vl_error V_DLLIMPORT VL_Tristrip_()
2{
3	__asm {
4		mov eax, VL_SUCCESS;
5                ret;
6
7		pushad;
8
9		mov cmdbuffer, eax;
10		mov v_type, edx;
11		mov vert_count, ebx;
12		mov vert, ecx;
13	}

These two lines need to go after line 2611:

1		mov eax, VL_SUCCESS;
2                ret;

If this works I'll post the source again.

Verite's microcode was pretty advanced back in the day. You probably could run modern shaders on it, but the VRAM area for microcode is very small., unlike modern stuff so you'd be constantly have to upload firmware. I don't know the internal architecture of modern GPUSs apart from marketing block diagrams and the high level interpretation in glsl (OpenGL/Vulkan), but you could generate fresh geometry algorithmic ally on verite. Also there's only a single core/single thread so it'd be very slow. Verité might not scale that well to multiple cores.

Intel tried a decade ago to build a gpu using cpu cores but gave up. The fruit of their labour was knight's corner/xeon phi and it wasn't a gpu after they built it.

It's hard to build a gpu using general purpose cores.

Credits excellent.
Race Demo Excellent.
QuickRace Excellent.
Well Done.
Final.
Congratulations).
This Video https://fex.net/s/dtlfkty
Deserves to be on your yt channel, if you want too))
Any way i can recapture it in other format if you want)

You can have that video. I don't have a verite board and besides you and chucky did all the painful slow-mo testing.

5 months to get this going, that's too long. I should've tried the microcode sooner, as soon as chuky brought it up.

Thanks. One down and speedy 3d to go.

ok, i think would be cool to post all working stuff on first post of this topic (edit it)
)

What kind of framerate do you get and how does it compare to v1000?

RaVeN-05 wrote on 2024-03-13, 10:45:

ok, i think would be cool to post all working stuff on first post of this topic (edit it)
)

Will do.

sharangad wrote on 2024-03-13, 10:48:

What kind of framerate do you get and how does it compare to v1000?

idk, i don't know the way to count it.
But playing manually is ok , very playable.
we can oly compare to Gona's video
https://www.youtube.com/watch?v=KVmBDoU1NfA&a … _channel=gonaeu

by my eye's (my pov) v2200 performs a little faster

Posted on first page.

It should also work on A V1000 with regular (non-F1) drivers.

Oh and test rainy conditions. A regular race with the weather changed to rainy to see if everything still renders correctly.