Shibiswag

That's not the issue as some need to actually help people with fixes or solutions rather than just complain about than try to get an admit to close it down because they're tired of looking at the confusion. If they have nothing good or positive to contribute to the conversation and are getting annoyed by everything being said than they shouldn't continue to even look at it much less contribute to it.

Maybe you should learn what "I think" means as it already implies that I may not be correct on my statement, therefor there's no confusion to be had. Also, it's not helpful, unless it's hurting your eyeballs, in which case stop reading this thread rather than telling an admin to close it because you're tired of seeing "confusion." Also, if you go back to page 16 someone has a temporary fix that works with oculus link as well as another work around through steamVR that also works. I guess you must have missed that, because rather than complaining to everyone, you should be directing people to that post so that it would actually get them up and running even if only temporarily until the patch is fixed. Instead of complaining about everyone and what they are saying, you would be more helpful in trying to help find a fix for people so they can keep playing. @BIGNEWY Can you please link a post to the temporary fix listed on page 16 by the user: sBinn64 for the oculus link fix.

hence why i said "I think..." at the end. Was just throwing a guess out there.

It means, they have a fix and are probably forwarding the fix to Meta to implement in a hotfix or update or whatever, so even if they patch it on this end it means that now we are waiting on meta to fix it on their end. I think...

ah okay, good to know. Confirmed this worked for me as well. My system: Oculus Pro Ryzen 9 5900X 7800XT 16GB 64GB 3200 DDR4

Anyone who used the steam workaround? What settings do you use. I can actually get into the game via oculus link into steamVR and launch it from there, from the guide that was posted. Getting horrible FPS though, talking like 5-10 with severe pausing and choppiness. So for someone using the work around, could you tell me your settings for both oculus, including the tray tool and the steam settings. Would be much appreciated. Thank you. What version of oculus are using? V62, 63, or 64? I can't seem to find anything on it either, though from various users, I have been told that ED has fixed it internally and are currently testing it to make sure it doesn't break anything esle. That the fix will come out in the next patch whenever that will be. Could be a day, a week, a month. No one knows.

Additional Info: This user below created a fix/workaround. Not guaranteed to work for everyone but worked for me using SteamVR TheIziWarrior - ED Forums (dcs.world)

Found another form that has a tempory work around/fix using SteamVR. Here is his User: TheIziWarrior - ED Forums (dcs.world) Not guarnteed to work for everyone but worked for me. My system: Ryzen 9 5900X @5GHZ all core. RX 7800 XT 64 GB DDR4 @ 3200MHZ

This user has a work around through SteamVR. Not guarnteed to work with everyone, but worked for me. Not as pretty but it's better than nothing until the fix is released. TheIziWarrior - ED Forums (dcs.world)

How do you do the work around using SteamVR? I have the same problem.

My concern was that if they could fix it, not that they wouldn't. This barley happened today, as I have not played in a good while, I had my oculus on with auto update and yes, maybe I should have done more research, however I was primally concerned that it was something on my system. File error, corrupted registry, etc... It wouldn't have crossed my mind that it was the actual VR software that was causing the problem, Had I not come on here. I might of went as far as to reformatting my entire system thinking something was severely wrong. So, after exhausting all my options, is when I came on here to start looking around for people who had similar issues. Also, no one is forcing you to respond, despite you trying to help people, if you keep seeing the same post so many times, then simply don't respond to them. Sometimes yes people overlook I myself included and I admit that it's not as if you are assuming that they are just ignoring it outright. Though again, I'm glad they are testing it, and that it will be released in the next patch and that it's "fixed" and they are making sure it doesn't break anything else. However, I will not go on any guarantees on anything until it's actually released and working. So, if everything is going okay with the fix than good. Hopefully they will release it soon and when I download it, I'll keep my fingers crossed it will work just fine. Until than I at least found a fix and posted it for people that want to at least play in 2D until then which I posted. Have a good day.

