JGregory
-
Posts
2,256 -
Joined
-
Days Won
23
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by JGregory
-
I'm not sure about changing the ICAO and how that might affect DRM. I would make a backup copy of the .acf file before you make any changes. If you want to be sure, contact Cameron at X-Aviation.
-
If I recall correctly, you must assign the left condition lever to Prop1 and the right condition lever to Prop2.
-
We appreciate your input, but, the error that @Holvarn reported would not have happened if he didn't rotate the knob.
-
This issue has been reported in the past. After looking into it, the bug is "windows only" and I could not recreate it because I develop on a Mac. I have made some changes to the scripts that resolve this issue, which will be available in the next update.
-
Do the engine overheat lights come on just prior to this event?
-
The Saab uses a custom DataRef for the baro setting manipulator. There are no associated commands. This will be updated in v2.0.
-
Are you using VR? The Saab is not VR compliant. Not sure this is the problem but you should try running without VR and test. If all else fails, I would uninstall and re-install the Saab. It's possible some files were corrupted.
-
Glad you got it worked out.
-
The issue that you are reporting usually indicates that the scripts are not loading. There is nothing in the log files that indicate why. You do have several plugins and there may be a conflict. As a test I recommend that you remove all third-party plugins except Gizmo and try to load the Saab. Let us know your results. If you have any problems please post new GizmoLog and Log files from that session.
-
The Log.txt file you provided was a NOT from an X-Plane session where you loaded the Saab. Please submit a new report.
-
Please also attach your Log.txt file.
-
Strongly suggest you remove all plugins (except Gizmo) and test. JarDesign GroundHandling is one example of a possible conflict. Please remove all plugins and report back your results.
-
You only uploaded the GizmoLog.txt. Please also attach the Log.txt file.
-
Please adjust your graphics settings to turn on texture compression in X-Plane.
-
Please explain why you can't edit the DataRef. If you follow the instruction in the post by @HamSammich above, the G530 should function fine. Otherwise you will need to wait for the update, which is in Cameron's hands at this point.
-
Always post your Log.txt and GizmoLog.txt files when you have an issue.
-
glad you got it sorted out. FYI... the log files are the source of information that tells us what version of the aircraft is being loaded.
-
Please explain in more detail what you mean buy "failure to activate", and/or provide screenshots/video showing the problem. You do have a significant number of plugins installed, some of which are known to cause issues. As a test, you should remove all plugins (except Gizmo) and see if the problem persists.
-
You are attempting to load an old version of the Saab. Please upgrade to the latest, which is 1.5.
-
The prop sync switch in the Saab does not use a command for activation, it is a custom DataRef.
-
You should be able to find all Saab commands by loading the Saab in sim and goto Settings -> Keyboard, and then select a command from the list. The command string will be visible if you hover your mouse over the selection.
-
A screenshot and your Log files would be very helpful. This issue sounds more like a texture problem, which has been reported previously. Try turning ON texture compression in your X-Plane rendering settings and restart X-Plane. The keys on the pop-out have never been animated.
-
We wil be using the FMOD sound engine for v2.0, which will allow you to hear sounds in replay.
