• Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About nomdeplume

  • Rank
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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?
  7. Flight Controls bug V1.5

    Great, thanks.
  8. Flight Controls bug V1.5

    Further to the above post, two videos which hopefully show the behaviour we're trying to describe more clearly. - 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. - showing external view with the weather and flight controls displayed in the data graph window. This video is with neutral controls.
  9. 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
  10. 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".
  11. Observations Saab 340 1.5.

    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.
  12. Passenger version

    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.
  13. Landing Lights?

    The MU-2 has extendable (or retractable, if you prefer) landing lights on the forward fuselage. The switches have 3 positions: Back position - the light is off and RETracted. Middle position - the light is extended, but not illuminated. Forward position - the light is extended and illuminated. According to the plate in the aircraft, the lights should only be extended at speeds below 175 KIAS (same as the landing gear). But I don't think anything bad actually happens in the sim if you exceed this speed with the lights extended. I quite like the extension animation; if you flick it straight to the forward (on) position, it won't actually light up until fully extended. Nice touch! (And the MU-2 looks almost as cool as a PC-12 with all its lights on.)