nomdeplume

I assume you're talking about the Takeoff Config warning occurring when you push the power level beyond a certain amount? The Systems.pdf has a list of the things it's looking for (bottom of page 182); pitch trim not good; too much flap; or condition levers not set for max RPM. I'd almost bet money it's the last one, as the condition levers max RPM setting is a detent just before the maximum position. If you just jam them all the way forward because that's what you do on most aircraft, you'll be in the weird "T/M" setting which I don't fully understand, rather than max RPM, and the takeoff check system will be angry with you.

Pretty sure it's just the XP11 built-in GPS using XP11 navdata. Maybe double-check the X-Plane 11 directory is set properly and your XP11/Custom Data/cycle_info.txt shows that is has actually been updated?

That would probably be it, the Saab model does not use a separate range for reverse like some other aircraft, so you have to be careful how much you pull the power back. Keep an eye on the virtual throttle in the 3D cockpit and only pull your physical throttle back to where it 'snaps' to the flight idle position when you're landing. You can also use the popup to keep this on screen at all times. After touchdown, gently pull it back further to go into beta and engage the reverses. If you do it too quickly (especially if you're landing fast) it'll overload the engines and they'll shut down. The same applies when powering up for take-off as well; it does not respond well to sudden throttle changes. You can easily redline the engines if you don't ramp up the throttle gradually.

That looks right to me, except my X-Plane 11 was actually detected automatically, so it's only the GNS430 data that is manual. Do you have the X-Plane 11 path set correctly on the Settings tab? And just to be sure, did you do the update via the "Addon list" button and they're all green? Current cycle should be 1809 rev 1. You can also check the files to see if it's been updated: For X-Plane 11 default GPS, it's X-Plane 11/Custom Data/cycle_info.txt For X-Plane 11 GNS430 data, it's X-Plane 11/Custom Data/GNS430/navdata/cycle_info.txt If FMS Data Manager says you're all up to date but those files don't have the information about the current cycle in them, then you've probably got the wrong path for X-Plane (should be the base directory, e.g. E:\X-Plane 11 for me). Now... since your issue is actually an out of date ILS frequency, from what I understand this is most likely going to be picked up from the file X-Plane 11/Custom Data/earth_nav.dat. This should be updated by Navigraph. That file acts as an override for X-Plane's default data, so if you don't have third-party navdata then X-Plane would be using its default data, from X-Plane 11/Resources/default data/earth_nav.dat. With the current Navigraph data (AIRAC 1809), I have this in Custom Data/earth_nav.dat: 4 61.406722222 23.571991667 368 11010 18 244.445 TP EFTP EF 24 ILS-cat-I 6 61.417238889 23.623108333 368 11010 18 300244.445 TP EFTP EF 24 GS 12 61.417238889 23.623108333 424 11010 25 0.000 TP EFTP EF PIRKKALA DME-ILS 11010 = 110.1 which matches what's shown on the current chart. The default data that ships with X-Plane has: 4 61.406722222 23.571991667 415 10970 25 244.445 TP EFTP EF 24 ILS-cat-I 6 61.419186111 23.621169444 415 10970 25 300244.445 TP EFTP EF 24 GS 8 61.423786111 23.646497222 0 0 0 244.445 TP EFTP EF 24 MM 7 61.446597222 23.748355556 0 0 0 244.445 TP EFTP EF 24 OM So if you don't have the updated data loading in the sim for whatever reason, then you could probably do the approach with 109.7 instead.

Navigraph's FMS data manager will update the navigation data files for X-Plane and its addons. You can also manually download the files and install them yourself, but if you're using Charts you probably already have a subscription. I think the Saab uses the default X-Plane files since it uses the default GPS, so just adding X-Plane and pointing it to your install should do the trick.

Are you remembering to set your altitude target beforehand? Sometimes I'll forget to reset it after approach and it'll be very low. Then the AP will level out and it will start to accelerate like crazy. Also you might want to consider engaging the flight director and climb/nav modes and hand-fly it prior to engaging the AP. If you enable the AP when you're already following the FD cue you'll get smoother and more predictable actions from it. If there's a big difference then when you enable the AP you can get significant pitch moments as it tries to sort the situation out.

