my VR was freaking out. My view point was jumping all the time for a split second to outside the car. I almost puked every lap.
Otherwise the front group was very strong and I only finished 2nd because if mistakes.
Amazing race otherwise
Post your streams!
I'll check it out man, thanks!Dan I have had that before ..it was one of my sensors playing up because of its position.
Yes for sure!A question, if anyone can help? Had to turn everything down to such an extent (inc a frame rate of 28!) it was like playing Ayrton Senna's Super Monaco GP, could this be because of the track being a mod?
I'll check it out man, thanks!
What tires strategy were the front group running? I ran medium-medium and I suspect one set could last the entire race with decent laptimes at the end.
Sounds like it's the CPU indeed. I'll have a look into the bathurst rendering stats during the next days and come back to you with some dataHiya Rasmus, thanks for your reply and hope this is what you're asking for... I have been told that my cpu is throttling performance so hope to upgrade soon - no idea what to though
Regarding running apps, the only ones I use are Helicorsa, FFB Clip, Sidekick and the Teamspeak app
Time of this report: 8/19/2018, 23:25:51
name of this pc:
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.170913-0600)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 08/28/12 14:06:14 Ver: 14.01
Processor: AMD FX(tm)-6100 Six-Core Processor (6 CPUs), ~3.3GHz
Memory: 8192MB RAM
Available OS Memory: 8174MB RAM
Page File: 3392MB used, 12954MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
Display Devices
---------------
Card name: NVIDIA GeForce GTX 1050 Ti
Manufacturer: NVIDIA
Chip type: GeForce GTX 1050 Ti
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1C82&SUBSYS_A45419DA&REV_A1
Display Memory: 4095 MB
Dedicated Memory: 3072 MB
Shared Memory: 1023 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: GF276
- MSAA up to 8x
- Pixel Density 1.5
- Post Processing Effects
- Smoke
- Reflections
- Mirrors
- World Details above low
- Shadows
- Resolution above 1280x1024 (for VR)
- In-game Apps! some apps kill performance just by being installed and activated on AC settings. Test one by one to find them.
- Reflections static (Use contentmanager to drop render distance down to 60meters.
- Mirrors low (Use contentmanager to drop mirror render distance down to 250meters in SYSTEM
).
- Essentials app
- realtime app
- Leaderboard app
- TrackMap Display app
- Protyres app
- Substanding app (horrible. drops 30fps just by being installed into AC)
- fuel usage app
- Fuel usage (mini)
- Standard AC track map app
- Standard AC race position app
- Standard AC lap timing app
- Standard AC tyre app
I ran softs the entire time, changing them at the pits along with fuel, I unfortunately over fuelled. I’m pretty sure if I didn’t mess up and push as hard as I did I probably could’ve got 2nd or 1st, I came 3rd. I’m pretty sure I got the fastest lap time as well. The soft tires also lasted long enough to still be as fast or faster than others in the corners and hairpins. Hopefully that answered your question! @Dan Costa
Thanks for sparing me from searching & copying my past posts once againYeah, AC cpu performance is a pet peeve of mine. I complain about it all the time in the oficial forums.
Funnily enough, I spent the entire sunday afternoon troubleshooting what eats CPU performance in AC in order to keep VR stable at 90fps with 28 cars just for this race.
My baseline to test performance was a replay from a 24 GT3 car real online race @ Vallelunga. It dips down to 40fps and struggles to stay above 70fps in VR. It was the worst race I ever had performance wise.
These settings did not affect CPU performance and can stay ON (if your GPU can handle them):
These settings absolutely murder CPU framerate
Disabling all of the above improved the dips from 40fps up to 75fps. Not Enough.
The trick to have a locked 90fps is to enable an option you can find in ContentManager, called:
After enabling the setting above, I found I now have free CPU resources to activate some of the settings above, albeit with low quality only.
Now that I have mirrors working (!!!!) at a stable 90fps, I'm almost done. I only needed to activate some important apps. And this was troubling. All these apps had a negative effect.
I found that I could only use these simultaneously, barely.
These are the settings that allowed me to race @ 90fps in VR 27 cars in bathrust. If these settings work in VR, they work in single-screen too.
And for the love of god, do not install MSI Afterburner. Ever.
The CPU is a 2700X with Hyperthreading OFF and only 4 cores active @ 4.3ghz. Every trick counts!
Cheers
Awesome job Dan, thanks for taking the trouble to share thisYeah, AC cpu performance is a pet peeve of mine. I complain about it all the time in the oficial forums.
Funnily enough, I spent the entire sunday afternoon troubleshooting what eats CPU performance in AC in order to keep VR stable at 90fps with 28 cars just for this race.
My baseline to test performance was a replay from a 24 GT3 car real online race @ Vallelunga. It dips down to 40fps and struggles to stay above 70fps in VR. It was the worst race I ever had performance wise.
These settings did not affect CPU performance and can stay ON (if your GPU can handle them):
These settings absolutely murder CPU framerate
Disabling all of the above improved the dips from 40fps up to 75fps. Not Enough.
The trick to have a locked 90fps is to enable an option you can find in ContentManager, called:
After enabling the setting above, I found I now have free CPU resources to activate some of the settings above, albeit with low quality only.
Now that I have mirrors working (!!!!) at a stable 90fps, I'm almost done. I only needed to activate some important apps. And this was troubling. All these apps had a negative effect.
I found that I could only use these simultaneously, barely.
These are the settings that allowed me to race @ 90fps in VR 27 cars in bathrust. If these settings work in VR, they work in single-screen too.
And for the love of god, do not install MSI Afterburner. Ever.
The CPU is a 2700X with Hyperthreading OFF and only 4 cores active @ 4.3ghz. Every trick counts!
Cheers
Thanks for sparing me from searching & copying my past posts once again
Says everything, thank you!
One thing though: what problems did you encounter with msi afterburner?
For me it's one of my core elements on my PC. Best monitoring, ingame overlay Overclocking tool and with the complementing Riva tuner the best fps limiter out there.
I read about problems with VR and with windows 10's full-screen optimizations though.
Thanks for your reply RasmusSounds like it's the CPU indeed. I'll have a look into the bathurst rendering stats during the next days and come back to you with some data
To have something to compare with, could you tell me a Kunos track that runs perfectly fine and maybe one that is on the edge? I know the official tracks are not cometely the same too...
Remember though that AI eats away the cpu while multiplayer doesn't. For me it's around 10 AI = 24 online.Thanks for your reply Rasmus
I have always run all other tracks with fairly medium, but perfectly acceptable settings (never have smoke enabled though), frame rate of 65. For example, other mod tracks with a grid of 24 cars didn't give a problem - Le Mans and Paul Ricard all ran fine, for example. So this is the only track that's been nearly impossible to run
The only difference between the above examples and Bathurst was a grid of over 24 cars - the biggest number I've encountered before last night, maybe that's the hair that breaks the camel's back for my CP?
I'll try Okayama tonight with 24 AI cars and my usual settings, fingers crossed Bathurst was a glitch in the space-time continuum and I can enter next Sunday's race
edit: probably not important and obvious, but just before the pc crashing the '99% cpu warning' popped up, only time this ever happened was when I first used AC back in January, and had everything on max settings, which I soon learnt it won't cope with
Wow, I wasn't aware AI is worse than multiplayer, my cave-man computer skills would say the opposite I spent all Sunday afternoon racing against AI trying to reduce settings to get rid of cpu warnings, no wonder my eyes are like p1ss holes in the snowRemember though that AI eats away the cpu while multiplayer doesn't. For me it's around 10 AI = 24 online.
Thanks for the info, I'll report back about bathurst performance
Wow, I wasn't aware AI is worse than multiplayer, my cave-man computer skills would say the opposite I spent all Sunday afternoon racing against AI trying to reduce settings to get rid of cpu warnings, no wonder my eyes are like p1ss holes in the snow