Jump to content

Authorization failed after latest patch


Go to solution Solved by RyanFlint,

Recommended Posts

Posted

I'm more shocked that, given the delays this patch had, something like this slipped through.

This is kind of ridiculous.

  • Like 7

Reformers hate him! This one weird trick found by a bush pilot will make gunfighter obsessed old farts angry at your multi-role carrier deck line up!

Posted
Just now, Slippa said:

Clocking in here as well. Three modules out with others grounded due to broken bindings.

How knackered was it before the delays?

Try to set english language.

Posted

Same issue here as well - legacy FC3, F5E and F86 owner and the FC3 aircraft (except the SU33 as I've got the Supercarrier) are no longer authorized. The F86 and F5E however are fine.

  • Like 1

Ryzen 5800X3D | 64GB DDR4 @ 3600MHz | Gigabyte X570-Aorus Ultra | Gigabyte GeForce 4090 | Samsung C34F791 | Varjo Aero | Windows 11 Pro x64 | Auzentech X-Fi Forte | too many flight controllers...

Posted

Same 1+

  • Like 1
 

Intel i9-13900K, @5.8GHz, Gigabyte Z690 Aorus Master, 32GB DDR5 6200 DomPlatinum, GIGABYTE GeForce RTX 4090 Gaming OC 24G, LG 48GQ900-B, 4x 2TB Crucial P5plus M2 SSD NVME, 1x 500GB WD SN850 SSD NVME ,Thermaltake ToughPower GF3 1650W ATX 3.0 , Windows 11 Pro, Corsair AiO H170i LCD RGB, TrackIR 5, Thrustmaster Warthog, VPC Mongoos T-50CM3 Base, Thrustmaster MFD Cougar, MFG CROSSWIND, Corsair K95 Platinum, Sennheiser G 600, Roccat Kone Mouse.

Posted
I'm more shocked that, given the delays this patch had, something like this slipped through.

This is kind of ridiculous.
Might be due to the fact the beta testers gets the modules for free? I don't know, while I do agree.

Sent from my SM-A536B using Tapatalk

Posted (edited)

Same issue here

Long time FC3 owner, authorization failed, attempted reinstall, loops the failed authorization message and FC3 greyed out in game.

F5E module is fine for me.

image.png

ask install Screenshot 2024-07-12 074548.png

fc3 grey Screenshot 2024-07-12 074524.png

Edited by BLUEmako
  • Like 2

DCS-modules-500x100.png

Ryzen 5 5600X, RTX 2070S, 32GB DDR4 RAM, Win 10 Pro

Warthog HOTAS, CH Pro Pedals, Track IR

Posted

Same here, I bought the F-15C separately before buying FC3 and I also got the SU-33 with the Super Carrier module, both are showing, the other 4 fail authentication.

"For many the glass is half empty whilst for others it is half full, but for some, the milk is sour." - Unknown French Philosopher

Posted
4小时前,MAXsenna说:

Might be due to the fact the beta testers gets the modules for free? I don't know, while I do agree. emoji2373.png

Sent from my SM-A536B using Tapatalk
 

I think so.

[sIGPIC][/sIGPIC]

Posted

I have the same issue too for my FC3 module of aircraft.

I get that authorization popup error and my FC3 aircraft are disabled in DCS.

I have tried doing a full repair, tried removing (deleting) then adding back again the removed modules in the modules section and nothing solves it.

 

I understand that ED is aware of the problem and hope they have a new fix for this soon since it's a paid for product and I refuse to buy it again as FC4!

 

Thanks!

  • Like 6
Posted
If beta testing isn't being done on end-user equivalent builds/rigs then their testing isn't exactly valid....
Of course not, while I've had that feeling for quite some time now regarding a lot of "mishaps" that obviously passes QA for some reason.

Sent from my SM-A536B using Tapatalk

Posted

Same issue as well.  Yet another terrible patch release from ED without sufficient QA.  These are not isolated issues, this is poor test planning and execution.

  • Like 2
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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