I've been battling Crash to Desktop (CTD) for quite some time now. I think I've nailed down when the crashes happen, just not what is causing it. Sys specs CPU I5 10400 GPU 3060 12GB 16GB ram 2TB SSD with ~30% free space, Running both in VR on an Oculus Rift S, using open composite/steam VR and Oculus VR Also happens when running just monitor. What's happening: The crashes always happen when I leave the menu in a session to drive. When there is a little stutter as the car does the bounce as it (I'm guessing) enters into interact with the track . It is always this transition from menu to driving when the game crashes to desktop. I have >100 bugsplat reports, and dozens of submitted reports. Anyone else having this issue? I've done reinstalls, refreshes, all the soft side fixes to no avail... I am going to try to see if this fix listed in another thread helps: Final tidbit, I did slightly overclock my CPU and it seems to be a little more stable but I still crash out randomly. Edit:** I should add that I have run memtests and have 100% pass of all tests, including RAM tests
Crash is happening at low level in directinput according to the few crash reports I found against your email address. In those specific instances there's nothing obviously daft happening on our side that I can see in the dump like passing in empty/unchecked values etc. I see you had other posts in relation to ffb issues recently too. Given both together I would suggest dropping the custom FFB for some testing if you issues there persist and doing an forced update or reinstall of your controller drivers/software. Not sure what controller hardware you have, perhaps notable recently is some reports on the forum that autoupdate is broken for TM software so if you have a TM wheel you'll need to manually sort that. If you could also please add your key hardware specs including controllers and output devices to your signature it is helpful for us not just when providing direct support but when trying to spot patterns in reported issues.
Hey Dave, thanks for looking into this for me. I'm running with a Simagic Alpha Mini with the penultimate software release (the newest drop has some reported bugs) Pedals and shifter are both G27, both routed with Leo Bodnar cables. As for the FFB issues, it was only when the FFB forced the wheel to full lock I'd get the drop in wheel weight. However since reinstalling that seems cured. I will add my sys specs to my signature.
@Dave Stephenson : I just reinstalled, wiped all FFB info, and loaded up a grid of BMW 2002s at Spielberg short. First grid start was dicey, had a lot of judder and random geometry for approx .5s (this is fairly common for VR). After restarting to see if I have finally caught this, it crashed. If you can see my latest crash log, there may be something there.
I'd suggest if it's directinput related that you remove your input devices and test. This may make controlling the vehicles more difficult but you'll find the culprit when you connect them one at a time and test. At which point it's likely to be drivers for one of them or a hardware issue (with your input devices)
@Michael3 @Dave Stephenson I should forward this in saying that I did plug all of my USBs back into ports they previously did not occupy (possible USB Cache issue?) So I have completed the following Troubleshooting: I deleted the AMS2 Documents folder and unplugged all my inputs. My test for each round consisted of 10 resets of a full grid at Spielberg in the Porsche Cup Cars. A pass would be all 10 resets of the race went fine: Test 1: No inputs - Pass Test 2: Wheel Only - Pass Test 3: Wheel and Pedals - Pass Test 4: Wheel Pedals and Shifter - Pass Test 5: Wheel Pedals and Shifter in VR - Pass Test 6: Wheel Pedals Shifter in VR with Custom FFB - Failed on 3rd restart. Test 7: Removed Custom FFB (running Default +) - Pass I am running @Danielkart 's FFB files. I am not sure if there is something in there that could be leading to my issues, but I am going to try a few other FFB files to see if more than one FFB in Custom will cause me crashes.
I just tried an online lobby with the final test setup. I crashed while in the menu trying to change a button map, then soon after crashed after leaving the menu to drive again... This is an incredibly frustrating issue to sleuth.
if you've an external SSD I would advise to put a fresh install on it, boot it up, download AMS 2 on it. Drivers, etc. then see if you can race just fine.
I started looking @ Simhub's troubleshooting for crashes and plugging the wheelbase into a surge protector is on the list of things. I have just run my test with Custom FFB and in VR. Pass.. I am really blown away at something so obscure causing this. I assume it is a clock delay or something caused by a slight dip in power supplied to the wheelbase. It has to be the weirdest issue I've come across in nearly 2 decades of simracing.
Some users of DD wheels have found weird compatibility issues with their motherboard USB controllers and have had to get a separate USB Pcie card. This link gives some summary info, but unfortunately the pcars forum it links to is no longer around. SOLVED - rF2 CTD using Simagic Alpha DD wheelbase