Update to my OP. It Turns out this crash is specifically to users who use Oculus for VR. I did some research and confirmed that both V63 and V64 even with PTC turned off from 64 and reverting to 63 it is the oculus that is causing the crash. I deleted the saved games folder, launched dcs_updater, signed in, game started fine. Deleted the MT shortcut and dragged a new one (Required, old short cut won't work), game started fine. I guess it's back to 2D until they fix it. I was made aware that ED is currently working on a fix for it and it's in testing which is some good news. For those of you who are still crashing upon launch and just want to play 2D here is a fix for that. Delete your openbeta folder in save games. Of course, back up your controller inputs. Delete the MT or ST (Both if you use both) shortcut off your desktop. Relaunch the game using the dcs_updater.exe Resign in, game should launch as normal. After game launch, create new shortcut for MT or ST or both on your desktop. Game will launch as normal.

No i did not, thank you for the info. However, you do not have to be rude and condescending when saying it. There is no need for that sir. Also, the "in testing" does not 100% guarantee that they will fix it. Though it's good they are working on it.

I did some research and confirmed that both V63 and V64 even with PTC turned off from 64 and reverting to 63 it is the oculus that is causing the crash. I deleted the saved games folder, launched dcs_updater, signed in, game started fine. Deleted the MT shortcut and dragged a new one (Required, old short cut won't work), game started fine. I guess it's back to 2D until they fix it, if they ever fix it. This will not work if you updated past V63 to V64 with PTC on or went from. So if you are on V63 and didn't update you can roll back but for those that updated to V64. DCS in VR with Oculus is now unplayable.

I never even had that checked, and I am getting the exact same problem with the exact same errors on the log. Is there a way to roll back the version?

Unable to load into the game at all. Tried repairing. renaming saved games folder, restarting game creating new saved games folder. Nothing works. Log file shows several errors and warnings. I see other people are experiencing the same issue, is there a fix for this or will we have to wait for the next update to actually play? dcs.log

I am having the exact same issue. Game gets to 15 years spash after nvidia logo than just crashes. Haven't changed anything and just started doing it. I tried the above mentioned by Rob10 and it didn't work. Here is the log file. Going through the log myself I did notice the following errors: 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R2}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L2}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R1}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L1}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R2_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L2_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R1_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-03-27 17:47:05.087 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L1_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" It shows in both the openbeta folders from my save game, the one i originally renamed to openbetaold and the new folder it created openbeta. dcs.log

Hoping someone can help me out with this, just bought the 47 and loving it. Only issue I am having is that for a cold start, on the ground and even after airborne the gyro sight on the gun will not move, it stays stationary in the middle. On hot start it moves around. I cannot find any switch in the cockpit, nor any control command to bind to a button to turn it on. If anyone knows the control bind description or knows how to fix it, would greatly appreciate it.

Yes I'm aware that DMS down turns it off, however this is not the case, i have no key presses bound to that. Only thing that's bound is on my stick, I thought maybe that was initially causing it, however I went onto a pve server and just flew around without touching anything and it still turned off and wouldn't turn back this included attempting DMS down as well as moving the knob back and forth. So I don't know what this issue is.

Yeah, i thought that might of been the case, but no, i joined server 4ya and just flew around away from the combat area it still does it just randomly without me pressing anything on my stick.

HMD for the Viper just randomly decides to turn off, this has only happened to me in multiplayer, single player works fine. happened 4/5 times. 3 times in Growling sidewinders server, a 4th time in a random guns only server, didn't happen the 5th time in the server the squadron I'm in plays on.

I'm having the same issue. Def a game breaking bug, I can't even fly it anymore it gets so annoying.

I have an issue as well, only happens in multiplayer, HMD just randomly turns off. played 5 games happened 4/5 games. Single player no issues.

Okay, thank you for the fix, though I still find it odd, that when I initially did it, I tried both, turning point and fly over. With each it still did the same thing, so maybe it was just bugged out on my end and your mission file was not affected it by it. Either way thank you very much.