Not at my computer right now so I can't check the exact text, but... (Note that I only use XPlane 11 so if you're on 10 the interface probably works differently and this won't help much.) First, load up the 340 into the sim; the controls will be present in the command list without the aircraft loaded but they won't have any descriptive text which makes it difficult to find the right one. Then go to the controls configuration, and hit the button to assign a custom command for the button you want to use to toggle the tiller. Then what I normally do is type anything in the search box, then delete it (backspace over it) - once that's done the entire command list will be accessible but collapsed. You should then be able to find the LES node easily in the list and expand it. If you still can't see it then maybe the aircraft isn't being loaded properly? But I would be surprised if you could fly it at all if it can't even load the custom commands.

There is a NWS binding, just not the X-Plane default one. Works flawlessly for me. LES/saab/NW_steer_ON_OFF

When I've encountered this it's always been when I've been trying to slow down quickly after a forcing a landing in which I'm way overspeed. If I'm more gentle with going to reverse it doesn't occur; i.e. if I don't just immediately jam the power levels to full reverse it's fine. I don't know if it's a bug of some kind, or if it's something like the sudden blade pitch change overloading the engines which then shut down to prevent damage.

I have lots of problems with Better Pushback and the 340, too. Mostly it's okay if you just go back and straight, but if you try to get it to turn you at all it'll get very confused. My speculation was that the Saab's doing something to prevent the nose wheel from turning when the aircraft is stopped and that was throwing off BP. But on the weekend I did a flight with DDEN's Challenger 300 v2 and BP freaked out trying to push that aircraft back as well. Plus there's plenty of clips of it freaking out with all manner of different aircraft. So I think the plugin just has some issues in some (many) situations, especially if you ask it to do anything beyond a straight push.

On technique, generally one would switch nose wheel steering off before or during the takeoff roll; once you've built enough speed the rudder should have enough authority to keep the aircraft centred. You don't really want to be turning the aircraft with the nose wheel once you're above taxi speeds. Same thing with landing; use the rudder after touchdown until you slow down and lose authority, then enable the steering. You can also use differential braking. I don't know the specific normal employment in the SF34, i.e. whether the pilot actually pulls the tiller during the roll or if they leave it in and just use very very gentle movement of the pedals until liftoff; or even if they line up straight and disable the tiller prior to starting the roll. If you're reasonably straight by the time you've drifted off the centreline the rudder should be able to provide enough authority to correct. X-Plane in its current state also adds the complication that propwash is badly modelled with any sort of crosswind, so you're probably getting a lot less rudder authority than you actually should have at any given speed/power setting; which in turn means you probably need to enable steering at much higher speeds than in real life. So I think as always we need to accept the simulator's limitations and do what works within it. For me, I disable the tiller during the takeoff roll at around 50-60 knots (then stomp on the pedals as needed), and when landing I use (heavy) rudder inputs and (light) differential braking for keeping straight until under the same speed before enabling the tiller. I also find nearly all X-Plane aircraft will have more steering authority from the pedals with nosewheel steering/tiller enabled even without actually using the tiller axis to steer the wheel, so effectively I get three levels of "sensitivity" - rudder only, tiller enabled but only using pedals, or pedals plus tiller steering (only for low speeds). If you don't/can't map the tiller toggle to a button on your flight controls (or at least to a keyboard button) for easier use, then probably using differential braking until you're slow enough and controlled enough to fumble around with the mouse is the best bet. If you don't have separate toe brakes either, then you're probably in for a bad time without an easy way to enable the nose steering.

They're definitely considerably darker but I don't have any problem reading them. The "Digits" rheostat does control the brightness but I think it starts on maximum anyway. A screenshot might be helpful to indicate if you're seeing something abnormal or if perhaps your monitor is just a bit darker or something? Here's mine for a comparison, also with the popup.

I think the 530 is just the X-Plane default GPS, does it work in other aircraft? If not then I'd try running the X-Plane installer (or do a repair if you use the Steam version) and see if it finds any missing files. Also please post your logs - Log.txt and GizmoLog.txt in your base X-Plane directory.

Hmmm... I don't have those. Only things I have under LES/saab are anti-ice, and a search for 'ias' finds only LES/CMD/IAS/test_button and LES/CMD/MSP/button/ias.

Probably talking about the continuous/automatic ignition switches. Edit: this reminds me, I was looking for a way to bind the 'speed bug' adjustment to a controller but could only find the button press (test) binding, nothing for 'turn the knob' bindings. Is this hidden under a different name or if not, could it be added?

