The 1955 F1 Mod For Grand Prix Legends Is Released

[Clive Loynes]

Not had the chance to do anything yet but the system is as follows:-

CPU: AMD Athlon 64X2 5400+

Motherboard: Pegatron Computer INC. M2N-VM1394
Mobo Chipset: NVIDIA nForce 560 Rev A2
Southbridge:  NVIDIA nForce 630a Rev A2

Memory: DDR2 Dual Channel 4 GBytes

GPU: NVIDIA Quadro 600

I use Direct3DV2 but I don't seem to have gplshift or no-letterbox patches.

[Cookie]

This is a very low end system for the modern tracks...
Use the Openharwaremonitor plot to see what happens when racing.

First you have to make shure that the CPU does not use any eco downthrottling.
You could use the PhenomMsrTweaker v1.2 to handle it.

Same has to be made for the GPU, set a profile for GPL...


 

[Clive Loynes]

This is a very low end system for the modern tracks...
Use the Openharwaremonitor plot to see what happens when racing.

First you have to make shure that the CPU does not use any eco downthrottling.
You could use the PhenomMsrTweaker v1.2 to handle it.

Same has to be made for the GPU, set a profile for GPL...


 

I have the hardware monitor running but the Phenommrstweak says:
"This installation package is not supported by this processor type.  Contact your product vendor."
when I try to install it.  Have I got the wrong download?

[Cookie]

No, the CPU seems not supported...

So you should try to disable "Cool & Quiet" in the bios to run the CPU in full speed.

[Clive Loynes]

No, the CPU seems not supported...

So you should try to disable "Cool & Quiet" in the bios to run the CPU in full speed.

I think that I have already done that but I will check.

[Cookie]

You can check it by running a 0-race with some AI's,
then look in the HWmonitor plot for the CPU and GPU frequencies and load during the race.

[Clive Loynes]

You can check it by running a 0-race with some AI's,
then look in the HWmonitor plot for the CPU and GPU frequencies and load during the race.

Well it says "Disabled" in the BIOS.

What is an "0-race"?

I tried reducing the screen resolution to 1440x900 and changed GEM to match but it didn't seem to make any difference to the fps figure when in the pit lane at Spa67.

[Cookie]

0-race is a single race in GEM (german language)

You should do one and record the CPU and GPU behaviour in the plot and show it here like this
https://picload.org/view/rwdwogwr/hwm.jpg.html

PS

TBH, I am pretty shure that your hardware is way too week for tracks like Spa67 and 60fps anyway...
GPL is special, it wants a fast bus connection CPU to GPU, 90% of the graphics load is done by the CPU!

[Clive Loynes]

You should do one and record the CPU and GPU behaviour in the plot and show it here like this
https://picload.org/view/rwdwogwr/hwm.jpg.html

PS

TBH, I am pretty shure that your hardware is way too week for tracks like Spa67 and 60fps anyway...
GPL is special, it wants a fast bus connection CPU to GPU, 90% of the graphics load is done by the CPU!

I guess I knew that the system wasn't up to it but I can manage if it only drops to around 30fps.  It's when I get to single figures that I'm in trouble!

So far the trick of displaying anything on the hardware monitor plot is a complete mystery!  I can look at the values on the "Gadget" but can't plot anything.  :-(

[Cookie]

Go to View -> check "show plot"
Options - plot location - bottom

Then you get checkboxes for load, clocks and temps of CPU and GPU

[EvilClive]

FWIW Clive, regarding the 55's. As Axel says GPL relies heavily on the CPU for its graphics performance and it all comes down to the motherboard and main processor and if you have not got the grunt there, then you are going to struggle. I might try some of the checks that Axel has suggested to see if I can squeeze a little more life out of my creaking equipment.

Spa 67 ( and most other circuits with a high graphic content ) causes my system to seriously struggle at the start of the race and for most of Lap 1, or until the field spreads out.
At Spa 67, I usually get 20-24 FPS during qually just sitting in the pit lane  and  only 10-12 FPS on the grid and through Eau Rouge. That makes a little stressful as cars simply jump about until things string out a little. Even after several laps I know I won't see 60 FPS at anytime during the race, usually my best is around 50, maybe 55 if the track is empty ahead. My only hope is to qualify close to the front and hope to reduce the number of cars visible ahead.

If we start talking the GT's or Can Ams in GPL, then 8 FPS on the grid is quite normal for my system. and even running in a 60fps race I will be lucky to see 36fps at any point.

I am seriously contemplating a new PC as mine is about 10yrs old now. 2.3Ghz with 2 Gb ram. A Hard disk that is full does not help either as I constantly have to delete stuff to maintain the Windows XP swap file size

I have upgraded the graphics card to a Nvidia 56** and at some point I put in a larger PSU.
Basically, I have been putting Band Aids over the problems and this has been highlighted now that I run some GTL races where they expect 120FPS as normal and I am getting as low as 30 FPS in places.

[Clive Loynes]

Good to know that you are suffering too!   

I have managed to run the hardware monitor and plot the results now but on my first attempt the computer crashed just after Masta on the out lap.

[miner2049er]

A Hard disk that is full does not help either as I constantly have to delete stuff to maintain the Windows XP swap file size.

You can set a fixed size for that.

Once you have you can defrag so as much of it is contiguous on the drive as possible which helps with performance.

I usually set it to double the amount of RAM.

[Cookie]

Sometimes it helps to use a program like CCleaner to delete all not used files.

[Clive Loynes]

I've done some more testing and it appears to me that the system in't great but it is working well enough until something hijacks the CPU.  I have now observed it happening off-line as well as on-line.

I have tried shutting down everything that I can but it still happens.  I'm just going to do a virus and malware sweep to see if it finds a bug!