Bernd, I tried twice with Corvette c6 GT2 at Silverstone GT and BMW M6 GT3 at Nürburgring Sprint. Removed fanaled plugin before as suggested but crashed again.
These trace files again end at different points. In your opening post, you did say that you have reinstalled it, so i guess that it worked before. What was the last build version that worked for you? And can you post your hardware configuration?
Holy moly, I switched back to new UI, which was the last working built and I could drive at least a lap. But I had to quit, 'cause lady want's to go out. Will try later. Thanks for your help.
It seems, I was happy to soon. Within two (lol) laps with Spark F1 on Nürburgring Sprint crash appeared. Eventmanager showed this - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-07-18T20:53:37.2311236Z" /> <EventRecordID>959</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-23U6K6P</Computer> <Security /> </System> - <EventData> <Data>rFactor2.exe</Data> <Data>1.1.2.0</Data> <Data>5ee239ee</Data> <Data>rFactor2.exe</Data> <Data>1.1.2.0</Data> <Data>5ee239ee</Data> <Data>c0000409</Data> <Data>00000000003aade0</Data> <Data>3998</Data> <Data>01d65d44ae57c5a8</Data> <Data>E:\Program Files (x86)\Steam\steamapps\common\rFactor 2\Bin64\rFactor2.exe</Data> <Data>E:\Program Files (x86)\Steam\steamapps\common\rFactor 2\Bin64\rFactor2.exe</Data> <Data>9b507d68-2d7f-4b3c-9405-ee8ea396fc14</Data> <Data /> <Data /> </EventData> </Event> hardware config: Core i7-4790 K @ 4000 MHz RAM: 16 GB DDR3 @1600 MHz Mainboard: MSI CSM- H87M-G43 (MF-7823) NVIDIA GeForce GTX 1070 MSI Armor, driver 451.67 Soundblaster Audigy FX triple setup 5760 x 1080 Acer z271 SSD Crucial MX 500 1TB Fanatec Wheelbase CSW v2, drive 328, firmware 627 Fanatec Porsche 918 RSR Fanatec F1 Carbon Fanatec CSP v3 Fanatec CSP Shifter v1.5
Last attempt for today with built v 1118, 5 m before start/finish-line (almost a lap) Edit: I checked my system with sfc and dism, no problems were found.
Again different last lines in the trace files. My last suggestion is to run rfactor 2 as an administrator, to see if that changes something. Start steam only. Then navigate to the folder ..\Steam\steamapps\common\rFactor 2\Launcher, rightclick on the "Launch rFactor.exe" and select "run as administrator". BTW If you switch the build, i would recommend to rename the Userdata Folderm each Time you do that. That did solve problems for some users.
Difference was, it just freezed but didn't ctd with new userdata folder and ran as admin, but no trace file was created. Btw, is there a possibility to create a trace file with new ui?
I don't know a possibility to force the game to create a single player trace file with the new UI, because i don't use it. BTW could you try this: Opt out of the beta and start the devmode then (the button under the single helmet). Does that crash too? Hint: the devmode creates a trace file by default and has an own separate userdata folder.
No, it didn't crash within the time it normally does. Created a trace file with 17 mb, so I couldnt upload. The first line had been repeated over and over. The wheel was not asigned at all. 375.95s hwinput.cpp 1868: GetDeviceState() returned error 0x8007000c, we will occasionally attempt to reacquire it ... 375.95s plrfile.cpp 2068: Retcode: 0 for renaming to E:\Program Files (x86)\Steam\steamapps\common\rFactor 2\ModDev\UserData\player\player.JSON 375.95s game.cpp 2828: Entered Game::Exit() 375.96s JVM.cpp 193: Invoking stop call 375.96s JNILog.cpp 33: Stopping framework 375.96s JNILog.cpp 33: Thread interrupted 375.96s JNILog.cpp 33: Joining 376.54s JNILog.cpp 33: Joined 376.54s JNILog.cpp 33: Stopped framework 376.54s JNILog.cpp 33: [Bootstrap] Framework stopping bundles 376.54s JNILog.cpp 33: [Bootstrap] Framework unregistering native services (including this logging facility) 376.54s JVM.cpp 198: Destroying JVM 378.51s JVM.cpp 200: Destroyed JVM 378.51s sound.cpp 1642: Entered Sound::Exit() 378.53s specialfx.cp 4373: Entered SpecialFX::Exit() 378.54s hwinput.cpp 8549: Entered HWInput::Exit() 378.54s hwinput.cpp 8572: LOGISDK Initialized in HWInput::Exit() 378.54s hwinput.cpp 8584: LOGISDK Exit() - Shutdown 378.54s hwinput.cpp 1786: Unacquiring device "FANATEC ClubSport Wheel Base V2" (if this is the last line in your trace.txt, your controller driver is probably buggy) 378.54s hwinput.cpp 1794: Now releasing same device (if this is the last line in your trace.txt, your controller driver is probably buggy) 378.54s hwinput.cpp 1796: Device successfully uninitialized 378.54s dynman.cpp 2994: Entered DynMan::Exit() 378.54s render.cpp 3386: Entered Render::Exit() 378.54s onscreen.cpp 4371: Entered OnScreen::Exit() 378.54s vidman.cpp 2938: Entered VidMan::Exit() 378.71s osman.cpp 1037: Entered OSMan::Exit()
I can keep you busy with more tests. It really seems to be a controler issue. Again rename the userdata folder. Start the single player and don't change anything with graphics or controller or other settings. Only select 1 opponent and click race. Don't load any setup or something and click race again, to enter the track. Don't do anything, only hit the key i on the keyboard to let the AI drive the car. What happens?
Well, running the car by ai as you suggested didn't crash. @Bernd, I appreciate your efforts to help me and thousand thanks for this , but for this weekend I surrender.More than enough of trial and error for now. There are other things to do. Maybe I'll give it another try next weekend.
It's a good idea to pause. What i would do as next step, is to unplug all USB hardware, except of the mouse and keyboard and uninstall (rightclick on the entry ->uninstall) all USB entries in the windows device manager. Some can not be uninstalled, but that is ok. And if you uninstall the entries that the mouse and keyboard use and they don't work anymore then, just unplug and plug them again. After that is done, restart the computer. Then plug only 1 device and test if rfactor 2 still crashes. If not, plug the next one, test again and so on. Start with the fanatec wheel. Maybe that helps to solve the problem or at least to identify the device that is causing it.
I couldn't even start a session now, so I deleted rf2 for now. Maybe another attempt in the future with a new built. Thanks for your support.
Well, after 5 months I gave it another try. All drivers updated (latest nvidia, Fanatec 373). After first start I cleared shaders and cbash trace file says 536.90s setup.cpp 3268: Could not find NURBURGRING_24H.ini . .. 538.03s GraphicsShad 2076: Error opening shaders MAS file layoutnordschleife.mas Could someone please have a look? Thanks and best wishes for a merry xmas
When exactly did it crash (at which stage of the loading process)? The trace has a logitech related entry as the last line, so i suppose that the before reported problem still exists. What happens, when you, before you start the game, rename the folder ..\rFactor 2\UserData , to let the game create a new one and start the game then? BTW the entry ...Could not find NURBURGRING_24H.ini is no problem.
Hi Bernd, very nice of you to help me again. The game crashed, when I drove out of the box, just input of wheel and pedal. I'm a little astonished. Where did this logitech related message come form. In the former trace file there was no logitech mentioned at all. The next attempt ran flawlessly, though there is logitech mentioned. The Logitech mouse has been replaced by a Razer. ok, good to know To come back to your post #33 Did you think of this?
Hello fischhaltefolie. (i only know Frischhaltefolie ) Do i understand you right, sometimes it works and sometimes it doesn't work? If yes, to do what i had written in my post #33 would not help much, i guess. The reasons for random crashes are hard to identify. Can you always progress until the track was loaded completely and you can see your car in the garage? If yes, does it always crash when you leave the garage or can you drive some laps sometimes? BTW also the trace entries "Error opening shaders MAS file ....." can be ignored too as it seems, because they also appear when everything works properly.
Of all a bit. Sometimes I have a ctd when loading the track, sometimes, when I had left the box driving in the pitlane, sometimes when I return to main menue after a session, sometimes not at all.
I was able to drive some Laps at Sebring with the new Cadi, went to main menu, started to load leMans 2020 with C8.R and loading was interrupted with a ctd.
