08-03-2022, 09:25 AM
Ricknau, post: 31006, member: 230 Wrote:I thought you might be onto something. I didn't think to try that. But no... still sucks. Just too much detailed surroundings I guess, that don't drop out with settings on low. There are a few sections along the way where it normalizes but then turn a corner and wham!... 40fps again. Definitely happens down long straights where the sight line is long. The track developer just needs to work on it a bit more if he even cares.I think the 1988 F1 track pack was last touched a year or two back - so no updates likely.
It’s always been a bone of contention for me that race-day in particular gets loaded up with extra crowds etc. at most tracks.
When Cruicky raised the issue of clouds suddenly appearing if the track height reached a certain altitude, I posted something related asking why the ‘clear skies’ setting partially clouded over - and S397 basically implied that allowing the user to actually cut out graphical detail to a level that allowed their hardware to run well was a step too far away from ‘simulation’…
My rig (2080Ti, Rift CV1 - but only 4-core i7 4770K - released *eight* years ago!) is also CPU limited (ACC is a complete no-go area - especially in VR but also just on screens) but I have no way - or real desire just now - to fund a mobo/cpu/ram/(cooler?) upgrade.
As an aside, if you‘re ever racing against AI cars, you might find some heavier on CPU than others. There’s a setting buried within mods which determines how often to update the AI physics. Mod developers might over egg this (I’ve turned it down one click in the GTPC BMW M1 SR4L_LE mod) and burn CPU time. There’s a subsidiary option that lets the AI run a lower CPU physics update rate - but to increase it temporarily if the AI are turning a corner more sharply than a certain yaw rate. It all adds up to an ability to either create really clunky Ai or to bring your rig to a crawl
