codeslayer

I think I figured this out. I have an X56 stick and throttle and the Buddy Fox A10-C control box attached to my system. It seems the default mapping for the throttle is conflicting with the control settings and causes one engine to shut down (although power settings are at idle). I first unplugged everything and it worked fine, unplugged just the throttle and the control box, worked fine. Cleared all the throttle settings (with throttle plugged in) and it worked fine, remapped the settings and it worked fine. The control box didn't appear to interfere at all. This is all with no programming of the stick or throttle through the X56 control panel. So it seems the mapping that ships with the module is the culprit.

Going through the full engine startup, either from cold start or during the startup training, when I'm starting the 2nd engine, it hits about ng 50% the starter turns off and the engine dies. I've tried this about 8 times, restarting the scenario or the entire simulation and it never gets both engines fully started. I've gone through the procedure exactly as documented or shown in the training. Doesn't matter which engine I start first, the other always fails at the same point. Am I doing something wrong?

I use McAfee and it deleted DCS.EXE as a virus, and my backup/protection software Acronis indicated it as ransomware.

I found this is a problem with my anti-virus (McAfee) and my backup/protection software (Acrons), both see DCS.EXE as a potential virus/threat. McAfee deletes it on start, Acronis warns that it's a ransomware threat. I stopped this problem by marking the exe in both apps as trusted. This needs to be looked into.