12 replies to this topic

[Purojannu]

I'm usually having 36 fps steadily, but sometimes when I enter the car it's only about 30 fps which makes driving distinctly more difficult. If I exit and then re-enter it's usually 36 again. The fps never changes much when I'm driving. My computer should be fast enough to run 60 fps on most tracks so that's not the reason for this problem. I'm not sure, but maybe this started after Windows 10 update. Does anyone know if there is something to do?

[gliebzeit]

Max fps with standard GPL is 36.  With brr's patch there is 60 fps ... with wonky AI behavior.

If you have a 64-bit OS and at least 8 GB system memory, then patch your "donor" (before patching by GEM+) gpl.exe file with the 4GB patch utility.  This will allow more graphics textures to load before the Windows swap file is accessed.  It usually requires you to drive at least one lap of the track (practice or race) to 'load' all textures that your system is capable of holding... from then on less 'stuttering' will be noticed.

http://www.ntcore.com/4gb_patch.php

FPS may still drop depending on your personal system, "heaviness" of a track's polygon count / textures and the "heaviness" of an Add-on Mod's car polygon count / textures.

Edited by gliebzeit, Jan 15 2018 - 03:12 PM.

[Purojannu]

Thanks. I'll try that patch when I understand how that is done. I just can't see any logic why fps is sometimes 36 and sometimes 30, and I didn't have that problem earlier.

The patch wasn't too difficult to use. I tried Spa67 with 20 cars, 36 fps, but then sometimes it can be 30 when practising alone at some more normal track. So nothing changed.

Edited by Purojannu, Jan 15 2018 - 04:02 PM.

[ginetto]

I'm just guessing here but
Are you sure is not some other program that start running in the background?

[Millennium]

The 4Gb patch worked good for me in the past. Before it I also had low framerates on Spa '67 with the 1955 mod (14 cars) and it defenitely wasn't my gpu/cpu.  

But switching between 36 and 30 sounds like there's some sort of double-buffer vsync active which locks the framerate to 30 as soon as it drops. Do you happen to have it enabled somewhere in GEM+2 or your gpu driver?

Edited by Millennium, Jan 15 2018 - 04:36 PM.

[Michkov]

Check the Vsync first, if that wont help try running the other rasterizer D3D7v2 or OGLv2 whatever you are not using atm.

[twinpotter]

I found (not sure if coincidence) that removing the black bars with the letterbox patch helped.

Also cutting down the on screen pribluda info (if used) and moving to a lighter pribluda.

As well as the 4GB patch (Gliebzeit)
Also check background programmes running (Ginetto)

All helped my performance.

TP:

[Purojannu]

Thank you all for your help! I disabled vsync but it didn't help. Changing the rasterizer is not an option because with Open GL I have even worse problems.

Yes, I use Pribluda and it shows the fps. Maybe every fifth or tenth time I enter the car the fps is lower. I don't have to drive a meter to notice that and I know it won't change during driving. Maybe one time the fps dropped during driving and then remained at 30.

[Purojannu]

Problem seems to be solved! I enabled triple buffering and changed the rasterizer. Now Open GL works, no 30 fps and much better looking Pribluda as a bonus.

[gliebzeit]

[John Woods]

gliebzeit, on Jan 15 2018 - 05:59 PM, said:

And the new rasterizer is?

[Pete Gaimari]

John Woods, on Jan 15 2018 - 06:08 PM, said:

gliebzeit, on Jan 15 2018 - 05:59 PM, said:

And the new rasterizer is?

He told us. Open GL.

[John Woods]

Pete Gaimari, on Jan 16 2018 - 03:50 PM, said:

John Woods, on Jan 15 2018 - 06:08 PM, said:

gliebzeit, on Jan 15 2018 - 05:59 PM, said:

And the new rasterizer is?

He told us. Open GL.

Thanks Pete.
Sorry, not all that up on OpenGL.
If only one version that makes it easy.