yes old build is 26 fps max at starting position of Scorched planet vs 33 fps max at last build.
DMA still faster
Try adding this to the joystick section. On dual core machines this needs to be added. I don't know what the situation will be on your machine.
[joystick]
multithreaded=false
Early Attempts to test Formula 1:
The game can be installed trough otvdm , thanks.
And it seems could not detect Randition, and doesnot installs f1red.exe file.
So i extracted it by UniExtract Tool a archiver which supports way nearly all archive types.
placed f1red.exe into newly installed formula1 game and ready to go.
in Game:
Performance variety goes from 19 fps, average 35 fps, max 60 fps(vsync).
The game seems rendered perfectly.
Only suspicious 2 things:
Wheels at far distance on foggy weather , not fogged , stays dark .
Cars very rarely 'jumps' off of their positions a little bit up.
RaVeN-05wrote on 2025-12-06, 17:04:Early Attempts to test Formula 1:
The game can be installed trough otvdm , thanks.
And it seems could not detect Randition, and […] Show full quote
Early Attempts to test Formula 1:
The game can be installed trough otvdm , thanks.
And it seems could not detect Randition, and doesnot installs f1red.exe file.
So i extracted it by UniExtract Tool a archiver which supports way nearly all archive types.
placed f1red.exe into newly installed formula1 game and ready to go.
in Game:
Performance variety goes from 19 fps, average 35 fps, max 60 fps(vsync).
The game seems rendered perfectly.
Only suspicious 2 things:
Wheels at far distance on foggy weather , not fogged , stays dark .
Cars very rarely 'jumps' off of their positions a little bit up.
Ok, I'll test this on the v2200 tomorrow. The v1000 still has issues rendering file explorer, randomly locks up, with rredline drivers. I saw a post here where someone said v1000 struggles to render the desktop with the full acceleration slider set to max on an Athlon xp, but works fine on older, slower cpus.
RaVeN-05wrote on 2025-12-06, 17:04:Early Attempts to test Formula 1:
The game can be installed trough otvdm , thanks.
And it seems could not detect Randition, and […] Show full quote
Early Attempts to test Formula 1:
The game can be installed trough otvdm , thanks.
And it seems could not detect Randition, and doesnot installs f1red.exe file.
So i extracted it by UniExtract Tool a archiver which supports way nearly all archive types.
placed f1red.exe into newly installed formula1 game and ready to go.
in Game:
Performance variety goes from 19 fps, average 35 fps, max 60 fps(vsync).
The game seems rendered perfectly.
Only suspicious 2 things:
Wheels at far distance on foggy weather , not fogged , stays dark .
Cars very rarely 'jumps' off of their positions a little bit up.
There's also a problem with the water spray texture from the rear of cars under wet weather not being sized correctly sometimes. I'm going to try to fix that today.
The cars jumping *might* just be LOD for the model changing. On real hardware it changes, but the framerate is low so it's less dramatic. I'll also see what's up with the fogging on the wheels.
Early Attempts to test Formula 1:
The game can be installed trough otvdm , thanks.
And it seems could not detect Randition, and doesnot installs f1red.exe file.
You have to tick the checkbox manually for all the versions you need. I reinstalled this earlier today, on my W98 machine, because the F1 wrapper, (RReady.V2k), wouldn't work with the reference drivers. I had to revert to Diamond drivers to get this to work. I should probably update the thread F1 V2k.RReady thread.
1Each of the INT n, INTO, and INT3 instructions generates a general-protection exception (#GP) if the CPL is greater than the DPL value in the selected gate descriptor in the IDT. In contrast, the INT1 instruction can deliver a #DB
This seems to be preventing me from patching bits of code out of ICR2.
It also seems to block port IO, this also throws an exception without every calling my code. There doesn't seem to be any bits of empty space to add code.
compared two videos:
Yes everything rendered correctly.
The game rarely CTD.
Do not use Alt+tabbing. Hangs app.
Rarely tire trails on asphalt gets corrupted texture.
Rarely shadow under cars gets corrupted texture.
The performance is variable fps.
Sometimes tire trails seen trough road.
Sometimes water splash effects has seen trough other polygons. Those two probably not fixable due to nature of how Rredline API works.
The game rarely CTD.
Do not use Alt+tabbing. Hangs app.
Thanks Raven for taking a look.
Having task manager running does the same thing, such as when starting a race.
On newer faster CPUs, F1 runs at a solid 60 fps. I think there was a user here who has a 14the gen Intel CPU who gets a solid 60 fps everywhere. It's mostly CPU bound.
There is a problem with the water spray texture having the wrong size. It's intermittent and I have trouble reproducing it. I also can't tweak the performance of this game. Profiler's crash because of the mixed calling convention.