Jump to content

nomdeplume

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

3 Neutral

About nomdeplume

  • Rank
    Member
  1. nomdeplume

    Saab Climbout on Autopilot oscillates/porpoises

    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.
  2. nomdeplume

    Cannot taxi - nosewheel steering inoperative

    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.
  3. nomdeplume

    Cannot taxi - nosewheel steering inoperative

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

    Saab 340 trouble with reverse thrust...

    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.
  5. nomdeplume

    Better pushback issues with Saab

    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.
  6. nomdeplume

    Another question, this time about the tiller

    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.
  7. nomdeplume

    Standby frequencies for NAV and COM really dull

    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.
  8. nomdeplume

    Airspeed too low for climb

    What version of X-Plane are you using, and what version of the MU-2? Been a while for me too (enjoying the Saab while waiting for the MU-2 update), but just did a quick test flight now and had no problems and didn't feel like I was doing anything special or unusual procedure-wise. If you have hardware controls for mixture you might want to check that they're on full; the MU-2 doesn't use them but X-Plane will lower engine output if your hardware is telling it to use a leaner mixture. Otherwise, I just put the props full forward and throttle to max, though if I recall correctly I usually watched the torque and temp gauges and limited throttle to keep them under control, and it was fine. Maybe if you can record a video or post a step by step of what you're doing we can work out what's going on.
  9. nomdeplume

    Garmin G530

    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.
  10. nomdeplume

    Dataref's

    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.
  11. nomdeplume

    Dataref's

    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?
  12. nomdeplume

    Flight Controls bug V1.5

    Great, thanks.
  13. nomdeplume

    Flight Controls bug V1.5

    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.
  14. nomdeplume

    Flight Controls bug V1.5

    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
  15. nomdeplume

    Observations Saab 340 1.5.

    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".
×