Hi, My system was working really nicely with the new build. Increased FPS, more AI, increased graphic settings. My PC had a blue screen today and when re started my JSON files (player, controller, multiplayer) were blank. No problem I copied in my backup JSON files. When I started RF2 and went to drive the purple physics bar was maxed out and the sim was dropping out of real time with the associated loss of FFB. When I turn off my wheel (OSW) the bar drops to 50%. Turn the wheel back on and it's maxed out again. Any ideas are appreciated.
I had some overheating issues when my CPU kept throttling. That's the only thing I can suggest for a sudden change.
Isn't the purple bar actually CPU usage? I had this in the past with that CPU spike issue build - when the cpu maxed (or purple bar either way) out the green bar produced a histogram, kinda looked like a waterfall effect. That histogram is when game come out of real time I believe, and for me it happened when CPU maxed out 100%
@AMillward @hardtohandle @Will Mazeo Thanks for your input gents. AM, Yes it might have been heat so I dusted the heat sink. It was dust that caused it once before. However after dusting it now wont even boot!!!!!! HTH Yes the CPU is indicated by the purple physics bar graphics (GPU) by the green bar. Will, once I get it back from the shop Ill check that.
Yeah. Depends on how full that bar was on old build. Aint sounding too good for the CPU... It's normal for the purple bar to drop a lot if you unplug wheel. Same as hitting I on track for ai control, drops it right down.
@davidporeilly If I were you, cleanly uninstall RF2 and then reinstall it and reconfigure it as you have for years.
Unfortunately at this point my pc won't even boot. Suspected hard drive failure. Been getting some blue screens lately. Dropping it in for repair today. What is daunting is the prospect of the amount of stuff I will need to reinstall when I start to think of my OSW wheel, plugins like Motec, Realheadmotion, Dashmeter Pro. Not to mention loss of all setups from settings file. Some of this stuff I might have on a usb stick. Oh well, 6 years with this PC.
SOLVED Thanks for your input gents. PC wouldn't boot due to a cable unplugging itself. So back up and running. To the original issue.... I suspect it was the controller JSON line suggested by @Will Mazeo . It was after I had to copy a backup JSON across that it occurred. Once I set that to "True" problem fixed. Happy and relieved here, and have updated my backups in my USB to include more stuff like plugins!. Cheers.
It puts the FFB process in another thread instead of keeping it together with the physics as sometimes it cause issues, kinda like the physic is paused to send the FFB info to your wheel or something like that. Why is it not done by default I have no idea. Just like the AI FCY issue, someone found a fix for it that S397 can do to all users. Steam it usefull for quick patches...
thanks for the reply,ive just noticed this in my controller json "Device Name 1":"FANATEC ClubSport Pedals V3=#0eb7183b", "Device Name 2":"Thrustmaster T300RS Racing Wheel=#044fb66e", "Device Name 3":"", "Device Name 4":"", "Device Name 5":"", "Device Name 6":"", "Device Name 7":"", "Device Name 8":"" should i have my wheel as device 1
I dont know there is one line in the player.json to set if the AI should follow the SC or the car ahead under FCY, looks like the bug happens if it's set to follow the SC and that seem to be the default
I think there is nothing to change, because I think this is linked to the USB device detection order (same as in the Control Panel for Game devices) If you change this order, you will desynchronise the the axis affectation already set in game, not sure this work because it's linked to hardware detection order.
It shouldn't matter. Input 1 for me is my T300, while Input 2 is my 360 Controller and 3 is my Thrustmaster joystick. Need to work out a way of using the 360 controller as a clutch, really...