JGregory

I you are still running XP9, that is your problem.

Please send us a copy of your GizmoLog.txt file from when this error occurs.

Be forewarned that using other scripting methods to interact directly with the Saab may cause unexpected problems, which we will be unable to support.

I have sent your questions off to one of our test pilots and will let you know. In the meantime, maybe another user will have some insight.

That is correct. I don't believe there is any way to do this without a plugin as there are currently no DataRefs or Commands for ALL igniters.

It may be that the JAR A320/330 was designed with that limitation. However, there is no such restriction in X-Plane.

We will need more info... such as your render settings. In addition, the Log.txt file you attached was created when you were running an aircraft named "DC9-32", not the Saab. On top of that, the Log.txt file shows that the "FlyWithLua" plugin crashed running "RTH".

FYI...There is no such limitation in X-Plane.

Use the "drag_axis_pix", you will get much better results.

Please post a screenshot of this window as well as your log.txt file.

We may consider a "menu" item in the future. I have no idea what GSX is. It is a requirement that you be in "3D Cockpit" mode in order to use manipulators in X-Plane. The click spot is there (thru the fuselage wall), you just need to search for it. Again, you need to be in "3D'cockpit mode to use manipulators. Unless there is bug that I don't know of, you should be able to click on the cargo door handle to close it. The doors will only close with "Auto-Start", as all systems are reset. If you do a manual start the doors DO NOT automatically close. I'm not sure if that is "possible" in the real aircraft. I would think your takeoff run would be rather long.

Seems to me the same problem would apply to animation or hide/show. You need to set the parameters in either case. Except you re making more "state" changes in the OBJ file with hide/show. Most AP buttons are "momentary". You push to "request" the mode from the autopilot and it will respond accordingly based on whatever the current mode is. Typically there would be indicator lights somewhere to tell you the "status" of the mode, i.e. OFF, ARMED, or ON. So, the button may animate when you push it, but usually will not stay depressed. The problem with having the button remain depressed is that it can be misleading as to the actual status of that particular AP mode. For example, if you push the NAV button and it remains depressed... is the mode now ARMED or ON? Unless you also have indicator lights or annunciators (preferably on the button itself), this can lead to confusion.

This same question was asked here just a few days ago .

Baz, Could you explain why you are using a hide/show when you could simply animate the button (in and out) in Blender?

If I'm not mistaken, I believe rose mode is the default at startup of the sim. If you want to set up your plane with custom/restricted modes you will need to use a plugin.

Due to the nature of the custom systems in the Saab, as well as the current sound engine, some sounds will not work in "replay" mode. The only workaround is to do your video recording during normal flight.

sim/cockpit2/autopilot/heading_mode is not a writeable DataRef. Therefore you cannot use a DataRef manipulator to change it's value. You will need to use a command manipulator with the appropriate command. This is typical of most AP functions.

There is no PANEL "light" on the overhead. I assume you mean the interior lights PANEL "dial"? This controls the backlighting of the panels (text labels, etc.). Those lights are AC powered and, therefore, the inverter must be on for them to work. Once the aircraft has DC power, place the MAIN INVERTER switch on the overhead panel to the "ON" position and the PANEL lights will work.

The release candidate went final. Release notes.

What are you referring to? This thread is rather old, and several issues were discussed. Some of those issues were resolved in previous updates.

SHJ, Are you having an issue with the animation in X-Plane, or with the Manipulator not setting the proper values? If it is the latter, are you using DataRef Editor to observe the daters values?

I'm quite familiar with the manipulators. I think what you are describing is actually a type of "button" manipulator. Please post a screenshot of your Planemaker screen showing the manipulator properties and the keyframes.

Never heard of a "wrap" type manipulator... please clarify ( should be toggle, drag_axis, etc.) Sounds like there is a plugin that is handling that functionality.

And how would someone "identify" the issue without having the scenery or a complete log.txt file? In addition, it would take time and effort to "identify" the issue. My point was that you are asking other people to take the time and effort to "identify" the issue on your behalf when you are unwilling to do what is necessary yourself. Does that really seem right to you?