Litjan

Ah, ok...yeah, that would be interesting to know if it changes this. I saw your thread in the scenery forum...we are pretty busy with getting 1.32 out of the door, but once that is done - if we don´t have a solution by then - I will get that scenery and try here. Cheers, Jan

Uncheck the "Use Vulkan" in the graphics tab

Did you try in OpenGl as well?

Hi Alex, this does "sound" weird! It seems that your computer does not stop to play a (some) sounds, I have never heard of that before. However - I would still ask you to apply the "standard troubleshooting protocol" found here: ...especially the part about (temporarily) removing all other plugins. Since your bug is so reproducible, this should give you quick results and I would like to hear what you find out. Cheers, Jan

I think we did have some complaints of incompatibilities... are you running the very latest version of SkyMaxxpro? I think 4.9.5 just got released a short while ago. I also could not spot any trace of SkyMaxxPro in your log.txt that you posted initially, so I could not ascertain the version number you are running. Cheers, Jan

Thinking about this...lets also see if we get another report on this - or I will go and buy that scenery to try myself!

Also try "rebooting gizmo" when you are on the runway in "ready to fly" and have the pulsing effect... There is also an option to "reset aircraft on relocation" in the preferences menu. Maybe see if that has any influence...you never know... Cheers, Jan

Sounds like a sound . Ok, curious what you will find out!

Working down the list, eh? Good job! One could almost think you had a job once where thoroughness and methodical work was a prerequisite . Cheers, Jan

Yes, I would agree with Ben - it seems to be something in our code. Maybe it is the sound (as you have to be close to the aircraft)...if the number of objects displayed affects it, there is obviously some computational problem were a resource (processing power, memory, etc.) gets maxxed out. Can you try with the aircraft truly "cold and dark" (no sounds generated)? This is still puzzling, because I would assume that this would also rear its head at other airports since you have a lot of custom ones... Cheers, Jan

You could try to switch the Gizmo versions - you are running the old (stable): G64: 0.000: Gizmo64 Script Engine v18.02.27.0200 Windows but you should really try the new beta (you should have gotten an email a week ago or so).

Hi Ian, does the EGNS airport create a plugin in your plugins directory? Can you post a log.txt file, please? Have you tried running the IXEG at EGNS with all other plugins removed? Cheers, Jan

Hi Scott, no problem, we will see if we can get this fixed. If your other aircraft are running fine - then this is already a good indication that its not some genuine background system problem. The "old stable" gizmo did have a certain "heartbeat" like slowdown in framerate at a periodic timing, it could be influenced somewhat with the lua garbage collector settings...but even that old version never really dropped framerate into the single digits. The newer beta version has been running really good for almost everyone, but again, everyones mileage may vary. Let me know what you find out after following the troubleshooting steps (plugins, running at TXKF or some other remote airport) and then we will go from there :-) Cheers, Jan

Thanks for the log! First off one can say that your CPU is not the beefiest one - so I would not expect stellar performance in X-Plane to begin with - I like to run my performance tests at TXKF (Bermuda islands) as there is little in terms of scenery to tax my system. For the intermittent FPS drops I would recommend (just to troubleshoot) to remove (physically, not only disable in plugin manager) all other plugins, especially librain, webfmc, xPilot, TerrainRadar and fly with lua. Let us know how that works out? Cheers, Jan Edit: It could also be that some other background process interferes with running X-Plane resource-wise. Make sure that you are not running something else on your computer that could need heavy processing power?

Hi Scott, sorry that you are disappointed. I am not aware that "some people have the same issues", I hope they can come forward as this be something endemic than that we can attempt to fix. So far you are the only one to experience those kind of performance drops. Depending on your sytems it is perfectly normal for Gizmo to "cost" you a bit of performance. We are doing calculations to simulate the 737´s systems and interface that with X-Plane, you certainly don´t assume that those calculations are not putting a load on your hardware? Ben is right, we need to see your log.txt to take a guess. In the meantime, this applies (as I am certain that you have a conflicting plugin causing you this) Cheers, Jan

Interesting...there may be something amiss here. When I watch a landing in replay my speedbrakes always pop to "full up" when I end the replay...no matter what I did during the flight (I make sure I really really retract them before starting the replay)...Tom has added some code to make the spoilers move smoothly during replay, I wonder if this could interfere with the operation. To be safe - I would always recommend rebooting gizmo between consecutive flights - even though our goal is, of course, to allow consecutive flights. Cheers, Jan

Hi JP, I think this here is the core of your problem: 0:00:00.028 G64: Gizmo64 beta expires in 0 days. 0:00:00.028 G64: This beta release of Gizmo64 has expired. Failed: E:\X-Plane 11/Resources/plugins/Gizmo64.plugin/win_x64/Gizmo64.plugin.xpl. (The plugin refused to start by returning 0 from XPluginStart.) You need to updated your Gizmo version - you should have gotten an email a few days ago with a link to update your Gizmo Beta version. Also make sure that your IXEG 737 is at version 1.31 - but I assume it already is and that really the expired Gizmo is your main problem. Let me know how that goes, Jan

Well, you can always try the latest Gizmo beta (in fact I recommend to try it, it is much more smooth in performance) - but I doubt it will influence this lighting problem. Instead of fully re-installing X-Plane you can also delete the content of the "Output/preferences" folder...X-Plane will then make new preferences with the default values. https://developer.x-plane.com/2016/11/you-dont-need-to-reinstall-x-plane-to-fix-it/ It is very likely that one of your shader plugins (Xvisibility or true shade) messed with those settings - and they will not be reset automatically. I wholeheartedly advise against using any third-party plugins that changes the "looks" of X-Plane, but I know that they are very popular because people can´t stand X-Plane´s realism in making the world look like it is most of the time...dull and hazy ;-) Cheers, Jan

Hi Russ, glad you got it working - and once you figure out which plugin causes the problem...please let us know! This might help other users with the same problem, sometimes there is even an update available for that plugin or something else can be done to remedy the problem. Happy landings, Jan

Hehe, we are all pilots here! If you can fly the IXEG 737 you are more of a pilot than most real A320 drivers

Let me know how that works out for you!

Hi Dozo, Why don´t you assign the TQ axis to "yaw" instead of "nosewheel tiller"? Cheers, Jan

Hi axmiha, I didn´t spot anything dubious in your Log.txt...but I would still recommend to "remove" your plugins to a safe folder, just for a testing run - both for the weird lighting and also the sound bug. I haven´t heard anything like that sound effect you describe, but to rule out any interference with other plugins it would be interesting to see if these issues persist if you temporarily move them out of your plugins folder? Cheers, Jan

The officially required ones, plus whatever the passengers and crew brings for their reading pleasure... Jan

Hmm, no, this is actually the first time I hear this... normally people with that problem have installed a mod or hack at some time that makes the streetlights more bright or so - often then forgetting they ever did that. So far your case is the first of the lighting level being messed up without the user changing art controls beforehand... Often users are reluctant to post Log.txt files because they suspect that it really is some plugin they have installed but can´t live without, so they don´t want it to be true Jan