Jump to content

JGregory

JGX-Designs
  • Content Count

    1,952
  • Joined

  • Last visited

  • Days Won

    9

JGregory last won the day on August 30 2019

JGregory had the most liked content!

Community Reputation

229 Excellent

3 Followers

About JGregory

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

8,622 profile views
  1. Not sure about the HP Reverb, but there are many people using the Saab in VR.
  2. Anthony, While I appreciate your attempt at diagnosing the problem, these facts still remain the same.... 1. The engine/prop code in the Saab is very complex. We override the throttles and the props. Therefore, observing the Dataref you mentioned above is not applicable and really does not provide any diagnostic value. 2. The next update (yes, I know it's taking longer than expected) has all new manipulators and logic for most of the systems. As previously stated, we are no longer "patching" 1.5.1. So, whatever answers/conclusions you've arrived at are not going to be addressed or applicable to the next update. Given these two facts alone, I suggest that you not put any further effort into diagnosing an old version that will not be patched and whose code is changing drastically in the next update. When the new update is released I hope you will try it out and let us know how it works for you. If you are still having problems we will be happy to work on diagnosing them against the new systems logic. FYI... none of our internal testing of the update is producing any kind of issues with the engines not starting, with or without hardware.
  3. Yes, that, and anything else that is "plugged-in" (USB, etc) would be considered "external" hardware.
  4. I think at this point you will just need to fly the passenger variant until the next update comes out. Even if we could verify your issues, we are not making any changes or updates to v1.5.1. We will test the cargo version for the next update to verify it is flying correctly.
  5. I would like to add... the next update of the Saab (before v2.0) will work in Vulkan/Metal. And that update will be free to all current customers.
  6. Some hardware requires a plugin to interface with X-Plane.
  7. Not sure why you would ask that, but hardware plugins certainly could be a problem.
  8. yes, hardware = joystick, rudder pedals, yoke, throttle quadrant, panels, etc... anything plugged in !
  9. Darran, You have several plugins installed, and you are using external hardware. My suspicion is that one of these is the problem. The correct way to diagnose this is to unplug ALL your hardware, remove ALL your plugins except Gizmo, PluginAdmin, and any whose name begins with XP. Then launch the sim and test. Another option would be to download the X-Plane demo, install the Saab, and test. If the problem is gone, you know it was either a plugin or hardware causing the issue. Place your plugins back in one at a time and test each time. If the problem returns you know which plugin is causing issues. Do the same with your hardware, plug each item in one at a time and test. Report your findings back here so we can determine your next step.
  10. No, there is not. The dome lights are true "spill" lights, there are no _LIT textures associated with them. Your apartment is not a simulation. Lighting (especially shadows in daytime) is particularly difficult to simulate. The "map" lights (overhead) should work. I will take a look at what we can do for the next update but this may need to wait until v2.0.
  11. We believe we have isolated the problem. The fix will be available in the next update. No, I cannot tell you when the release will be
  12. darran, The point is.. if you are going to report a possible bug in the X-Aviation/LES Saab 340A, please use in-cockpit pictures so we can verify what you are reporting. I am still waiting for your Log.txt and GizmoLog.txt files.
  13. The picture you posted above is NOT from our Saab 340A.
  14. Please post your Log.txt and GizmoLog.,txt files.
×
×
  • Create New...