Performance Recommendations for 1.6

Hey,

First all LOVING the update! Awesome job and congrats to everyone at Reiza.

Anyway, I have a modest setup RX6600, 32 GB Ram and a Ryzen 5600X. Game always ran well, on mostly medium settings. Just wondering what are the biggest performance hogs now. I've noticed some choppy spots at Le Mans in any conditions, and some rainy tracks with large grids. I'm assuming that cars on track is a resource killer (hadn't needed to set a max visible cars on track before but the grid has expanded by 16 cars so I assume I may need to set it in the 30's). Curious if anything else has changed that could impact performance.

Also was there talk of modifying visible cars in the mirrors?

 

I find having both reflection to medium and grass off is enough to bring the beta back to the same performance as the main game, but the main game i can run them maxed.

 

I did a total fresh install and my frames have also taken a massive hit. I don't think I hit 90fps at all in any lobby last night, always juddery. I have my settings a little lower than what I have run for years but still couldn't get performance. Sebring was 30fps the whole time, I had to leave.

Though maybe it's not AMS2, I'll troubleshoot today. I did go onto the latest nvid driver at the same time, maybe I still need to run the old recommended one. I had issues lately with VD so went into Pico connect wired but both don't run the game smoothly now. Even the image was not clear like before.

I really hope vr wasn't spoiled I was hoping my 3090 would do another year.

 

I have a 3080 laptop and it runs just as well

 

I have only seen a significant performance hit on the new tracks, Sebring is particularly taxing. Perhaps Reiza will do an optimization pass on it at some point. Turning down track detail helps a little.

 

Cheers Khalid, are you running W10 or W11? I'm just about ready to sack W11 for VR. I toggled hags and game mode back off and I seem to be back into 80 frames. I don't think the game is the issue but Sebring must be really heavy considering the slide show I had.

 

So yes sebring can get a little heavy especially when you get to the open area close to the back straight but is still good. Kind of like the run down to eau rouge at spa and parts of le mans. I literally updated from 23h2 to 24hu and it works very well. On latest Nvidia drivers with game mode on and hags off. Do note, I think a big difference between us is i am using a cable instead of Wifi like you did before

 

Thanks for the feedback, tinkered around a bit and it seems like the max visible cars on track has the most impact for me right now. Le Mans is way better with only 36 visible cars (good enough). Only other thing I'm seeing is a big performance drop during starts and FCY's (seems fine once things are green).

 

most of the cars are bunched up at that time, so bigger performance hit

 

I have Ryzen 5 7600X and RX 7800XT and have seen a bigger performance hit than I expected with the 1.6 update.

All of my settings are at high/ultra (except for grass and particles at medium) and I still hit 72fps (locked) with ease. I’ve just seen my GPU usage go from 60–80% during a race to 65–90%.

The new tracks are especially heavy on the GPU. I see GPU usage spike from 45% to 90% turning onto the back straight of Mosport.

I do hope we see further optimizations in coming months!

 

I recently noticed that even though my setup was a single screen in the triple screen options something was enabled. I disabled it and saw a boost in performance.

 

Holy sh**, this worked.

Triple screen was enabled in my options. I turned it off and watched my performance in high-stress areas drop from 90% to 75% — should we file a bug report about this? It seems triple screens are enabled by default in 1.6.

 

For me it seems I get the best performance on the first session of the first track when I load up the game. As session advance or I load up another track, or restart the same one my performance drops off, the more I do this the worse it gets.

I'm on a single screen and turning off triple screen spanning made no significant difference for me. I am pretty sure on a single screen any triple screen options have no effect, only a dev can tell us for sure. Also when you enter a race, then exit it shows that it is enabled again.

These lines are in the triplescreen file.

<prop name="ForceTripleScreen" data="false" />
<prop name="AllowTripleScreen" data="false" />

 

This is fascinating to me!

I tend to leave RivaTuner Statistics up as I’m very sensitive to frame pacing issues. I'd rather have a locked 72 fps than an inconsistent 100 fps. The performance gains I saw this afternoon weren't placebo.

The "Triple Screen Settings" had the "Span Three Screens" (or similar) option checked when I opened up the options this afternoon. I unchecked it, clicked save, and was told to restart the game to see the changes. My GPU usage dropped dramatically.

Prior to the changes, sitting on the starting line at Sebring with a 45 car grid had my GPU at approximately 70% utilization. It was 58% after the change. I’ll continue to tweak but I'm very curious.

One thing is for sure, though. Replays are MUCH more taxing than before. I can race at a smooth 72 or 84 fps locked but replays often dip into the high 50s.

 

Yes, I noticed this also. GPU load at 50-70% in race / GPU load at 85-98% in replays.

 

Have you gone back and looked at the same setting? Because when I uncheck it enter a race then leave and go to the settings it is checked again, even though I saved it unchecked.

 

Hi what can I change to improve fps in sunset? Always get a dip then, I’m guessing shadows and reflections which I have already lowered. There’s no setting anywhere for amount of headlights is there?

 

For you guys that turned off triple screen spanning, did it stay off? I just tried it and everytime I relaunched AMS2 it was re-enabled

 

It stays on, which seems to be a bug. If you look at the triplescreensettings.xml in Documents/AMS2 shows it is off.

<prop name="ForceTripleScreen" data="false" />
<prop name="AllowTripleScreen" data="false" />