Ben Russell

https://support.discordapp.com/hc/en-us/articles/208866998-Invites-101

Ran for 1.5 hours with no issue under the latest build of Gizmo. Might be a bug with the older versions, might be nothing.

I've just setup my local machine with 19 AI aircraft using X-Planes built in system. I'll let the sim run and see if anything happens. There's no reason why it should. Gizmo doesn't interact with the AI aircraft in any way "out of the box" but it's an easy test to run.

Post your entire log.txt and gizmolog.txt files.

You probably installed a plugin that broke something. There's a few in the log.txt that I haven't seen before.

Move X-Plane out of the "Program Files (x86)" folder. (Desktop or User folder or some other disk..) Windows is protecting the contents of the program files folder which messes with plugins writing files to it cleanly.

Given your stated computing experience, please consider the following: X-Plane plugins all share the same memory address space. There is no modern memory protection applied to them. Any single plugin can override or clash with any other plugin, similar to the joy that was Windows 3.x or Mac OS Classic. Because of this, failures often are only present when under "resource pressure" and it may be that a relatively rare plugin or bug causes something else to crash, as it was back in the 90s too. Your last post above containing Memory Allocation Error messages is specific to the Lua JIT ram pool that X-Plane allocates. The Saab typically uses 10-20 megabytes of this depending on how you have the Garbage Collector tuned via Gizmo. The total pool available should be* somewhere around 1.6 gigabytes. Both Skymaxx and the Lua memory pool usage have been stable issues for many years prior to these recent events. You can find more information regarding the Lua JIT memory pool here: http://hacksoflife.blogspot.com/2012/12/integrating-luajit-with-x-plane-64-bit.html You can see some usage information if you open up the Lua Garabge Collector prefs window in Gizmo itself. You will be able to see the current Gizmo Lua VM usage as well as total X-Plane Lua pool usage. If one of these has a leak you should be able to detect it here. If neither is leaking then some other plugin is likely abusing the address space. There's a button available in the RH toolbar or you can look for it via the Plugins > Gizmo > Windows entry. ( I cannot remember the exact name it's listed under as I've been reworking these accesories for the new XP11 GUI style and Gizmo update to come..) I hope to get an update to Gizmo out in the first quarter of this year that will add additional debug data to the Logs if and when Lua Memory Allocation error occurs. It's been nearly 2 years since a public update to Gizmo so there's also the potential that the code maintenance over that time may resolve this mystery issue.

I've added some code to gizmo to report more info about memory usage when it encounters this sort of error. Hopefully be able to release a new beta update soon. This is a relatively new bug and I'm not sure what the cause is yet.

Also, Log files, or it never happened. Upload the complete file, not the part that you think is important.

You're using the 32bit version of X-Plane. You need to be using the 64 bit version.

This forum is not associated with the X-Pilot multiplayer plugin in any way. This forum existed 10 years before their poorly named project.

I'd start with WebFMC. From the looks of this it's not following the thread-safe guidelines for the X-Plane SDK. Notice how the WebFMC entries are interrupting the other plugins log entries? That should NOT be happening. Ever.

Are you using multiple monitors?

Delete this: Loaded: D:\SteamLibrary/steamapps/common/X-Plane 11/Resources/plugins/projectFLY/64/win.xpl (projectfly.bridge).

I like Linux but I can't justify the time investment to make and support products for it.

http://dashboard.x-plane.com/ 1.14% of the market at time of writing.

Basically, the XP11 brought multi-window support with it and changed the way that window-coords are shared with plugins. Gizmo and the Saab were written pre XP11 so they do not account fully for these new coords. As you've discovered, the monitor that X-Plane resides on matters, it's not so much the physical location of the monitor as it is the logical-id of the monitor. Eg: Your 16:19 screen is probably logical ID 1 and 21:9 might be 2 or 3. The fact that screen-1 is in the center doesn't matter. X-Plane will feed us useful position data. When on screen-2 (far left, 21:9) the position data is somewhere in the negative values and thus the tool-tray mouse detect code doesn't fire correctly. Better multi-monitor support has been on my list for a long time now but life has a habit of getting in the way. There is currently a dev-beta of Gizmo64 v20.x being tested privately which has support for the new XP11 pop out windows and so on so support is coming for all the multi-screen goodies but it takes time. For now, the best you can do is continue to move the sim window around. Sorry I can't give you a better solution.

Are you running single or multi monitor?

Your Log.txt indicates that your X-Plane machine is crashing because of OpenGL driver errors. FBO cloud_shadow ID: 0 is not a real FBO object. Failed with: GL_POINTS 0:01:20.992 I/WIN: Opened window menu bar 0:02:05.761 E/SYS: +------------------------------------------------------------------------------- 0:02:05.761 E/SYS: | There was a problem setting up OpenGL. 0:02:05.761 E/SYS: | 0:02:05.761 E/SYS: | (Please send your log.txt file to X-Plane technical support at info@x-plane.com for debugging purposes.) 0:02:05.761 E/SYS: | 0:02:05.761 E/SYS: | (OGL_extensions.cpp:1229) 0:02:05.761 E/SYS: +------------------------------------------------------------------------------- --=={This application has crashed!}==-- Please update your Graphics Drivers and see if that helps.

This typically happens when you have a plugin installed that you really should not. I suggest you do an audit of what you have installed on that machine.

Posting for the sake of clarity, not trying to be rude here... This forum is not officially affiliated with the (very poorly named, this forum predates it by about a decade) X-Pilot multiplayer plugin. There may be a better place to post your query where you will recieve better support. I do not know where that may be.

Delete the file "X-Plane / Output / preferences / gizmo_prefs.txt" to ensure that you haven't disabled the tooltray using the Gizmo GUI.

Per the Log file attached. "2:00:31.976 E/SYS: | Please report this to Laminar Research." https://dev.x-plane.com/support/bugreport.html