PMDG DC-6 and FS-FlightControl

Discussion Hub Aircraft
1

This driven me crazy for a while, as I was not aware of this problem. Basically both are not compatible. In the case of DC-6 using FS-FlightControl produces that gauges and engine stress info in the tablet rapidly oscilate all the time and also a flickering low oil pressure annunciator that never turns off. This is specially critical if you have enabled the realism settings in the tablet as it leads to engine failures short after takeoff, making it impossible to fly the DC-6 with realism enabled.

If you face this problem while following the right procedures for this plane then FS-FlightControl is most likely the reason.

But I have found that the problem is reproduced only during aircraft initialization and engine start. Therefore you can still use both if you follow these steps:

  1. Quit FS-FlightControl before launching the flight from MSFS.
  2. Once in the cockpit perform the engine start procedure on the DC-6 without FS-FlightControl. Engine start can be done manually or using AFE if you prefer.
  3. Once you have your engines running and you are ready to taxi you can manually launch FS-FlightControl again.

You need to quit FS-FlightControl before every new flight with the DC-6 and repeat the steps above.

This has worked for me so far and yesterday I could complete a 2h flight with all realism settings enabled without any issues for the first time. In my case I just used AFE for the preflight checks and did all the rest manually.

If for some reason you see rapidly oscilating gauges, oscilating engine info on the tablet or flickering low oil pressure annunciator in the cab that´s FS-FlightControl again and this will lead to an engine failure, no matter what you do, so you will need to quit it again and continue flying normally. I just had problems during engine start so I never needed to quit it again afterwards.

Cheers

2

Did not know there is a problem with DC6 and FSUIPC. I flew around Africa the last days, having FSUIPC running with msfs start, because Luke Airtool requires it. But did not run in any trouble. I have realistic engine start, carb icing et al enabled, but engine damage disabled. Maybe that is why?

3

Yes, that´s it. Engine damage is what is affected by FSUIPC. If you enable it you will notice how the manifold gauges start to oscilate and you have a never ending low pressure annunciator light. Also the stress tab in the tablet has flickering status of warnings all the time.

Cheers

4

Another SW that creates problems with it is FS-FlightControl. You also need to run it after having started your engines. I presume this one generates problems because it has both failures and engine controls modules included.

Cheers

5

Ok, after further testing it´s FS-FlightControl and not FSUIPC what causes the engine failures. I thought it was FSUIPC but as I launched FS-FlightControl with it (using the FSUIPC autorun feature) I didn´t realize that the other SW was the problem. Just using FSUIPC alone does not produce any problems. The real problem is therefore FS-FlightControl application. For more info about this tool please refere here:

I have updated the first post in case this helps to other users and sent a report to the SW author.

Cheers

1 Like