dybal

Marianas map is OK, landed on Rotas International and the runaway lights were on at 4PM

Got the same. In previous version, white lights would be turned on when ATC received an Inbound radio call, then when a Landing Confirmation was sent to ATC on final, red light woould be turned on ponting to the runway "head", and spotlights would light the runaway head. In 2.1.11.21408, after the Inbound call I can see the blue taxiway lights, but no white runway lights. After the Confirm Landing call on final, the spotlights would be turnoed on, but still no white runaway border lights, or red runaway approach lights

Thanks to jean-knapp, I learned that in the current version of the mod, to be able to add waypoints to the end of route, the UFPC waypoint page must be in WPT mode (by default it's in FYT mode... you know the current mode by the text left of the waypoint number in the waypoint page). To change modes, select the waypoint number in the waypoint page using up and down on the main UFPC switch, then click right in rthe UFPC switch (towards the ' menu' label) to change modes.

Just to document the mod, the U key (cage/uncage) doesn't change the HUD.... but there is an entry in the UFPC menu that does: choose Misc (0), then Drift (6); there are two values: NORMAL: in the presence of crosswinds the FPM, waypoint mark (circle) and pitch ladder are rendered off-centre (the crosshairs, waypoint hbearing caret and aircraft heading mark in the bearing tape stay centered) DRIFT C/O: the FPM and ladder are centered even in the presence of crosswinds Version 0.3.0b

Thanks, Eduardo, I didn't know about that! Yes, the mission (thanks for it, by the way!) mentions a crosswind in the first leg. Is that a DCS thing (the HUD compensating for crosswind), or does the real Super Tucano avionics do it? (how could it know about the crosswind? By detecting a lateral drift through the sequence of GPS coordinates?)

Did the Landing training mission tonight, the straight in approach... did it something like 4 times (with one crash), in the last one I started figuring out that to keep the FPM marker in the brackets by trimming alone after lowering the landing gear I have to lower the speed as I trim the nose up. Anyway, in all the tries the HUD was messed up, with the FPM marker and the pitch ladder off to the right relative to the nose cross marker and bearing tape (heading marker included)... Version 0.3.0b and 0.2.0b (didn't try the 0.1.8b).

Thanks for the tip! There's a lot of commands for a newbie to learn Is the saved head position kept between DCS sessions? (i.e. can it be done just once?) I probably will get a real head tracker set-up... VR would look as the way to go except for the not fully clickable cockpits: can't use keyboard keys without looking at the keyboard (and right now the exchange rate down here in Brazil makes VR sets *really* expensive )

Now being able to find the next waypoint direction on the HUD's heading tape, I advanced on the Waypoint Navigation Tutorial... found two problems: - the Auto Rudder switch doesn't stay at the engaged position (it moves back to the power position when the mouse button is released): works in 0.1.8b, but doesn't in 0.3.0b - when cycling through the waypoints in the UFCP (after pressing WPT/4 button), the list goes form the last defined waypoint (in the case, 6) to the first airfield waypoint... the exercise says there should be a "next" waypoint, with zeroed data, between the last defined and the first airfield waypoints, and that zeroed data could be filled in to create a new waypoint (I modified the sixth waypoint with the supplied coordinates just to finish the exercise). Doesn't work in both 0.1.8b and 0.3.0b. The strange part is that it worked on rudelchw's video on this tutorial.

Follow-up on the HUD cropping the borders in VV/VAH mode: When I used a head tracker (ViewTracker from Steam), I noticed that if I moved my head up and closer to the HUD, the cropping of the borders was gone. Without a head tracker, I have to use the Move Camera Up from the View Cockpit section (zoom in wouldn't do, it just enlarges the current view without changing "head" position...) Version 0.1.8b started with an adequate head (camera) position, but 0.3.0b doesn't.

Did the first training mission, but got some trouble with the second one (the one about navigation)... the HUD content is bigger than the "projection area", so the content's "borders" are clipped out, including the angle of attack at the left side, the waypoint's heading caret at the top and the "roll with landing gear down" marker at the bottom. Version 0.3.0b

I have some trouble when I start the engine: it spools up to 15.2% then spools down. It happens in a Instant Mission or the Startup, Taxi and Takeoff training mission, with 0.1.8b and 0.3.0b, Steam DCS World and Standalone DCS beta versions. I tried with Thrust/Throttle bond only to keyboard and bound to an axis in my joystick. The dsc.log doesn't show anything. I removed the i18n folder from the track zipfile to reduce its size. EDIT: Found the problem: I pushed the throttle forward and then all the way back... that's CUT-OFF instead of IDLE... SUGGESTION: can the tooltip when hovering the mouse over the control include the control's current state where applicable? For throttle that would be nice, since in several the back positions the handle hides the markings. dcs.log A-29B - Training - M01 Cold Start (by Rudel_chw).miz_30112021_21-15.trk