Ben Russell

Probably Jar Ground Handling or XSB

First I've heard of this..

Hmmm. Odd but a good lead. Thanks

Pretty sure this is an ancient bug that only affects the log file messages.

What version of xp? I added code to use the full cmd name if the description is blank.... I wonder if a new version of XP with tool tips is being too smart by half and blanking it out of the description is the same as the full cmd name..

Log.txt contains this line: G64: 0.000: Gizmo64 Script Engine v18.02.27.0200 Windows This confirms that the most recent available version of Gizmo is installed and running. Install the Saab to "break" your install, run X-Plane. Upload your Log.txt and GizmoLog.txt files and, if you like, check the Log.txt file for that line to confirm that the Gizmo version is correct.

Post your Log.txt and GizmoLog.txt files from BOTH a working install and a failing install. This will let us see version numbers for the plugins that are being loaded and also any potential systems scripts errors that are being logged. Anything else is just guessing in the dark.

If you turn the GC off trash will accumulate until the Lua memory pool is exhausted and the plugin crashes. You cannot disable it as it wouldn't achieve anything useful if you could. If your frrame rates are "a lot higher than usual" while using this product I'm not sure why you believe this is an issue.

the only people wanting to run xp10 have weak hardware that wont support xp11 well. this same weak hardware wont support hi def scenery either so there’s basicaly no reason to bother. xp10 is dead. save your pennies and move on.

A good suggestion for the future...

Trigger threshold is "pause" and cleaner strength is "step multiplier" when referenced against this page from the Lua manual; https://www.lua.org/manual/5.1/manual.html#2.10 Some safety limits have been imposed so that Gizmo can't be configured to use endless amounts of RAM as it would eventually crash X-Plane. (There is a 1 or 2 gig pool shared among all Lua plugins...) Nice to hear that the new options are helping people. I will probably adjust the default values to suit the common preference for more ram usage with a large spike less often. (300 / 200, or so...)

If you ever figure out which plugin is conflicting please let us know. Alternatively, upload a Log.txt file with all your plugins installed and we can figure out a general idea of which ones it might be.

did you update gizmo to 18.02.27.0200? post log files.

18.02.27.0200 is the most recent version and should be suitable for release with a Saab update. gizmo is the center piece of multiple aircraft and our drm/activation system. it runs global for good reason despite what various haters on another forum will try and tell you. (those that can, do. those that can’t bitch on the internet instead of putting in the hours to change reality *coughkerbaughcough*)

Bruce. Try this;

Thanks Bruce. Log files have the data I need. Will re-work the code in question again...... Frustrating but such is life. Cheers, br.

it might also come down to whether the primary display is on the left or right..

Aha! I think I just found the clue I needed. Many thanks.....

For the sake of clarity, it's not how Gizmo manages the GC. It's how the IXEG systems scripts choose to use memory and/or CPU resources. For example, this has no such effect on the Saab systems. Cheers...

in this instance it’s probably gizmo. personal circumstance for the last few months has been tired and stressed. we have a multitude of weird bugs going on. under these circumstances its probably my work at fault. sim crashes are just yet another way the problems can manifest...

Multi quote to trigger notifications... Please try the following plugin and post log files;

It's been reported and it's being worked on. Thanks for reporting it anyway.

Not much point packaging the Saab update up with a buggy copy of Gizmo is there? Notice all the IXEG bug threads right now from the update we just published? The same plugin powers both aircraft. Systems scripts run on top. We could publish the Saab tomorrow, but it'd just create more headaches for everyone. Your patience would be appreciated.

"Same for me", exactly the same, down to exact error message and exact aircraft selections? Or just "vaguely the same, i saw some red text" ..... Every detail matters. No matter how tedious it seems to report it. Esepecially prior aircraft selection in this particular instance. Thanks.