JGregory

Our startup procedure is not just "the way to do it in the sim", it is actually a correct start procedure as per the manual from Saab themselves and as per our Saab consultants. What you are describing is "dry motoring" of the engine, which is a different start procedure. Perhaps the procedure in your manual was specific to that airline at the time your dad was flying for them. Dry motoring is part of our simulation, if you choose to do that type of engine start. Please see the following excerpt from the Saab Manual... SAAB 340A AOM Rev 40 - Complete 868.pdf

I'd be interested in knowing more about this. Can you explain what you mean by "engine selector" ? There is a procedure called "dry motoring" where you leave the condition levers at cutoff and then advance them to start, which we did simulate... is that what you are referring to? All of the development we did was based on exhaustive research, real world manuals, and consultation with real world Saab 340 pilots. I'm fairly sure we did not make an error in the starting procedure. If there are "alternative" procedures we are unaware of, I would like to know about them. Is there any chance you can get us a copy of the manual that you are referring to?

John, We didn't implement the test panel functionality because our consultants (all real-life Saab 340 pilots) told us they actually never use the test panel. As far as the future goes... who knows... we may implement this some day... never say never I believe you can just re-run the installer and select the liveries that you wish to install.

lk, Most of the dials/switches/etc. in the Saab use custom DataRefs for manipulation and animation. There is no published list. However, once you have purchased the aircraft, if you submit a request for a specific DataRef we will be happy to provide it to you.

There is nothing outstanding in the log.txt that would indicate why you are having a problem. Please list the exact steps that are required to reproduce this issue so we can try it on our systems.

LES/CMD/CW/button/AP_disconnect

If your getting crashes there may be something wrong with your installation. To test the Saab issue fairly, you should download the demo of X-Plane, disconnect all hardware, install Gizmo, then install the Saab and see what happens.

Please unplug all your hardware and make sure the weather is set to CAVOK. The report back here if you still have a problem.

http://www.x-aviation.com/catalog/contact_us.php

Check your trim settings.

Martin, There is absolutely NO reference to the Saab in you Log.txt file. You need to run the Saab and try to recreate the OOM, then send us the Log.txt file from that session. If you are getting OOM issues with other aircraft, then the Saab is obviously not the problem. As no one else has reported an OOM issue with the Saab, my guess is the Saab has nothing to do with your problem. You should definitely "clean up" you scenery issues, and then remove all plugins and put them back one at a time as a test.

Put the camera in the position you want... then press "control" + Keypad[num] to save the view for future use. The Keypad[num] can be any of the numeric keys on your keypad. When you want to use that view simply press the Keypad[num] and the camera will move to that position.

That's a bit of a stretch, don't you think? I could easily find pay ware aircraft where the interaction is much worse. Across the board is not going to happen. We are going to add scroll wheel manipulators for the OBS1, OBS2, and HDG dials on the center console. First, you can't have click-to-toggle on a three-way toggle switch, ie. which way should the switch move if it is in the center position? Second, ALL of the two position toggle switches are currently click-to-toggle. Third, if the drag on some of the three-position switches is too much, please be specific and we will look into it. As Cameron stated, the answer to this can be found in the forums. But the short answer is that X-Plane does not always use the same "slot" for assignments between X-Plane sessions, so there is no way to know what the previous assignment was. Default slots (prop feather) and single manipulation of both condition levers will not work due to the complex programming involved in properly simulating the Saab engines.

There is a command for this... LES > CMD > CW > button > AP_disconnect

We have no plans to implement FMS/GPS waypoint display on the EHSI at this time. It would be somewhat redundant since these waypoints are already displayed on the 430/530. As far as this being easy to implement, unless you have written some complex navigation algorithms for X-Plane, I wouldn't make any assumptions.

Well, that depends. If you enter a flight plan on the GPS then no. If you simply use the NAV1 radio, then yes, as this feature already works with the NAV1 and NAV2 radios.

Well, the overhead should be rather simple, maybe we will do that next.

The 530 would have been our preference as well, but the panel is just not big enough to accommodate it with the configuration of other instruments that we have. And if you don't want to use it, you can simply turn it off. There is a full compliment of radios and navigation instruments that will allow you to fly without the GPS.

Andre, Your frame rates will not necessarily be tied directly to the number of flight models that you set. Since your frame rates are OK, then there is nothing to worry about where that is concerned. There are far too many factors that affect frame rate for a simple discussion of direct causality. As long as your problem (oscillations) are fixed, then its all good

It will run the flight model portion of X-Plane more frequently.

Andre, Very strange, no one has ever reported an issue like this. Please provide some more info... 1. You computer hardware and OS specs. 2. The version of X-Plane you are you running. 3. Are you using hardware (joystick, etc.) ? 4. Your frame rates. 5. The plugins you have installed, if any. If you are using hardware, please disconnect all of it and let us know if the problem still exists. If you are using other plugins, please remove all of them and then test. You might also try increasing your flight models per frame setting (Setting -> Operations & Warnings).

Kieran, Not sure what's going on with your file. It is VERY large. But again, without the entire Blender file I really can't offer any more insight.

You shouldn't have to do that. What scripts are you using?

Kirean, For starters… you have the manip type set to noop… so your manip is basically doing nothing! I would need the blender file to help you any further… but I can't guarantee when I will be able to get to it.

Without having your source files it is a little hard to help. Maybe post some pics of your blender file showing the manip. Is your manipulator in the cockpit.obj file?