Capt_Hook Posted July 31, 2018 Posted July 31, 2018 (edited) I hate posting a thread on this, but I'd rather not go through the more intensive steps of an uninstall / reinstall if someone has a better answer. I've been playing IL2 just fine in VR (Samsung Odyssey) till the last update. Now the game crashes back to the launcher immediately after clicking 'play'. Windows even logs show an APPCRASH in IL2 with a fault code of c0000005. Steam VRserver log shows: "Delaying SteamVR Home launch because system.generated.il-2.exe ran for only 1.721211 seconds" Anyone seen this issue? I also can't say for sure if the IL2 update itself was the culprit, as I also updated Nvidia drivers at roughly the same time. Other VR apps work just fine, including DCS. Edited July 31, 2018 by NervousEnergy
JonRedcorn Posted July 31, 2018 Posted July 31, 2018 Haven't had any issues myself on my rift, was just playing last night. Run it through steamVR only myself. I'd do a clean install.
dburne Posted July 31, 2018 Posted July 31, 2018 (edited) Have you tried running the game by just launching the IL-2.exe rather than going through the launcher? That is how I always launch it, I only use the launcher to get updates when I know they are out. Granted it should not crash on you using the Launcher, but may be a workaround. Edited July 31, 2018 by dburne
Capt_Hook Posted August 1, 2018 Author Posted August 1, 2018 Thanks for the tips... going straight for the il-2 executable didn't fix it, but clearing the update cache directories and forcing a re-download of the last update did fix it. Odd, but... it worked.
JonRedcorn Posted August 1, 2018 Posted August 1, 2018 16 hours ago, NervousEnergy said: Thanks for the tips... going straight for the il-2 executable didn't fix it, but clearing the update cache directories and forcing a re-download of the last update did fix it. Odd, but... it worked. Glad you got it working, I also had some weird shit just go on, I had all my Il2 website stuff but none of my steam bought stuff in game and it was asking me to log in, I deleted the startup.cfg and it fixed it. If you ever have future problems try deleting that startup.cfg file. Bugs out sometimes.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now