Can no longer enter DCS FC3 planes

[Aethyrion]

Since the last DCS update (Steam version) I can no longer fly FC3 planes like F15C and Su-27. The module appears to be active/valid on the DCS home page (1.5.2 version is displayed). Steam shows that I own the DLC. But when I launch a mission, the map is displayed instead of the cockpit. I can view other planes with F2, but can't jump in player plane (F1 or RAlt+J) which doesn't seem to be present in the battlefield anyway.

 

I have already tried to force activate FC3 module (fc3_protect.exe) without success. Planes from other DLCs are still working.

 

Can anyone help me ?

Edited January 23, 2016 by Aethyrion

[Aethyrion]

Tried uninstalling FC3 module then installing it back. Still not working.

[Aethyrion]

Found some lines like this one in the logs :

ERROR DCS: Invalid Unit Module: "F-15C"

 

Nobody can help me ?

[winchesterdelta1]

I seriously don't know how to help here.. Maybe uninstall DCS. Delete the DCS profiles and such and re-install from STEAM. Or maybe go for the Non Stream version.

[DarkFire]

Yep, sounds like it's time for a full DCS re-installation. From the invalid module error message the problem is likely either to be a windows registry corruption or some sort of module unlocking issue.

[Aethyrion]

Still not working after a full reinstall. How to "delete the DCS profiles" ?

 

Thanks for helping me.

[winchesterdelta1]

Go to C:\Users\username\Saved Games

 

Copy that DCS folder in there and save it somewhere save and delete it. Or simply rename it. to DCS backup or something.

[Aethyrion]

Tried it, still not working, but thanks.

 

I have opened a ticket and someone from ED support is trying to help me, maybe he'll find a solution.

[Rio.id]

Hello, I have the same problem. It only happened with Flaming Cliffs 3 related aircraft. I also owned A-10C, and the module works just fine.

 

I've tried everything from reinstalling DCS, removing registry and saved games folder, re-activate the FC3 module, but nothing seem to fix this issue. I've also open a ticket, but without any solution yet. How's your ticket goes? Did they give you a fix yet?

 

Thanks

[Aethyrion]

Hi, I'm been help by an helpful support guy but issue not fixed so far.

 

What I have tried since my last post :

- replaced Flaming Cliffs\bin with "working" files,

- deactivated FC in admin mode (fc3_protect.exe), launched the game as admin, prompted to activate FC back again.

 

Curiously in the same mission, I can enter other aircrafts (such as A-10C for example) but when I try to enter an F-15C (R-Alt + J) the plane behaviour is altered for a fraction of second (as if I'd managed to take control of if) but it quickly returns back to its previous course.

 

My guess is that there is a bug with the last Steam version. Maybe the game is now looking for modules named after aircraft rather than module named "Flaming Cliff" ? It would be interesting to hear if other users are still able to use FC3 planes with Steam version.

[BIGNEWY]

which anti virus are you using?

[Aethyrion]

Windows Defender only (since updating to Windows 10).

[Rio.id]

Found a solution, just download DCS from the official site, then login and use the key obtained in Steam. Everything works well now. I think the problem lies in Steam version of FC3.

[Aethyrion]

FC3 planes are still not playable in the Steam version nearly one year later... Is this bug planned to be fixed someday ?

[BIGNEWY]

I wasn't even aware it is not working?

 

if you have the steam version please try them again and then add you logs here, I would be happy to take a look into it

[RabidSquirrel]

I have the same exact issue as well. Everyhting you have described is exactly my issue. The only difference is that I am not using any steam editions. I am going to do a clean install and see if that does it. Although, after hearing what Aethyrion has already tried, and with no result, I am worried I may run into the same problem!

[mytai01]

Sometimes a clean installation of Windows is the only way to go!

[BIGNEWY]

if we could see some logs we may find the reason