ss8913

The Jetstream32 has this same problem with the condition levers. The Saab folks have attempted to at least solve the problem, however - on the JS32 you can't assign the condition levers to an axis, period, and you have to use the mouse manipulators... I'm hoping that this can get resolved soon. BTW I am not using autostart, I'm doing everything manually which is why I'd really like this to work. It's not that I"m losing the assignments - the assignments say "OK assigned" but *nothing happens*.. i move the lever, nothing happens on the screen. Going to go try it again. When you say "verify in the axis screen for settings" - what am I looking for there? I've used these levers for prop control for a long time, but I have made sure they're set to None before starting the process... am I looking for something in this screen that says "Saab CL" or...? I'm not sure what I'm supposedly able to verify in the axis settings screen within X-Plane?

This is the first aircraft released that is 64-bit only, and never had a 32-bit version. The Ramzess 777 for example is now 64-bit only, but if you have a slightly older version, it works with 32.. I've held off upgrading the 777 for that reason. It looks like it's "close," though, for the 64-bit xsquawkbox. Is Laminar actually involved with that, though? anyways, you're right, it doesn't *really* belong here, although it'd be helpful if your plugins should pop something up saying 'this doesn't work in 32-bit' when you try to; the aircraft actually *loads* in 32-bit xplane, but you can't do anything with it, none of the switches work, etc, since obviously all of the plugins that you are using aren't getting loaded in the 32-bit sim. So, if someone is having that problem and is confused, and searches the forum, they'll find this thread, and get their answer

yeah, sorry I did actually do what you describe, in that order (left then right). Doesn't matter, though, neither axis does anything. Where is the config file that is getting written by this? I could go in there and verify that the right axis is being written, and compare to the x-plane default config file and make sure the numbers match...?

heh.. now we need to pester XSquawbox to get moving on the 64-bit client; the Saab *cannot* be flown on VATSIM, since the Saab only works in XPlane-64bit, and Xsquawkbox only works in XPlane-32bit

OK, I've looked over the documentation on this and followed it exactly, and it acts like it's going to work, up until the point that it does not. I've got a CH Throttle Quadrant with 6 levers. Generally I use the prop levers for condition levers, in turboprops. So, following the instructions, I: 1. went into settings -> joystick axes, unassigned the two prop levers (set them to 'None') 2. Opened up the gizmo64 "Assign Saab CL" window 3. Checked the checkbox on left CL 4. pushed 'start' on step 1 5. pushed 'start' on step 2 6. it says 'SEARCHING' 7. move the left condition lever on the throttle quadrant 8. it says 'ASSIGNED ID: 34' ok, great. But moving the physical lever does not move the condition lever in the sim. I have several other peripherals connected, (and it sometimes picks up ID 21 by mistake, if I'm not moving anything, not sure what that is), but none of the other levers/etc on any other device, do anything in the sim. What should I try next?

oh, ok, I will trust it then. Also, I claim first post on the 340A support forum unintentional, though.

I just purchased and downloaded this, and when extracting the archive, my AVG virus scanner detected and quarantined the installer because it claims to contain the "Heur.dropper" virus. Please advise what to do? did a virus slip into the packaging or is AVG flagging this erroneously? I almost never see AVG complain about anything on this computer, so I'm kind of scared to run the installer now.

In the US, adding an aftermarket GPS or FMS was pretty common on the 727. There was also the CIVA INS system which can be bought for $10 as an add-on to the FlyJSim 727, which was apparently far more popular in Europe than it was in North America. I own the CIVA INS and I use it, although it requires a bit more attention and care than a GPS since it has to be manually realigned with DME updates every so often to maintain its accuracy (just like the real one). The CIVA INS is designed to be used with other planes as well.. may or may not work with the Saab's systems in coupled mode (I'm guessing not), but you could always fly the recommended headings/tracks yourself to use it for navigation. You would of course also need accurate charts, since the CIVA unit does not accept a fix name (such as ERYKA) but instead needs the actual latitude and longitude coordinates to be programmed in.

X-Plane's VOR database is in sync with the real world's. In the US anyway there are 3 types of VORs, Terminal (T) with about a 25nm range, Low-altitude (L) VOR with a 40nm range, and then you have the high-altitude VORs (H) with 100-130nm range - there are some altitude restrictions to the reception range on the (L) and (H), but that's generally how they work. Ah, here it is... (L) is 40nm from 1000-18000ft MSL, (H) is 40nm from 1000-14500 MSL, 100nm from 14500-18000, and 130nm from FL180-FL450

Right, I wouldn't expect it to couple with the autopilot or anything. I'll just be happy with the 340A the way it is, and I will buy the 340B Upgrade Pak with the FMS later after you've made that, and then have both

