Jump to content

Recommended Posts

Posted
Getting Auth failure on

F/A-18C

Georgian War campaign

SU-33 from flaming cliffs.
Logs, screenshots, Steam or Standalone?
Confirm the time on your computer is correct.
If you have some licenses on Steam, but have the Standalone version installed, "update" the Steam "link" on your Eagle Dynamics account.

Cheers!


Sent from my MAR-LX1A using Tapatalk

Posted

I, am getting the same thing but with f16, syria, sinai, apache.

 

 

 

 

 

 

authorization failed.jpg

dcs.log

  • Like 1

Intel Ultra 265K 5.5GHZ   /  Gigabyte Z890 Aorus Elite  /  MSI 4070Ti Ventus 12GB   /  SoundBlaster Z SoundCard  /  Corsair Vengance 64GB Ram  /  HP Reverb G2  /  Samsung 980 Pro 2TB Games   /  Crucial 512GB M.2 Win 11 Pro 21H2 /  ButtKicker Gamer  /  CoolerMaster TD500 Mesh V2 PC Case

Posted (edited)
9 hours ago, Flappie said:

 

yes my time is synced with the server and my time zone is correct..PC is updated to the latest, I just double checked and I still get that error..

Edited by The_Nephilim

Intel Ultra 265K 5.5GHZ   /  Gigabyte Z890 Aorus Elite  /  MSI 4070Ti Ventus 12GB   /  SoundBlaster Z SoundCard  /  Corsair Vengance 64GB Ram  /  HP Reverb G2  /  Samsung 980 Pro 2TB Games   /  Crucial 512GB M.2 Win 11 Pro 21H2 /  ButtKicker Gamer  /  CoolerMaster TD500 Mesh V2 PC Case

Posted

I ran into the same problem earlier this week. In my case it was the F-14, the F-15C (not FC3, the "standalone"), Nevada and Persian Gulf. 

Turned out these are modules that I had bought via Steam and "transferred" over to DCS standalone. Presumably, the Steam server must have had a hiccup. I fixed the issue by reimporting the serial numbers via my profile on the DCS website.

Hope that helps.

  • Like 2
  • Thanks 1
Posted

OK will check that info out thnx..

Intel Ultra 265K 5.5GHZ   /  Gigabyte Z890 Aorus Elite  /  MSI 4070Ti Ventus 12GB   /  SoundBlaster Z SoundCard  /  Corsair Vengance 64GB Ram  /  HP Reverb G2  /  Samsung 980 Pro 2TB Games   /  Crucial 512GB M.2 Win 11 Pro 21H2 /  ButtKicker Gamer  /  CoolerMaster TD500 Mesh V2 PC Case

Posted

The exact situation for me.  Rebinding the Licences from my Steam Account to DCS fixes everything in 1 minute. 

  • Like 1
  • Do not own:  | F-15E | JF-17 | Fw 190 A-8 | Bf 109 |
  • Hardware:  [ - Ryzen7-5800X - 64GB - RX 6800 - X56 HOTAS Throttle -  WINWING Orion 2 F16EX Grip - TrackIR 5 - Tobii 5C - JetPad FSE - ]
Posted
4 hours ago, Jayhawk1971 said:

I ran into the same problem earlier this week. In my case it was the F-14, the F-15C (not FC3, the "standalone"), Nevada and Persian Gulf. 

Turned out these are modules that I had bought via Steam and "transferred" over to DCS standalone. Presumably, the Steam server must have had a hiccup. I fixed the issue by reimporting the serial numbers via my profile on the DCS website.

Hope that helps.

Yep, this fixed it ..

  • Like 3

Intel Ultra 265K 5.5GHZ   /  Gigabyte Z890 Aorus Elite  /  MSI 4070Ti Ventus 12GB   /  SoundBlaster Z SoundCard  /  Corsair Vengance 64GB Ram  /  HP Reverb G2  /  Samsung 980 Pro 2TB Games   /  Crucial 512GB M.2 Win 11 Pro 21H2 /  ButtKicker Gamer  /  CoolerMaster TD500 Mesh V2 PC Case

Posted

@Orwell Can you give it a go? 👇

18 hours ago, Jayhawk1971 said:

I ran into the same problem earlier this week. In my case it was the F-14, the F-15C (not FC3, the "standalone"), Nevada and Persian Gulf. 

Turned out these are modules that I had bought via Steam and "transferred" over to DCS standalone. Presumably, the Steam server must have had a hiccup. I fixed the issue by reimporting the serial numbers via my profile on the DCS website.

Hope that helps.

 

---

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...