Can you try extracting the exe inside attached zip, to the steamapps/common/BeamNG.drive/Bin64 directory? Then run it directly (double click the new exe file), and send a crash report (not support report) when/if it crashes. As usual, put some keyword in the crash report description to help me locate it. Thanks!
Ah, please install these C++ Redistributables: https://www.microsoft.com/en-us/download/details.aspx?id=40784 ( vcredist_x64 )
I'm using Win 10 and when I try to run vcredist_arm.exe it says that this app cannot be run on my PC vcredist_x64 works fine
What the error says? Is your operating system 64-bit or 32-bit? If 64-bit, the x64 is the one you need. If 32-bit, the x86 is the one you need
I'm using 64bit. When I try running the Debug.exe from stenyak it says that MSVCR120D.dll is missing on my computer.
Ok, extract the attached zip into the same directory as the exe When launching the exe, you may see a window similar like this (in your language): That's because that's a debug .exe, so it's not signed. Press 'Show more info' and then press 'Run anyway'
Alright, the debug.exe is working now. Same problem: when I reset a vehicle the game crashes. But now I get the notification from Windows "BeamNG.drive has stopped working" and searches for a solution. I can only close the program through this notification. I'm not offered to send a crash report...
I went into C:\Users\drew\Documents\BeamNG.drive\settings\inputmaps\ then opened c262046d and changed the FFB from true to false at the end and this made the wheel stay rigid so it goes back to center and wasn't completely loose and the vehicles respawn fine, but it gives no force feedback over bumps and terrain or the engine or any of that, and this may be a temporary thing to make the game more playable for all who experience the problem until the guys hopefully find the problem and fix it
https://gyazo.com/ed98b9e600009028e0151cf899d2ec8d This is what I get, not every reset but pretty often.
Im going to ask something, please forgive me for my bad english: Since this started with 0.8, what changed related to the ffb system? Did the new drivetrain code modify ffb in some way?
The only direct changes that happened to FFB were reverted in those test files I posted earlier in this thread. As for indirect changes, one of them could be the timing of vehicle start/restart procedure. The timing is something that can change each time you modify any code (and we do change heaps upon heaps of code on each update, as the changelog for v0.8 shows, so all timings will change on each release, it's unavoidable). So it is possible that we have had this bug forever, but the planets aligned with previous timings, and the bug didn't trigger until now. But it could also be something else entirely. The fact that it happens only with this very specific steering wheel model (G920), and not with other wheels (neither logitechs nor other brands) could mean the bug is in logitech drivers, but that's jumping to conclusions too soon. I've contacted Logitech guys, hopefully together we can shed some light into what's really making their drivers crash. Unfortunately, due to holiday dates, a fix is not going to happen soon. Please disable FFB in BeamNG as a workaround. I know it's not a solution and you'll be left without FFB, but at least it should prevent most of the crashes, allowing you to play. And again, thanks everyone for helping by creating support reports, sending crash reports, and providing useful information in this thread