nbates66

If possible can you please find out the USB bus descriptions of these devices just for extra info? for example the device I had to disable was called "USB Input Device" but the description revealed it was related to the motherboard RGB controller:

Curious as to if that's also related to USB input devices I mentioned in the last post here: Does your issue also clear if you go through the USB input devices and disable them?

I've noticed this happen intermittently, I can get control back by alt+tabbing the game but if the bug occurs I won't be able to rename until I start a different event I believe.

Steam VR has two, one for all apps and then an override that works on a Per-app basis, I'm not sure it really matters however if you change both, as long as you pay attention to the final application resolution:

Figured I'd add this here, had a constant stuttering problem on new ASUS Strix motherboard based system, ended up clearing when the specific USB input device in this picture is disabled. My motherboard is an ASUS ROG Strix B-450-I but it's probably a safe bet that ASUS use the same AURA RGB controller on their ROG B350, X370 and X470 ITX boards, if you have a PC based on any of these boards see if disabling this device makes a difference, Entirely possible my system is just an edge case but anyone who finds that disabling a USB device clears the stutter please take note of the devices details here.

As one who struggled to get DR1 to run well in VR, I cannot agree with this assessment on DR2.0 VR, however I only own one headset to test with. Also shoutout to those who predicted that if VR got added there would be various peoples complaining their particular platform was less favoured than some other. Some lighting is sub-optimal on my Dell Visor as well but I thought it'd just be due to the quality of the displays, I gotta get my hands on one of those Samsung Odyssey's.

Can you elaborate on that? I would disagree...

Please don't get everyones hopes up, these are the workarounds, not fixes 🤣

They are actually.

The handbrake is analog, it doesn't appear to bind as an axis but it definitely behaves as one, I plugged in and tested with a Logitech Joystick to confirm this.

I don't find this to be baffling really, personally I think the combination of developing for PC as well as the consoles AND the console sub-variants is proving to be a difficult developer workload, considering the sorts of bugs that have been appearing. It must be considered that some rendering methods and pipelines do not gel well with techniques such as those relied on by the PS4 Pro. As for the list Mastoideu posted, it makes no mention of if any titles were checked for issues, only for if the Developer had done the checkbox. more random reference: https://wccftech.com/blow-checkerboard-rendering-ps4pro-isnt-completely-free-might-better-uses-power/ Means little, newer games can be more complex and the PS4 Pro's hardware often relies on additional tricks for 4K that other hardware doesn't.

I did a very brief lookup of information regarding the PS4 Pro's behavior and it appears that there are some cases where performance, or worse visual consistency in games has dropped when utilizing these upscaling techniques, considering that DR2.0 does have some performance consistency issues already it's possible they tried a few of PS4 Pro's bandaids and ran into issues, perhaps it requires specific optimization. for reference: https://www.eurogamer.net/articles/digitalfoundry-2016-why-are-some-ps4-pro-titles-running-slower-than-base-hardware

Don't know if it's been mentioned already, but I've had an instance where I had a set of things to repair after a stage at service area, selected to repair them, scrolled down to select the rest of the items but then found my earlier selections were reset upon scrolling up.

Those suffering this no grip bug and crashing on PC, have you had steam verify game files?

If you're going to do this sort of thing shouldn't you also be comparing stage section times between compounds to see if tyre heating is taken into account? Information in first two posts is kinda useless since there's no mention of what was driven, Day/night may need to be taken into account as well.