Cutterone

I'm having the EXACT same issue as SizzlepopBACON in regards to the "new" error message when loading .trk files. Any word @BIGNEWY from the team regarding what may be causeing this and/or a fix?

Simple question: ED, will you be offering refunds for those of us who paid for the "previous version" of the Sinai map which now no longer exists? For Ugra/ORT and all the other 3rd party devs. If you really want to kill a product (DCS) and a community, THIS IS HOW YOU DO IT! I for one, and I suspect I'm probably not alone, will be VERY hesitant to purchase ANY future maps/modules from ED, Ugra, ORT, or any other dev. knowing that products WE (the customers) have paid for can, without even the common courtesy of a notification, be taken away from us and/or altered AFTER we've paid for them. And before anyone says it, this isn't the same as an "Early Access" or "Future Updates" issue. Those imply that the product will be expanded upon and improved in the future, and you are made aware PRIOR to purchase, this product had stuff removed and was diminished with no notification. So, unless it's resolved quickly with the CUSTOMERS in mind, yes ED you will pay the price for this (even though it's 3rd. party vendors) in that it WILL affect future sales (Business 101). Carry on!

Just wanted to confirm that the fix for former Steam users who transferred to Standalone works. I started DCS this morning, issue was there (all FC3 and FC3 planes greyed out and inaccessible), shut down DCS, went to ED site, when to my profile and hit get licenses, transferred licenses, opened up DCS and no authorization message, and all the FC3 planes show up individually and I took out the Mig-29S in an instant action free flight just to confirm. Seems to be working now, although the module manager still shows FC3 as being available for DL. Also note* other modules transferred from steam years ago when I switched over were not affected, only FC3 (I had the UH-1H, Gazelle, Mi-8, Caucasus, and some others that were not affected by the issue, only FC3

nullJust adding my name to the list of folks affected by this. Yes, I purchased FC3 a while back and am having the same issue as everyone else.

Having the exact same issue. Transferred from Steam to Standalone over a year ago. Tonight all my transferred modules are giving the same message as the OP. For me this means PG, Nevada, FC3, CA, Gazelle, Mi-8Hip, and Huey, are not working.

Oaky great!!! Yes, I use Openbeta standalone not through steam.

Great!!! Thanks guys. Should I move my saved games folder over to the M.2 drive before the switch as well? Then move it back to C:\Users\my name after I install it in the new PC?

Yes, my current PC uses an SSD for the OS, my new PC will be using an M.2 for the OS. My DCS is on a separate dedicated M.2 just for it.

Hello, I'll be getting a new PC soon. I currently use DCS openbeta 2.7 and have multiple modules and maps (Syria, Nevada, Persian Gulf). I have my DCS on a dedicated M.2 drive and would like to move the drive to my new PC when it arrives. I am wondering how I can do so without causing the modules and maps to become invalid. Any suggestions would be appreciated. Thank you

Here's a video I did for my unit last month. TAW NA 33rd. Btl. Hope you guys like it. https://www.youtube.com/watch?v=QN05qTAcjRs

I'm having the same issue with it not showing up in Module Manager even though I pre-purchased it days ago. Do we need to install the latest update first before downloading the terrain?

I fly the Ka-50 and my group does a lot of missions that start pre-dawn. I noticed this yesterday. Anti-Collision beacon no longer works, Navigation/position lights are so dim you can barely tell that they're on. And cockpit NVG lighting is now really dim as well.

All, sorry if this is in the wrong spot. I recently had an issue pop up where my mouse stops controlling the camera in External view when playing back a track. It works fine at the main screen, I click "Replay" and click on the track file from the folder, it loads normally. When the track file starts to playback, I can still see the mouse working normally when "in cockpit", but the minute I go to F2 for external camera the mouse does nothing. It will not control the camera at all. If I jump back into the cockpit I can see the cursor and use it normally, but hitting F2 for external camera and....no mouse control. I've checked my control setup and the mouse settings in the axis commands panel seem to be setup fine, I even reset them to default just to make sure, but...nothing. The problem is still there. Has anyone else experienced this? If so, is there someway to resolve it? Thanks.