ok.. that's the one I meant, then. That allows direct-to fix/direct-to VOR/NDB, yes?

what's that one in the Baron/king air, then, that doesn't have the moving map? or am I completely blind?

wait, I thought the KLN was one of two default GPSes that X-Plane 10 has? I'm pretty sure the default baron or king air has a KLN in it doesn't it? There's *some* non-moving-map default GPS, anyway, which is not the fake-430 nor the fake-FMS.. anyway, yeah, I'll stop complaining about it and will just treat this plane like the JS32 and assume it has no RNAV capability, which isn't really a problem in north america as you mentioned.

granted, it looks and operates like crap; I was more wanting the KLN90B for this, not the fake-430, but I see your point (the X-Plane "430" doesn't do half the things that a real 430 does, I've used one fairly extensively real-world). If you just want something that can take you direct to an IFR fix, the KLN90B would be acceptable. My concern with this new feature is that it only handles fixes (a real GPS would have the VOR stations and NDB stations in its database also), making it kind of an.. oddity. I know of no real world instrument that *only* handles fixes that aren't VOR/NDB stations and ignores ones that are...? I could be wrong on that, but I've never seen such a device. Oh well, here's hoping the next version of X-plane (11) has some better default gauges that everyone can leverage for cases like this, which look and perform closer to reality

why not just simulate an aftermarket GPS unit installed into the panel/etc? Could just use the default X-Plane GPS and put it in a box mounted.. somewhere? Or even a pop-up 2D panel with the X-Plane GPS (like the one in the Baron).. that way you could do real GPS procedures/approaches with it like you could with a real Saab 340A that has an aftermarket GPS receiver installed, as I'm sure many do. The Boeing 727 never had a factory GPS or FMS either, but I know a real-world 727 cargo pilot who said that when his cargo airline was still flying the 727, they had aftermarket GPS units in them, and the few planes that they got from American Airlines actually were fitted with aftermarket FMS... fairly common in aviation to upgrade avionics in older planes, I've seen DC-3s with GPS, and the 1972 Piper Arrow I used to fly certainly didn't come with that Garmin 430 moving map My concern is that the pop-up window is kind of a ... realism-buster, when done this way. I know you're trying to get the plane out more quickly, so i kind of see why you did this, but I'm hoping that version 2.0 will have a more realistically modeled aftermarket GPS, as I'm sure any real Saab 340As operating in the Eurozone have. For now I will just elect not to use this feature, as I fly mostly in the US, Canada, and Mexico (and sometimes Australia) where this does not appear to be a problem.

The JS32 is a great plane, albeit small. The Saab 340A is significantly bigger so it fills a somewhat different role. *I must have both*.

Tutorials are good. All turboprops seem to be slightly different; for example, I thought that I could jump from the Q400 into the JS32 no problem... 2 engine fires later, I had to go find a tutorial on how to properly start it since the order in which you do things matters. Moreso on the older stuff, the Q400 is kind of a pussycat by comparison.

EDT = GMT-0400 PDT = GMT-0700 EST = GMT-0500 PST = GMT-0800 there

EST... aren't there multiple timezones with this abbreviation? In the USA, EST = "Eastern Standard Time" (which is only used during the winter months), but I believe it's also a european(?) timezone as well...?

heh.. I made a joke about the a320neo being like a mime, in that it was French and was trying to kill me (the AIRAC cycle I was using had incorrect crossing altitudes for one of the STARs into KLAS and almost flew me into a mountain, and it likes to dive at the runway unexpectedly under certain wind conditions with the A/P on, at least in the version I was using back in may when this happened), and the moderator at x-plane.org apparently banned me from the shoutbox. so yeah, I'm kind of surprised that calling the developers' work 'vaporware' is ok but making a joke isn't. I even PMed the moderator and apologized, which he didn't reply to, and I still am apparently banned from 'shoutbox' 4 months later.

oh, one question; will this plane be 64-bit *only* or will it be 32 and 64? I ask only because with xsquawkbox-64bit still not available, I can only fly on VATSIM in 32-bit mode...

http://en.wikipedia.org/wiki/Erieye_radar That's what the pod is/does Not a giant death ray emitter, which was what it looked like at first Too bad, though, the death ray emitter would have been easier to model

what does that pod actually do? is its function modeled in the sim? Is there at least.. like some kind of button or switch to turn it on so we can pretend, if it's not actually modeled?

You'll put someone's eye out with this thing... I'm hoping that this is the start of a series of study-level simulations from you guys. There can never be enough of that, in my view

you might get the plane before the manual so you can figure it out by trial and error, so that when you DO get the manual you'll understand what it's talking about also... have you guys released any pricing information for this yet, or do we have to wait until the Day Itself to know how much it will cost?