Great, thanks.

Further to the above post, two videos which hopefully show the behaviour we're trying to describe more clearly. https://youtu.be/1E_myS6JlJk - showing cockpit and then external views with the control surfaces and flight controls displayed in the data graph window. First neutral controls, then full left rudder followed by full right, repeated for both views. https://youtu.be/JU_MINjJy80 - showing external view with the weather and flight controls displayed in the data graph window. This video is with neutral controls.

I get this a lot - tail waggling and elevator flapping, sitting on the ground at startup. Went to the external view now after removing all ground elements except nose wheel chocks, connecting GPU, and turning on the batteries, external power, nav lights, all 3 avionics systems, arming the emergency lightning and opening the cabin and cargo doors. I don't think any of those are necessary (it'll start flapping immediately), but wanted to be thorough. Edit: had to restart for TrackIR, and went through my setup slowly. At spawn, only the elevator was fluttering; removed the ground elements one by one with no effect. Turned on both batteries and checked - immediately the rudder started its waggling. So whatever's going on is dependent on electrical power and the batteries are sufficient. (I have the GPU connected but external power is not yet enabled on the overhead.) Location is TNCM parking A4, using X-Plane's built-in real weather. I've attached the METAR.rwx in case it is weather-specific. In the cockpit view, the pedals move in sync with the rudder movement. Hydraulics look normal for engine off (attached screenshot). Applying my own pedals does affect the rudder as expected, but the 'random' waggling continues. At full deflection it'll jerk back to what appears to be a perfectly centered position. The winds are steady at 10.10 (knots, presumably) but variable direction (060 thru 140 according to the METAR, which looks about right for the data outputs). METAR.rwx GizmoLog.txt Log.txt

Excellent news, thanks very much! Found another minor thing - somehow my altitude selector got stuck on xxx50 ft (49.183228 ft to be precise) and I can't fix it back to displaying even 100 foot increments, so it looks a bit awkward. No idea what I did to achieve this state, it's been fine for my first flew flights with the update, and I can't be sure exactly when it 'broke'. Maybe if it could be forced to an even 100 feet at startup that would fix it, or alternatively make the lower bound clamp it to 100 feet so you can just roll it all the way down to 'reset' it? On further investigation it looks like it's a standard X-Plane dataref that may be persisted, so maybe it was another aircraft that messed it up? I loaded the MU-2 and it reset the selector to 5,000 feet and when I switched back to the Saab it's fine. So it can be fixed easily enough but it might be worthwhile making sure the value when the aircraft is loaded is "valid".

The autopilot roll behaviour does seem a bit aggressive and uncomfortable for the passengers, but perhaps the Saab is normally flown by hand for turns rather than on AP? Another thing I've noticed is that course corrections are very aggressive. This can most easily be demonstrated in HDG hold mode which small changes to the heading; the aircraft will roll quite a bit more than seems necessary in order to align on the new course. So perhaps you could also check with the pilot if the autopilot is really that excitable? One interesting thing I found is that just switching the nav system results in a series of rolls. As in: Set both NAV radios to the same VOR. Get established on an inbound or outbound radial using the NAV AP mode. Make sure both CRS1 and CRS2 are set the same. Switch to the right-side nav (or vice versa). My expectation: Minimal (if any) change in aircraft roll attitude, since it's still following the same course. Actual result: Fairly steep roll right, followed by another roll to the left to re-establish on the radial. I don't know if X-Plane can/does model the precise location of the radios within the aircraft and these rolls are due to the aircraft finding itself slightly off the ideal course, or if there's something else going on with switching autopilot control source, but either way this strikes me as "unexpected behaviour". Another little thing - if you use the HDG Slave button to set the AP heading to the current heading it works as expected, but the previous seems to be retained by the heading selector dial on the center pedestal so upon the next adjustment it'll start from the previous position rather than the current position. This also results in some unexpected and confusing behaviour. I assume the heading is set based on the animation value of the dial or something? In that case, maybe syncing the dial when the heading slave is used would be a viable workaround. I think something similar occurs when using the OBS dial to change CRS1, as I've seen that jump around in weird ways though I haven't fully sussed out exactly what triggers it.

Nope, sorry, still lives in the "Unclassified" section at the bottom as "Passenger Variant". You could try ticking the "Show extra aircraft from old versions" checkbox, though it shows for me without it.