It looks like the critical altitude on the engines is completely wrong.
The GT-ISO520 used on the Titan has a critical altitude of 16,000ft, but in MSFS, the manifold pressure starts dropping almost immediately, so it seems like Carenado correctly modeled the turbochargers, but has the critical altitude set to sea level.
The external lighting switches for this plane are controlled by a panel on the left door frame. That panel is not interactive in the sim, so you canātāfor instanceāturn on the landing lights except by binding them to a keypress.
Currently trying to come to grips with the C404 Titan. I can get AP running, but canāt find where to put a target altitude, or how to set a VS to that Altitude.
Tried Elevator Trim, but the big Wheel, & the small Wheel behind the center console, both seem to have a mind of their own & wonāt hold a +ve rate of climb.
You canāt set a target altitude with this AP. You can set a VS with the small wheel besides the AP Master Button which is located below the 6 levers. When you reach the desired altitude just press ALT
What # would you set on that wheel for a climb rate of, say, 800 fpm?
I tried setting a +ve rate but it wouldnāt hold & went back down to around -1.7 fpm.
How do you ālock inā a +ve climb rate?
TG
Ok, Iāll try that, I turn the wheel, but it doesnāt hold the setting given.
Is there a VS button anywhere?
Iām missing something in the process.
TG
Hello, has anyone tried to fly at high flight levels?
Iāve tried to depart SELT Cotopaxi, runway 19 at elev. 9000 ft. According to the manual, I have selected maximum climb, 2235 rpm, full throttle and full rich below 16000 ft.
Previous posts seem to indicate that the critical altitude has been set incorrectly in the Titan. I recommend submitting a bug report to flag this and hopefully a fix will appear soon.
For those that have external FCU hardware, you can control and set the target altitude with the following simulation events, which are common in most default aircraft.
To display target ALT: AUTOPILOT ALTITUDE LOCK VAR
To increment: Send AP_ALT_VAR_INC100
To decrement: Send AP_ALT_VAR_DEC100
(You can also use ā¦DEC1000 and ā¦INC1000 to change 1,000 feet at a time)
For vertital speed:
To display vertical speed: AUTOPILOT VERTICAL HOLD VAR
To activate / deactivate VS: AP_PANEL_VS_HOLD
To increment: Send AP_VS_VAR_INC
To decrement: Send AP_VS_VAR_DEC
Just flew from KSLC to KBOI - my first longer flight in the Titan using the olā school navigation. Some observations:
No way to tune ADF 10 khz. Usually it is done by pulling the inner knob. This does not seem to work.
NAV mode of the autopilot seems to be always linked to NAV2 no matter what. While the AP panel shows NAV1 as a source (and btw I am not able to switch it to NAV2), the AP reacts only to NAV2/OBS2 settings.
the critical altitude is too low (but this was discussed in some earlier posts)
both IAS needles are modelled as if someone bent them outwards from the gauge face (this is distracting especially in VR)
The Titan has a great potential and it would be great if the issues above got addressed by MS. I will re-check and then file bug reports.
Though given my experience so far with the bugs I have ever logged on this forum, I have only very little hope. But I hope to be proven wrong.