Hollister56

The User Manual can be found here: Program Files\Eagle Dynamics\DCS World\Mods\Aircraft\F4U-1D\Doc Send it to your Desktop for easy access. Ed

Yes you need the moose script for it to work. At least I think you do? I installed it and it works great.

Check this out.

Thank you for this very well done tutorial on setting up a helo to follow the Task Force. It worked great!

To further enhance the DCS community the TDK should be open source. IMHO

This is an old thread and I am surprised it hasn't been fixed yet. Who knows, maybe ED isn't aware of the issue?

It appears to happen after shutdown and then restarting, easy to reproduce and for me it happens every time. It's anyone's guess to why this is happening? The first cold start the FCS BITE test works as it should, after shutting down and attempting a second cold start it happens.

Okay thanks. I like to land on the carrier, shutdown and then re-start and go for another launch, but for now I will just re-spawn until it is fixed.

I've been having this same issue, land on the SC, taxi to parking, do a complete shutdown. Start back up, preflight checks, and do the FCS check and I get the same indications as the OP. Happens every time. Is there a reason for this or a solution? I sure would like to know what the problem is or if I'm doing something wrong? Anyone else had/have this issue?

Gross weight is pretty low, DLC is required for ACLS approach, the switch is set to off and the other switches are in ACL. It's pretty odd behavior for sure............and it doesn't do it in every mission, which is even stranger.

It appears that if you let the F14 autoland the lights go out at touchdown. If you take over, disconnect the autoland and hand fly it to landing, the lights stay illuminated and will not go out. Even after shutting down the jet and then starting from a cold and dark restart, not exiting the mission. Maybe some one else can try this and see what happens are report back. The VEL/PCD didn't work. No cockpit mods..........

Rustbelt, Are you from Steel Country? Anyway, the solution was to move the autopilot ACL switch to VEL/PCD then to OFF. Just moving the ACL switch to OFF didn't extinguish the amber caution lights. The Fire lights came on when shutting down the engines, and doing a Fire Test put out those lights. I will fly a few more flights to verify. BTW, I did a complete shutdown to a cold dark airplane. Then requested external power, which the ground crew won't connect unless the canopy is open, took me a while to figure that one out. After power up the lights were still on, Engine Fire and VDI Caution lights. So, then I tried the above and it worked, no lights.

I'm referring to the amber caution lights after a ALCS approach, and shutting down the jet with only external power connected. Everything is off, all switches you mentioned. I said AMBER not Red lights, but I did confuse Amber caution lights with Red warning lights in my original post. That's actually pretty funny, but also be less on fire.........

Does anyone know how to reset the VDI amber warning lights after landing? Thanks

Heatblur Team and F-14 forum members, When I build a ACLS mission for the F-14B and have everything setup correctly, when I engage the autopilot in ACL all the spoilers extend and DLC goes to maximum extension, airspeed increases to approximately 150kts, much higher than the normal Vref speed. Also note the Localizer needle is off to the right, it was centered when I engaged the autopilot. When you breakout the airplane is aligned with the deck, but the needle is off to the right. I am not sure why this is happening, just wondering if anyone else has seen this problem and if there is a solution? Thanks in advance.