Jump to content

JGregory

JGX-Designs
  • Content count

    1,846
  • Joined

  • Last visited

  • Days Won

    9

JGregory last won the day on August 30 2019

JGregory had the most liked content!

Community Reputation

218 Excellent

2 Followers

About JGregory

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

8,280 profile views
  1. It's a moot point with regard to 1.5.1. I guess we will find out if your expectations were right or wrong when the update gets released.
  2. We do not use the prop data out values as you think we do. I really don't have any more time to keep going back-and-forth about this... The question still remains... 1.If you disconnect your hardware, can you consistently reproduce the scenario where you get a failed auto-start? If not, then your assumptions are not correct and the problem is hardware related. and... 2. You should also consider that we are not getting any other complaints or bug reports about this and you are not the only user of the Saab that is using hardware to control the condition levers. Based on these two points the problem would be more than likely isolated to your system (hardware) and not a Saab related issue. But again, I think this is all a moot point as we will not be patching v1.51 anyway and the new update is not that far off.
  3. Huh? What constitutes the "end" of a failed start to you ? If the starter is still running then I would not consider it the "end" of a failed start. And... once the starter is running it will only stop running at a pre-determined N1 (or loss of elect power), not the position off the Condition Lever. Are you certain about that ? Have you observed the joystick Datarefs to see what happens to them when you disco your hardware? It's possible that the act of disconnecting itself introduces a temporary noise/spike.. who knows! I don't think you should assume it doesn't. It's not quite that simple. I used the term "noise" as one example of a potential problem. The bigger picture was that your hardware was not behaving in some manner and that was causing the engine start failure. We are simply taking the values from your hardware (assigned as Prop) as an input of the condition levers (position). If the failed start ONLY happens when you have hardware connected then that tells me the hardware is causing a problem. I have no way of knowing exactly what that problem is since I don't have your hardware. it's starting to feel like you may be over analyzing this. And, we are basically "beating a dead horse" here anyway. The next update is not that far off and all of the manipulator logic has been re-written, including the Power Levers and Condition Levers. So, even if we found an issue that is currently affecting v1.51 we would not be issuing a patch for it anyway.
  4. I'm fairly sure that our code does not take into consideration the user disconnecting their hardware in the middle of an engine start, so I'm not surprised by what you've found. Not sure an aircraft reload is necessary. Have you tried to power off the entire aircraft after a failed start?
  5. Anthony, It sounds like you've discovered the problem. At this point I think it's safe to say the aircraft is performing as expected. Your logic regarding the condition levers being tied into the battery temp logic is not correct. You can test this by using the GPU for your starts and continuing to use your hardware for the condition levers...this eliminates the battery temp restriction on multiple starts. My guess is that you will continue to have the same failed starts because, as you have discovered, the issue appears to be in your hardware (noise) mapped to the condition levers. Without reading the code, I believe that if our engine logic does not find the condition levers in the "START" detent then you may get failed starts (probably due to fuel starvation), especially if the CL is below the START detent. Cleaning the hardware may eliminate some of the noise. In addition, you may try re-calibrating the hardware in X-Plane.
  6. Right, "hardware", as in yokes, throttles, pedals, etc. You mentioned in one of your posts that you had the condition levers "mapped" to your throttle quadrant. As an example, the last log you sent shows you have something mapped to prop and mixture. You need to disconnect ALL your hardware to do a proper test. BTW.. when doing tests with plugins, it is not enough to just "disable" a plugin, you need to remove it from the plugins folder entirely. I see that you mentioned you had a test copy of XP where only Gizmo was installed... that's the correct way to test. Does that mean there were instances where the engine did start ??
  7. You system is running several plugins, has a fair amount of custom scenery with plugins, and you are using hardware. The easiest way to START diagnosing this is to either remove the plugins and hardware, or download the X-Plane demo, and then try the autostart. If that works then you will need to determine which plugin or hardware is conflicting.
  8. The OP stated he was having issues with Auto-Start. You are doing a manual start and did not even mention if you tried Auto-Start.
  9. JGregory

    saab gizmo not working

    Please be more specific. Was the Tool Tray Menu working previously? When you move the cursor to the upper right of your display, does the menu not appear? Is the Saab activated? We need more details. FYI... just "disabling" plugins does not guarantee no conflicts. If you suspect a plugin conflict you should temporarily remove all extra plugins and then load the Saab and test.
  10. JGregory

    Saab Climbout on Autopilot oscillates/porpoises

    Definitely not in this update. We will evaluate for v2.0 (need to see some real world examples to justify).
  11. JGregory

    CTD every time after loading

    The same thing happened with X-Enviro, only crashed with the Saab. At first they said it wasn't their problem but eventually they admitted it was and they fixed it. If the Saab was causing the crash then we should see something in the logs, but there is nothing there... only the reference to Traffic Global. Traffic Global is a relatively new product so it would not be surprising for it to have some "bugs". The Saab has been on the market for years without causing CTDs. Are you pushing the tiller wheel down ?? That activates the steering. You no longer need to assign the CL in that manner. Simply assign your hardware to Prop1 and Prop2.
  12. JGregory

    CTD every time after loading

    The last (4). four lines of the Log.txt file are... TGXP: Crash TGXP: Exception in thread 9520d: (null) TGXP: - Arg 1 : 0x0000000000000000 TGXP: - Arg 2 : 0xFFFFFFFFFFFFFFFF That is Traffic Global crashing the sim, not the Saab. Suggest you remove that plugin and/or contact the developer.
  13. JGregory

    CTD every time after loading

    Post your Log.txt and GizmoLog.txt files.
  14. JGregory

    Engine surging

    YES !!! YES!!! Very Soon™
×