SantasGolfClub

I work for a software company. We rate bugs in a specific order. No work around, and a major functional area being unusable. Affecting a percentage of users - is a P1 (Priority 1). We hotfix. Pull latest release branch. Fix bug and release the hot fix (current release + the fix) why can’t ED have done that? They say they have a fix. Patch it into the latest release.

So just to confirm, as my darn headset went to v63 (And there was a 'recommended update' for the Oculus app), so I'm broken as well - there's currently no work around, as the PTC is no longer a thing - v63 is official and forced? There's mention of running someone elses uploaded executable... but ... I'd rather not. So for now, we just need to wait? And .... MSFS2020 it is?

Ahhh crap! Same issue, and I JUST updated to 63 Oculus! :(

Thanks for that! Sounds like a very good plan. Do you do a restart from the 'Server Settings'? Or is it a Mission Editor / M.O.O.S.E scripting it of code that triggers the restart? Would be nice to popup a "Hey, the server is restarting in 10 minutes" type message.

Hi All, Hosting a little server, and if I restart it, people can and do join. But after an unknown period of time, between 15 minutes and an hour, no one can find the server on the server browser. I am able to connect directly with the IP, but it seems to not show on the server browser. If I go to my DCS profile, My Servers, I see the server listed as being alive for 9 days, or however long since I started it - but it won't appear in the server browser. If I click it in my profile, it shows as 'DCS Server' and never loads any details. It's as if the server is down. But I can connect via IP. So as I say, after re-start, it appears. So not a port issue that I can see. It seems maybe DCS somehow doesn't ping it to see if it's alive after that. I'm worried maybe my router is stopping 'pings' from DCS or something. null

It happens as soon as I click the aircraft icon in the toolbar. The box goes gray and the error is written. strangly - if I open an existing mission - it works. It’s only on a new mission. That’s baffling me.

I am unsure what has happened, but when I go into Mission Editor, Create new, and try to place an aircraft, I get a grey square where the aircraft details should show. All other things are fine. Ships, Helicopters. Just aircraft. I see an error appears in the dcs.log: Anyone know a fix for this?

I think I saw this reported. And can’t find it. But hoping there’s a fix. I used to launch DCS by putting on my Quest 2, going into airlink. And launching DCS from “Recently played”. But now when I do that - as soon as it loads into the hanger view - DCs shuts down instantly. And I’m sent back to the Oculus Home. launching from the desktop with the Oculus on - works. I hope the fix is no “well then, launch from desktop”. Has anyone seen this and know a fix?

And again after maybe 5 mins of play: I've set my page file to 32 Gig.

DCS just freezing, and then closing for me a lot on a new build Fresh install. Flying any aircraft. Nothing in the log, but Windows Even Log shows this. And then the next logged even is an Info: Tha DCS log has nothing too exciting. It seems DCS goes away before it has time to know it died. Any help with tracking this down would be great

I just did a full reinstall and things seem ok. I’m sure it worked first time last time though. So installing add on aircraft. Will check them.

Just renamed open beta folder to Old. Restarted. Folder got recreated/ Same issue. Just closes down instantly.

I've also edit the post with the full log.

Ok. I’ll try this. Just to be clear: this was a complete reinstall. Formatted SSD etc.

I had to rebuild my pc. I’ve reinstalled DCS and tested in the monitor. All good. But I am a VR chap. So loaded up on the Quest 2, the game loads but when it shows the hanger scene whereby it gets the menu - DCS just shuts down. Disappears. I checked the logs. No (significant) error when it dies. It just vanishes. Works fine in non-VR. (Log pasted below) Anyone seen this? RTX 3080. Ryzen 7 7700X. 32Gb 6200Mhz DDR5. Where can I even start debugging if there’s no error in the log file?