Jump to content

Cutterone

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Cutterone

  1. 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.
  2. Oaky great!!! Yes, I use Openbeta standalone not through steam.
  3. 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?
  4. 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.
  5. 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
  6. 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
  7. 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?
  8. 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.
  9. 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.
×
×
  • Create New...