BluePhantom

No, the problem is not that my comms don't work. This is not an 'easy communications' or correct frequency issue. The problem is that the Communications Menu does not appear in game at all Apologies, it is not due to the Horrido campaign. It is either an ED or Ugra problem. It happened again to me. Once it occurs (I have no idea what triggers it), the comms menu fails to work for ALL Allied Warbirds on the Normandy map. It appears Axis aircraft work okay. Other maps are okay. Lastly, when this happens, the communications menu works fine on the ground, but as soon as you go airborne -- nothing. Nada. Zilch. The never-ending saga of super-touchy, super-sensitive DCS. Sorry to have bothered you.

I have played Mission 2 twice now. Both times, I have comms capability on the ground, but once airborne . . . no more comms. Neither a key binding or the '\' key work. Press, press, press and nothing. This first time, this strangely leaked over to all of my Allied Warbirds. Took out all mods and same behavior. A computer restart seemed to erase that. Warbirds are good again, but same problem with Horrido. Probably another issue caused by the recent patch?

Agree 100%. ED continues to crowd out modders by locking everything down. The free modders are an invaluable asset to making this community vibrant and interesting. ED seems to have zero interest in working with the external community or of fostering them as a resource that can accomplish so much for ED.

This is what ED doesn't get: the modding community has been hundreds and hundreds of hours creating work to make DCS better -- in this case liveries for the F-5E. These all wiped out in one fell swoop. ED's attitude is "We have provided a template, no go out and spend hundreds more hours creating supplemental work (which of course we will wipe out in one fell swoop later again). No working with the community to create a sustainable, playable product. Just slight of hand marketing. The effort that went into this upgrade could have been so much better directed toward other aspects of game play. I am already sorry I purchased this update. That was my foolishness.

Thank you for your reply. Much as I surmised. Even though a winter environment is more relevant to Normandy than other maps, the developer has no intention of fulfilling this wish. I know it is a lot of work, but, really, enhancing the palace of Versailles . . . is that really more important?

I really look forward to the new DCS ATC and general communications upgrade when I reincarnate in the year 2348.

I am very surprised that there is absolutely no interest in a winter version of Normandy. How strange.

Thank you for taking the time to explain your viewpoint. While I understand and partially agree with your point, I don't think it quite addresses my unhappiness with the situation. 1) One example might be where a mod is old and no longer compatible with the newer DCS versions and the creator will not upgrade the mod to work with the newer version. If I can load the mission without that particular mod, I can replace it with something else and still use the mission. Or I can skip that mod. The point is that all of my hours put into creating the mission will not have been wasted. 2) A recent example was one of CurrentHill's mod's. He now packs all of his mods into one large country file, so you cannot easily go find the original single mod, download the latest version and install it to make the mission work. I did ensure I had the latest version of his pack. I could load a brand-new mission with the same module just fine, but DCS refused to see the module in my older mission and would load nothing. In this case, the mod is valid but DCS does not see it. BTW, this issue usually involves non-aircraft mods for me. I am not really talking about flyable aircraft. It might be something as simple as placing a mortar in the mission. So, is there a real security issue if DCS allows a mission to load without a "problem" mod? Can't they just say, "Hmm, this mod item is old or doesn't work, let me inform the user but strip it from the mission." Do they have to deny access to all elements of the mission?

Can someone please explain to me (1) why a remedy to this issue is so difficult and (2) why ED will neither acknowledge or address this issue? It is so depressing. (HC_Official: Thank you for the link. I am so tired of having to use hacks and workarounds for issues that ED should address. They will ensure that some missile has exactly the right thrust or speed and yet they rarely address core issues like this one.)

Thank you. The C++ repair fixed the problem. Don't know how it got corrupted. I even downloaded a fresh install of DCS last night. First attempt to open and received the same error. BTW, no log file with this issue. It evidently does not get far enough to even open a log file.

I also just started getting this error without any changes other than installing a few skins. Tried the OpenXR disabling: did not do a damn thing. Problem still there.

I have noticed this, too, and it is very disappointing. If you lack a necessary module, your mission is totally unusable. You cannot even load it to fix the missing module. Why have ED done this and why have they not responded?

Apologies if this has been covered - I have searched and scanned and found nothing: Since the 2.9 update all of the Currenthill Military Assets files cause a game CTD for me upon start up. What is the fix or cause? Is there a mod conflict? I have installed the files in the Saved Games directory.

Hmm, very strange. You are right. I am still running the Open Beta version. What seems to have happened is that the game now creates a "DCS" folder under Saved Games and uses it. My Saved Games folder has been "DCS.Openbeta" for years and was still like that after the last DCS update. Now, it uses only "DCS". The only change I can think of in the meantime was making the change in my anti-virus software. I moved all my Saved Games files from the DCS.Openbeta to DCS folder, and it now works normally. Thank you for you help.

I recently configured my anti-virus to allow DCS. In doing so, it seems to have switched me to the DCS stable version. I have been running the Open Beta for years. The game keeps creating a DCS folder under Saved Games and ignores the DCS.Openbeta folder. How do I get the game back to being in Open Beta mode?

Thanks for the suggestion. I will use this next time it happens. In the meantime, I made sure DCS was allowed in my anti-virus SW. It seemed to be missing. Perhaps that was it.

For the past year I have been experiencing an issue whereby something happens and I lose my saved login data for the DCS World game itself and for the ED home site (e.g., "user files", "change log"). Usually this is after Windows updates. The problem is not that something happens to the stored or cached login information, it is the fact that neither the game nor the ED home site offers any option to log in again. If I try to go to the User Files page, all that happens is the bloody tab just keeps turning for eternity. No error. No please entry your log in information. Nothing. In the case of the game, it loads up but logs in in standalone mode ("The web site is not available . . ."). Once in the game, I can logout but, again, but there is no option to provide login credentials log back in. It just kicks me out to the desktop. The only solution is for me to clear my browser history/cache and restart the computer. This is very annoying and time consuming, as I must log back into every other web site just because of DCS. To be clear, this is not a browser problem because it does NOT happen with any other program web site or game. ONLY DCS.

Okay, thank you. I'm having trouble to get it to do anything. At least I can rule this out as the cause.

Can anyone please confirm that this still works in 2.9?

Nope. Invite is invalid.

Mea culpa. I did have the flaps down, but not fully. Works beautifully now. Many thanks, gentlemen, for helping to get this wonderful bird in the air!

Of course. I tried it on several different carriers, too.

Has anyone been able to successfully take off from an aircraft carrier? The launch works perfectly fine. I am talking about getting enough momentum to keep the plane airborne after launch. No matter what I do, I crash into the ocean a few hundred meters after leaving the carrier.

It's working now. Your comment helped me troubleshoot. Not sure what happened, but I think some command or series of commands disabled the keypad. Weird. hanks for your help.

Does anyone know why the DSMS settings page will not allow me to set the LS time for lasing the GBU-12s? I am able to do it in a weapons practice mission I created, but in another mission created some time ago, I am unable to set any time for LS Time. The keyboard does not show any signs of registering inputs and when I push the button next to LS Time, nothing happens. It stays at zero. I made sure the DSMS MFD was SOI. Still same results.