Valkween

I'm not a game developer expert by any means but i've seen many big game dev compaines handle stable and beta branches in a better way so here are my thoughts: As you said, OB should be used for testing new features. The problem is that they also use it for pushing the bug fixes that stable has so then you have to wait a long time for ED to push the big patch that contains a clusterf*** of things: FIXES/NEW FEATURES/UNRESOLVED NEW BUGS etc. Doing that will never result in stable being stable. To prevent this i think they should test the fixes internally and push it both ways, stable and beta. Then, in beta, they should submit a bunch of new features and stop there (not bring new ones) until they fix all the bugs that the current ones brought and then push them on to stable. Hope this idea helps.

Same issue, at a random point it starts queuing commands until i press the comm menu. :(

Nice! NineLine said an hour ago on the Steam community hub that there was a delay on the update because of some issues. Seems to be resolved now.

Hi backspace. Where did you get this information? Because unless there has been a problem with the update, i usually get it a few hours later than the standalone version, doesn't matter the day.

I don't think that's the problem since i'm currently am (and always been) on openbeta branch and recieved the proper updates just like the standalone. Don't know if you play DCS on Steam but if you right click the game on your library and go to properties→beta you can change the branch you want to be in.

Hi, i'm wondering if the steam version is going to get today's update in a few hours or so, i saw people asking this on ED Facebook and Steam community hub but no answers. I thought that maybe there was a delay because of some binding bugs reported on the forum but there was no official statement about the case. I was personally looking forward to play with my group tonight but we are split in two diff versions of the game.

Yes i was refering to the F10 map heading. Thanks all for the responces! I'll try that later when i'm back home. EDIT: That was it! Appreciate for the help.

I noticed that the heading showing on the hud is not accurate (8° off). I always align INS before taking off. Is this a bug or am i missing something?

Woops, my bad. Fixed.

Track file uploaded. comm_menu_bug.trk

As the title says, when going to the editor and putting and F18C starting mid air makes the comms menu unusable. This problem can be reproduce with any instant mission that starts mid air. EDIT: This also happens after taking off. Tried validating files just in case but nothing... I'm using the steam version. My specs OS Name Microsoft Windows 10 Pro Version 10.0.17134 Build 17134 Processor Intel® Core i7-4790K GPU NVIDIA GeForce GTX 980 VR OCULUS RIFT CV1 Logs: https://pastebin.com/j0qGR0sE