Twin Otter Extended
Support for the Aerosoft Twin Otter Extended
945 topics in this forum
-
- 2 replies
- 782 views
-
- 8 replies
- 1472 views
-
- 4 replies
- 776 views
-
- 2 replies
- 751 views
-
- 3 replies
- 1105 views
-
- 6 replies
- 797 views
-
- 0 replies
- 545 views
-
- 18 replies
- 4148 views
-
- 2 replies
- 583 views
-
- 9 replies
- 1178 views
-
- 4 replies
- 852 views
-
- 4 replies
- 907 views
-
- 2 replies
- 638 views
-
- 0 replies
- 400 views
-
- 8 replies
- 1699 views
-
- 3 replies
- 1047 views
-
- 3 replies
- 703 views
-
- 11 replies
- 1876 views
-
- 3 replies
- 792 views
-
- 3 replies
- 1196 views
-
- 3 replies
- 511 views
-
- 2 replies
- 1370 views
-
- 9 replies
- 861 views
-
- 3 replies
- 631 views
-
- 4 replies
- 455 views
-
Posts
-
Hallo, vielen Dank für die zahlreichen Tipps. Ich werde das einmal "sacken" lassen und ausprobieren. Ich berichte dann, ob es geklappt hat. Gerhard -
Based on your screenshots, the P3D Simulator is installed on D:\Lockhead Martin. In the Registry the Setup Path for the Sim points to C:\ProgramData..., so there is something wrong with the P3D installation itself. -
By Homerun1978 · Posted
es sind alles die selben module..muss noch googeln wie ich die taktrate im bios einstellen muss/kann. -
Okay, so in the meantime I have sorted out the power loss / non-starting engine 2 issue... Observations from my side in respect of the current virtual pilot / copilot checklist procedures: Cockpit Prepation Checklist - copilot Fd is not activated (perhaps a beep for actioning should indicate manual input); Before Start Checklist - APU Generator not activated (immediate cockpit powerloss after APU has been activated; Engine 2 will not start if / when appropriate switches in the AIR module section have not been activated. In short, the programming actions of the virtual pilot / copilot are not complete. Please note the above is not to criticise the product but simply food-for-thought as for someone totally new to aviation could get unnecessarily frustrated. Happy flying! Herman
-
Hi Dave, I renamed the FSUIPC.cfg and assigned the throttle axis in P3D but the issue is the same. FMA shows MAN TOGA GS LOC. But I think I found the cause of this. Calibrating the CH-THR-Qudrant with the CH-Utility then the FMA changes to SRS and NAV regardless of the axis assigned in P3D or FSUIPC. And I don't have any other issues with FSUIPC and the throttle setup. But then with the CH-Quadrant-Throttles in idle detent the engines are in REV-Thrust on the ground. This is also true for the PMDG 37 and 47 and the QW 787. I have to advance the throttles a considerable way out of the idle detent for forward idle thrust. There is no way out but using the CH-Delete-Utility to delete the throttle calibration. But why does the 330 not change to the TOGA-mode despite the throttles in the VC move all the way to the forward stop or TOGA detent and the FMA shows MAN TOGA? Hope you have a solution for this. Thanks
-