JGregory

If you can recreate this consistently, lease send me the steps to do so and I will look into it.

The issue in the other thread was occurring on Windows AND Mac. Your problem sounds like something different, although I don't know what. No one has reported this problem, especially since the 1.5.1 update. If you can send me the .fms file(s) ( both the one created by the Corvalis and the one created by the FMC programmer) I will take a look at them.

I referred you to that link because it shows HOW the manipulator should be used, not just WHAT it is for. I wanted to make sure you were using the manipulator correctly prior to responding to any claims that it was not responding. And, since it is working properly for everyone else, my guess that your problem is an incorrect use of the manipulator would be logical. Please re-read the bottom of that post and report back that you are, in fact, using the manipulator correctly.

This has already been answered here. This is not a problem. Many people are flying the Saab without any issues. Check the manuals and performance charts for proper operation.

Fabio, There are many people using the autopilot in the Saab, so we know it works. It is certainly possible that some of your hardware is overriding/interfering with the autopilot. I would recommend disconnecting your hardware and removing other plugins as a test.

I sounds like you've answered your own question… "This is under Windows, under OSX the plane stays on course. But I must mention that the windows machine has more USB hardware, i.e. saitek panels and such, also more plugins are loaded." You may have an issue where your hardware is overriding or interfering with the autopilot Does the AFCS Status Box show "GPS" in green when this deviation occurs?

Are you ABSOLUTELY SURE the autopilot is engaged (AP appears in green on the EADI) ?

Huh? Switching aircraft will not make the Saab work better (or worse). And, the brake issue is fixed, look here.

We cannot provide a solution if we cannot reproduce the problem. This seems to be a VERY isolated issue and as of today we have been unable to duplicate it on our systems.

I have started this thread to provide a single source for the most current HotFix. This will reduce any confusion that may arise from having multiple threads with HotFixes in them. Any bug fixes/corrections/changes that are mentioned in other threads will have a link to this post where users can get the latest HotFix as they become available. OK, here's the MOST CURRENT hot fix…. Open X-Plane and the Saab In your menu bar at top, select Plugins > Gizmo64 > Windows > HotFix You will be asked to enter in your HotFix ID. Copy and paste in the following: f6a1e394d2e0e82b1aa8f6b1d122f97b Click 'Update' Once it has downloaded and installed, click 'Reboot' and you'll be done! I would recommend you reload the aircraft.NOTE: You will need to apply the HotFix to ALL variants of the Saab (Passenger/AEW/Cargo) The following issues are addressed with this HotFix: • Fixed bug in anti-skid system preventing user from applying brakes (2/13/14).

Philip, Thanks for reporting this… you have found a bug. I have corrected this. I am not sure when the update will be available.

Thanks for the clarification. Yes, you are correct, the EADI annunciator should change, but it isn't. This is a bug introduced in v1.1 and has now been corrected. I am not sure when we will be issuing the update for this. Thanks for reporting the issue.

Ummm… NO. The man OWNS a Piper Aerostar, that was why he suggested it. Why would he want us to do a Dash8-100 ?

When there is a valid signal, the EHSI will show NAV1 in Cyan and NAV2 in Green, otherwise they are displayed in Red. It has nothing to do with the NAV L or NAV R selector.

Please give us the specifics of the situation at the time this occurs…ie. your location (airport, etc.), the waypoint frequency you are navigating to, etc. Also, please provide you system specs. And, what is your frame rate?

There is a HotFix available that resolves an issue with the brakes/parking brake. You can get it here.

NOTE: A Hotfix has been issued for an issue with the brakes/parking brake. You can get it here.

You can get the HotFix here.

OK guys, here's the story. What you are seeing is a bug in the anti-skid system. I have fixed this. I will post a Hotfix here shortly… in the meantime you can workaround this by not using the anti-skid system (keep the toggle in the off position).

I will wait for your test results. Where are you reading this pressure?

http://www.x-aviation.com/catalog/gv_faq

Glad to hear you worked it out.

Wait…. you miss John's balls ?

Antonio, Did you resolve the problem, or is this still happening ?

Timing. At any point in time any one of us may make changes in our respective areas of development. As well, Cameron needs to code and prep the installer. The various stages of development determines when a bug fix/feature gets included in the next update. Yes, I'm sure, there will be further updates in the future (beyond the one you are already expecting). Any time we find a bug, or something that isn't correct, or even a new feature, we will make it available in the next update within the timing mentioned above. Updates will be ongoing in order to bring you the best possible product we can.