JGregory

OK, starting to see a possible trend here.... 1.) This only happens with the right throttle lever. 2.) This problem is dependent on the position of the right condition lever... all is OK if right CL is below MIN? Everyone please confirm. Note: You should be able to test this without starting the engines.

I would also like to see screenshots of your frame rates when this issue occurs.

Note: For anyone reporting in this thread about a problem with the Throttles... please post as much info as you can about your system, ie. Windows/Mac, OS version, XP version, etc.

No.

My belief is that because of the custom handling of the throttles in the Saab, the problem is "revealed". It doesn't mean that the issue doesn't exist with other aircraft. It also doesn't mean that the Saab code is wrong. ie. In the 172 there is no reverse and therefore there still may be an issue but it just doesn't have the same effect as in the Saab. Interested?... not sure that would be the right description. Of course we want all our customers to be happy, but an issue being reported by 2 or 3 people out of thousands is not a significant priority. This just further strengthens my statement that the issue is not in the Saab code. Perhaps something changed in 10.42, but I am not seeing it with the hardware I have. In addition, from what I can tell by your reports this is not something that you can consistently and repeatedly reproduce with the exact same results. And now we have a report of it happening in 10.42 but not 10.36. It is extremely difficult to diagnose something without a set of a parameters that can reproduce the problem. I am not abandoning this, I just cannot test hardware when the Saab code is, and has been, functioning as it should. I also do not have every piece of hardware available on the market to try out. I would certainly be interested in hearing from all users who utilize hardware for throttles. Tell us what version of XP you are using and if you have issues or not.

Martin, I do not have the time to test various hardware configurations. Maybe another user can help you with specific hardware questions/issues. At this point I think it is clear that these problems are not directly related to the Saab.

If you are talking about the "CH Products throttle quadrant" check box in the Equipment Tab, then yes.

That is correct behavior. Yes, GS will only engage when approached from below. Yes, there are. And you should always use the custom commands for the aircraft if available.

Martin, This pretty much confirms that this is not a code issue, but rather a hardware issue. The code behaves the same every time, especially as there are no other conditions affecting the operation. However, it is possible that the hardware could be hypersensitive, or can produce noise and/or cross-talk, which can vary each time it is used. The condition levers have absolutely no interaction with the throttles at all, so they cannot be at all related to the problem as far as the code is concerned. However, if you have your hardware connected to the condition levers, there may be cross-talk or noise affecting the throttles on the same quadrant. I tested this on a CH Products throttle quadrant and a Saitek X52 and could not reproduce this issue. The DataRef I asked you to monitor is simply an input to the Saab in X-Plane. This Dataref is used by hardware, manipulators, and keyboard comands, and all the tests I have run with these inputs show them to be working fine. The DataRef will be set to whatever value your hardware sends to it. If the hardware sends erratic values, it can do so VERY quickly (much faster than the code could pick it up), thereby causing the throttles to misbehave. Therefore, you get an out-of-sync condition where you may see the proper values in your calibration screen but, until you move the throttles again, they will not sync. It may not be noticeable in other aircraft as they may not use the input values the same way we do in the Saab. I am open to any other suggestions, but based on other hardware working (as noted above), the manipulators working, and the keyboard input working, this is most definitely not a code issue.

The throttles should be set to "ground idle" during startup, not after. Just to be clear.... when you say "one or both", is it different every time you start the Saab? Is there ever an instance where it does not happen at all? Also, to be clear... they are always moving to max reverse thrust when this happens, correct? I assume you mean they are properly calibrated using the "Calibrate joystick Hardware " button in the "Joystick & Equipment" window? Again, to be clear, if you move the throttles when the engine are NOT running, they behave as they should, correct? This is very strange as the code that handles the throttles does not take into account whether the engines are running or not, so it shouldn't matter. As no one else has reported this I'm inclined to believe it is unique to your hardware. Perhaps there is another Saab user with GoFlight hardware who can help out. If you want to, you can use DataRef Editor to monitor this DataRef... "sim/cockpit2/engine/actuators/throttle_ratio", to see what values are being sent from your hardware to the throttles. The code simply uses that value, so if it's no good at that point you have a hardware issue.

That is INCORRECT! Years ago there was an issue with sound, which has been resolved for a long time. I would be interested to know how you concluded that Gizmo is causing a conflict with World Traffic.

Flo, Here is a response from one of our Saab pilots... (sorry for the delay) So descent in a Saab. Speed is planned at Vmo - 10 kts (240 usually). The v/s to use is 1500fpm. Calculate TOD using 3nm for every 1000 feet you need to lose. For example if I need to be at 2000ft AGL above the airfield on arrival, and I am at 20 000ft AGL, then I need to lose 18 000ft. So I will need to start my TOD at 54NM (3 x 18) from the airport. As far as wind goes, add 1nm for every 10kts of tailwind and subtract 1nm for every 10kts of headwind. The trick with this is to keep doing the calculations to see if you are high or low. So in the above example I know that passing 12 000ft I need to be 30nm from the field. So I can adjust my V/S to make sure I pass through that gate correctly. And of course if ATC gives a speed limit, then I may need to back off the V/S a bit so I can still meet my height and speed goals. Eg say in the above example I want to be at the aerodrome at180kts at 2000ft joining crosswind. So I obviously cannot keep at 1500v/s and 240kts till 3nm from the field. So I will need to start slowing down in enough time that I can meet those goals. The SAAB will happily descend at 1500ft at 240kts with minimal power set, so there has to be some planning in advance to start reducing the V/S and the speed to meet the speed requirements at the aerodrome.

I don't think the .obj file formats is blocked from uploads. Maybe Cameran can explain further. You could zip the file and post that.

Please attach the appropriate .obj file.

And that may be your issue. I believe they have fixed this. You should contact them directly.

Did you recently update X-Plane? What version are you using?

Thanks for sending me the logs in a PM. Please see this previous forum post for an answer to your problem.

We need the ENTIRE Gizmo Log as well as X-Plane's Log.txt file.

Check the lighting settings on your attached objects in Planemaker.

We did use something similar when we developed the electrical system for the Saab. However, the Citation is being developed with an entirely new software framework and the systems will be even more deeply simulated than the Saab.

Yes, it is used to monitor all the pressure, temperature, and air flow values under various conditions while developing the bleed air system. This will not be part of the aircraft as delivered to customers. We just wanted to let you know what we were working and the depth of the simulation that we are creating.

Did you check this out... Citation Bleed Air System

That depends on whether you are creating an omni-directional light or a "cone" shaped light.

I wasn't clear about what you were referring to with the drag_axis_pix. Taking a quick glance at your pics above, I think you missing a parameter for the light. I believe there should be 9.

You should not use a drag axis pix with a toggle switch.