ss8913

I noticed that with my TrackIR4 if I wasn't zoomed in to the VS wheel far enough, the wheel would look like it was working, but not actually change the indicated VS on the display. If i zoom further in, it works.

interesting. do you have any starting issues when doing a manual start? or is this localized to the autostart?

are there custom failures modeled in the Saab? Do you have X-Plane's random failures turned on (and does the Saab honor that setting or does it override?) ... you could have just had a random electrical failure injected by X-Plane?

I generally have to do this on all planes when I fly on VATSIM. Turn the plane's sound down, either from within X-Plane's audio control panel or through the plugin volume controls (every third party plane seems to implement this differently, so it's one of the first things I have to teach myself ), so that I can hear ATC, since xsquawkbox does NOT have a volume control.. Also I noticed that you have to turn up the audio panel's COM1 slider to see even the text ATIS when you've got the radio tuned to the ATIS frequency. That was a nice touch, it makes sense and it's realistic (well, text ATIS isn't realistic, but you guys don't have control over that, and you certainly can't get a real ATIS with the audio panel set to zero volume in the real world ).

instrument flight is usually still taught without the use of GPS, at least in the United States. You can fly any V or J airway in North America without GPS or any kind of RNAV equipment. I believe you do need it for our Q airways however. Just bring up charts (www.skyvector.com) and use VOR/DME to navigate, maintain your MSA and you should be good to go. Sometimes a fix can be identified by two crossing radials or a radial + DME. If you ever wanted a really good excuse to learn to read IFR enroute charts, well, here you go, you have a Saab now, and the Saab wants you to be educated

hm.. I can't think of anything *you* could be doing wrong that would cause it to hang at 82C ... usually pilot error will cause it to not start at all, or to catch on fire. I think you're probably looking in the right place, with the gizmo plugin and the other log files that you've pasted here. I'm not a developer, though, so I can't answer you as to what *is* going on, but I'm *fairly* certain this isn't a case of pilot error.

make sure the condition levers are at MAX, not at the detent that is further forward than MAX. I am not sure what that one is, I have to read the manual again, but the plane is not happy climbing with the levers in that position, even from KSEA which is 400' MSL.

oh you never mentioned the name of the addon for which you've been pasting those config snippets.. I'll take a look at xjoymap, thanks The saab will 'speed up' when you pull them back because there is a detent on the CL past 'MAX' that you generally don't want to use in most cases.. I leave mine at MAX during takeoff and then at cruise I pull them back into the green arc, just like I used to do on the Piper Arrow, and like I do on other turboprops, to keep the prop RPM in the green and provide more efficient cruise settings. Also, like the JS32, *easy on the levers*. They don't like being jerked around. When you move the throttles, you're not just changing the engine RPM, you're changing the torque - with a constant-speed prop system, oil has to flow in/out of the prop hub to adjust the propeller pitch so there is some delayed reaction when moving the throttles as everything adjusts to the new settings. This is something that X-Plane, and especially planes like the 340A and the JS32, model very well, which MSFS never quite got right.

huh, maybe they released an update(?) .. I remember when I bought it (the JS32), I had this problem, I asked on their (JS32) forums, they said, "that's just how it is and we can't fix it," at least at the time.

it would be nice if the drag-and-hold made the numbers change a LITTLE faster though.. just my opinion. Not a lot faster, since as you said, fine adjustments, but maybe juuuust a bit faster would help. Or make it configurable somehow, if that's even possible.

even better. XP10.x updates are free. I like free. and updates. So free updates, you can imagine how I feel about those

it seems to be a common issue with properly-modeled turboprops. As I stated earlier, the JS32 also has this issue, and they have no way to assign an axis to the CLs *at all*, so kudos to LES for coming up with a solution. Maybe the JS32 folks will borrow the method? Perhaps this is something that Laminar can address in XP11 though, so that these kinds of workarounds by third-party developers are no longer needed in the future, and XP itself knows how to properly read a 'condition lever' for a turboprop?

flight surfaces move on the ground in the real world, at least on windy days in the pipers and cessnas that I used to fly. Obviously those don't have hydraulic control surfaces, but for all I know the Saab only uses the hydraulics for the flaps and the gear and doesn't use them for the elevators, ailerons, and rudder (?)

A/T was removed from the CRJ200 because CRJs don't have an autothrottle at least not as-delivered from Bombardier. But, that's getting off-topic...

You can probably use UFMC with it. Your time and struggle to make that work is still less expensive than the $20k+ you'd have to pay an avionics technician to install an FMS into a real Saab 340A (which I'm sure has been done, somewhere in the world, at some point). rigging an 'aftermarket' FMS into an older plane is a completely realistic thing to do. The LES folks have given you an as-built-from-Saab 340A, identical to how Saab would have delivered it to you. What you do with it after you buy it is up to you, your mechanic, and the FAA/EAA/etc. The lack of 32-bit is really only a problem for VATSIM flyers currently. Once XSB64 drops, there will be absolutely no reason whatsoever to use 32-bit X-Plane anymore. I hear they're "close" with XSB64. I'm considering talking to them and seeing if I can lend a hand with it, since I'm a software developer/systems engineer myself, and I really really want to see it done. I hope they are not holding up the entire project because of Mac audio issues, though; they should release the windows version now, that way people can find bugs/get them fixed/*use the thing* while they work out the mac audio issues... but i don't know the whole story, there may be more going on there than I'm aware of.

Yes. KPAE (the payware one). However, looking at the same scenery from inside the cockpit, the frame rates were fine... I'll post my render settings later, I'm not sure if I have HDR on or off actually.

I'd bet that Crossair and other operators likely replaced the altimeters for their own needs, and what the team here has modeled is a 340A as it was delivered from the factory. People modify cockpit instrumentation all the time, it's very common. I've never seen two piper arrows or cessna 182s in the real world that were identical to each other. Each individual aircraft is different.

I like how the control surfaces move on their own during gusty wind conditions. Have seen this before on the Pipers I used to fly - although.. is this something that happens on a plane with hydraulically controlled flight surfaces? the rudder pedals in the cockpit move along with the rudder, which I wouldn't expect in a cold and dark state with the hydraulic pumps off/system depressurized? Or is this just something that X-Plane does?

Jim - it sounds like what you're planning in that update should solve the problems that JimboG and I are having - I will submit a full report as soon as the update has been released and I have given it a try.

I'm having exactly the opposite. In the cockpit (shift-9 view, with my trackIR4), frame rates are fine/comparable to other planes. In the external view (shift-4 view) they drop to 7-8fps, in the same location where the cockpit view yields 17-30 FPS. If it helps: specs: i7-2600K CPU 8gb DDR3 ram GTX570 4gb video card win7 professional x86_64

Unlike in MSFS, the toe brakes do NOT release the parking brake in X-Plane, at least not on any plane I've flown in the sim. Which is realistic, since in the real world, the toe brakes do not, to my knowledge, release the parking brake either. So the rudder/toe brakes settings/assignments are not/should not be relevant to this problem. Try mapping a key to the parking brake toggle like the V was in the default settings, that should fix it (?)

it's not just the 'right' one, it seems that if it picks up the wrong ID and you restart the process, and then it gets the correct ID, you have to uncheck the box to make the lever move. I've tested this a few ways and that behavior is consistent. Regardless of the position of the checkbox, when the lever moves correctly, it's "working" - I've done a few flights with it now, regardless of the checkbox indicator, if you can get the lever on screen to move with the physical lever, that is the success condition, and once I get it to that point, it works flawlessly. All of that said, once I get to the point where it works and once I figured out that the prop RPM gauges seem to be driven by the AC inverters, the plane flies really well, and I like it a lot. Although if you advance the condition levers too fast, you'll get to a point where the turbine is spinning but the generator won't engage and the prop RPM shows 0... have to reset the plane to fix that - but that belongs in a different thread, and I'm not 100% sure if it's "supposed to" work like that or not.. as I've never flown a real one.

ok more info on this: 1. I got it to work (but:) 2. Please make a way to manually type in the axis ID - that would simplify my life quite a bit since I know which axis # I want here. I have a faulty potentiometer, it seems, in one of my toe brake axes which is causing ID 21 to pop up a lot instead of 32 & 33 which I need. 3. I got the left one assigned properly, then went to do the right one. After fighting with it for 10 minutes I got it to pick up axis 33 instead of 21. Great. but it still didn't work - the left one did, the right one didn't. So I took a wild guess and *unchecked* the "right CL uses joystick" box - which shouldn't work, but *that fixed it*. That might be something you want to look into as that's not how it's supposed to work ... but it does, so I'm going to go fly it. Please let me know if there's anything else you want me to check/help test/etc, I'd be happy to follow a test plan and post a full report for you to look at. Also, letting me manually key in the axis ID would be super helpful - although if you're lowering the detection sensitivity, that might also solve the problem in the next patch.

pushing V toggles the parking brake, with XP10's default key assignments. It's working for me. Check your XP key assignments and make sure it hasn't been re-mapped?

Right, because people read all of that before they come here to complain I'm a software developer myself, I am always telling people to RTFM but they never do... heck most people don't even search the forums Oh well, here's hoping XSB64 is available soon. I want to fly the saab on VATSIM...