Monaco

[Clayton Nelmes]

where can i find that icon? i don't have a shortcut if that's where it is.

 

[David Dominguez]

You need to create a shortcut (right click into rfactor.exe --> send to --> desktop(with shortcut)). Then you will have the shortcut in your desktop.

 

[David Dominguez]

Well or just right button into rfactor.exe --> create shortcut, then you will have the shortcut in the same folder as the .exe.

 

[Clayton Nelmes]

Tried it i didn't really see an improvement unfortunately. Just make sure i don't start last!

 

[David Dominguez]

Do you have a multi-core processor ?

 

[Clayton Nelmes]

AMD athlon 62 X2 duel core processor +3600 whatever that would be haha.

 

[Ryan Callan]

Regarding holes in the guardrails, our track team will try to fix these, but since we only have one person who does the actual editing of the tracks, it is unknown whether he'll have time to do all this.

In any case, should we need to change tracks, we will do so on this Sunday at the latest, to ensure that everyone would have enough time to get used to the other Monaco version.

It's not that the guardrails have holes, it's the way Codemasters built them which causes the issue when converted. You would have to build a none-rendered collision wall all the way round, a la default ISI tracks, but you do need half decent modelling skills and the correct software to do this.

The problems will not necessarily be FPS, but the overloading of RAM resulting in CTDs for many people, as the GMotor engine is designed to only handle 1000polys per GMT (then you can have as many GMTs as you like), when of course Codemasters converted tracks have more.

 

[Mikko Puumalainen]

Link for information regarding the test on Saturday.

 

[Atze Kerkhof]

I tried the fullproc and my frame rate went from 150 to 400+! big recommendation. thanks for this.. although i believe the FSR manager automatically runs on fullproc..

 

[Johannes Kunkel]

I tried the fullproc and my frame rate went from 150 to 400+! big recommendation. thanks for this.. although i believe the FSR manager automatically runs on fullproc..

it doesn´t automatically but it at least makes it very easy to use the fullproc command.

 

[Clayton Nelmes]

I tested fps. When racing around last with 25 cars infront i get about fps 5-15 lap 1, that's with full display settings all of that. When i tried the fullproc it only goes to about 10-20 fps still heeps of lag but a tiny improvement. I even tried the settings so basically all low/medium and it only improved to about 20-30 average fps. So basically i'm gunning for a good starting position haha

 

[Joona Lappaenen]

I've made similar conclusions, lowering gfx-settings isn't helping much if at all when there's traffic. Considering that I can run any other track with full gfx it just doesn't seem right to me

 

[Clayton Nelmes]

That's the exact same for me. Everywhere but monaco i use full with no problems.

 

[Ivar Kalamees]

Its weird, cause I have no problems what so ever on the grid with 30+ AI's with almost maxed gfx and fullproc. FPS is over 80.
My FPS on the other tracks is around 120 with most of the gfx settings on medium.