Ben Russell

Yes. It should be.

thanks for taking the time to report back that this is fixed.

You paid for what's detailed on the store page. There are no official dates of release specified for the pending update. There is no official news letter sent providing a URL that doesn't work. Seems you're confused about your own experience. This doesn't change the fact that there's still an update in the pipeline that will be released, when it's ready. Not when you ask for it, when. it's. ready. At the moment, that situations blocked because of some nasty bugs with the plugins that power it. Bugs that I've been fixing tonight. Doesn't mean the update will be ready tomorrow though. You've become frustrated with your own impatience. There was never a date given. Only Gorans best intention and happiness that he'd completed his part of a multi step, multi party process, but you've made it extensively clear that you don't care about the details, only your own gratification.

15 hours. Not sure what you were hoping to achieve here.

Had you bothered to read and understand the contents of this thread in full this conversation wouldn't be happening. As you don't give a shit about what I have to share, I'll return the favour and move right along leaving you with nothing but what you brought to the thread. Snark and attitude. Good day.

"the fps spikes are too big!" "the fps is too low!" I'll be providing an control panel to choose between "higher fps big spikes" OR "lower fps spikes but more consistent FPS" with a simple check box. There's no free lunch here. The drop is the result of both more detailed graphics AND Gizmo being tuned for more consistent fps with less spiking.

There is no terrain texture. You have to build it using the SDK probes function. These requests are getting ridiculous. Gizmo is a commercial product composed of hard won knowledge. I’m a little tired of you asking for cherry picked answers for short cuts to take for your own means. Either use it or earn your own battle scars.

Yes. It is. You'll also note that we just pushed an update for the IXEG 737 which contains bugs that are caused by Gizmo. This means that the Saab update is now blocked by me because the Saab runs on top of Gizmo and I'm the sole author for that product. And guess what, in the last few months life hasn't exactly been smooth sailing. I'm currently seeking a new house and doing my best to work out of a garage while staying with family. This means that any future updates will be ready "when they're done" and not a moment before.

The issue is a classic "ram buffer" C programming bug. It may help to reduce the plugins you have loaded or simply reboot. Expect it to show up randomly. This is why it's not been a problem until now. The plugin revision has been in active use by a fair number of users for about 37 days and there have been zero reports of the problem until today when it's gone "into the wild" with all the config flavours that come with that.

No. Sorry. The plugin version is checked to ensure that a minimum version is in use. You can use the product with newer plugins but not older.

No. Different bug. The marker.1 bug dies with Gizmo 18+ but it seems I swapped it for another less predictable item. Oh well. Such is dev life.

Bug confirmed. Cause is a change I made to Gizmo late last year on 13th December 2017. Strange that it hasn't been reported by anyone else until now. Fix will require a Gizmo update which is a bit tricky at the moment due to personal circumstance.

fps has been tuned for consistent rate rather than peak rates. peak rates were higher in older versions but it came at the cost of larger more noticeable spikes. when both plugins were tuned for consistent rates the new plugin ran better in the lab.

Seems pretty clear that, A: This is caused by the Ground Handling bug spewing data into Log.txt B: You're the only person to have ever reported it that I'm aware of. It could be a combo of ground handling + custom scenery or choice of locale, or any number of things. What it definitely is not at the moment is a big deal spread across a large number of users. There have been problems in the past with the Ground Handling Demo on Windows but as far as I know these were corrected by using an up-to-date or full version of the GH plugin from JAR. Sorry to say but there's not much to be done here except wait and see if it does explode. If it's a serious bug it will self replicate and become a big deal. If it's a random bug or clash resulting from your sim config, scenery and flight locations then you'll be the only one who can replicate or produce it. I suggest installing a fresh copy of X-Plane using the demo installer (not copy and paste using Finder) and only installing GH and the IXEG inside it and see if your choice of flight locations are still consistently able to produce the problem. This will bring us some useful stats by elminating any chance of external influence by either plugin clash or weird scenery glitches. This additional copy of the sim will not affect your licensing in any negative way. The machine ID is generated by OS details. You can have as many copies of the sim installed as you need.

What folder do you have X-Plane installed in? Gizmo is failing to save a file. I suspect X-P is probably a Steam copy buried under "Program Files" and thus we're getting blocked from a save by Windows or it's permissions settings... If you know how, try taking ownership of the X-P/X-Aviation/ folder and ensuring it has write permissions for the windows-user that you normally use while flying X-P.

You'll have to wait for Cameron to merge your account purchases. Thanks.. br.

3 projectors but how many GPU's / machines? are you using one single stretched x-plane window or three entirely seperate displays with their own angle offsets and so on.....?

All software has bugs. Most AAA games for Consoles never reach a remotely bug free state. Some games with multi million dollar budgets are riddled with issues. In other news, water is wet.

For what it's worth I personally _hate_ that this "Defender exclusion" is the solution we have to recommend. The main reasons we recommend this are; 1. The FMC code is still a work in progress. Tom is mostly responsible for this part of the project. It's a complicated beast and subject to major reworks as he learns more and fixes bugs. I could get in there and optimize all this away, breaking the code down from something an engineer has created to be "as correct as possible" into something that would run "as fast as possible". This might take me a few days or weeks depending on how long it takes me to understand the system and then re-verify that it works correctly through either automated tests or team playtesting. Then Tom might decide that the FMC code is all wrong and throw it away so that he can add more features or correct some critical flaw. ('cause lets be honest, the FMC has had more than its fair share of "Gizmo Errors" over the last year or so...) The end result is that we'd be back to another "engineers version" that's correct but probably slow again. Teaching Tom the depth of knowledge required to understand the requirements of a fast gaming loop and how to shard the work is also not really an option for either of us at this time. We have other commitments meaning that our time is genuinely better spent elsewhere. So, for now, I have to sit back and let him focus on the "as correct as possible" unti the point that the IXEG team decides that it's functionally complete. If they were to make this call tomorrow I would look at optimization immediately as this issue stinks from both a user experience perspective and a system security(placing an exclusion on the X-Plane folder means other plugins for other products will be ignored by Defender*) perspective. 2. Lua JIT. We use Lua JIT to run our systems code as fast as possible. The JIT engine marks a large block of RAM as write+exec.... it _must_ do this to be able to do it's job, that of translating Script into Machine Code on the fly. We could move to straight Lua and this issue would go away but frame rates would likely plummet. Something no one wants. Sometime in the future this will no longer be an issue. Thanks for using our products.

In the X-Plane folder you will find a file called Log.txt Please attach it to a forum post so that we can confirm which version of Gizmo you're using. Thanks.

Actually, from my side of the fence, it feels like the large number of developers with enough passion to work a second job and still publish products are keeping the industry alive, but what would I know... right?

The IXEG team uses Gizmo as the engine underneath their systems. There are some things they're dependent on me to add support for. At this time it is simply not possible to create a pop-out window of any kind using Gizmo. As this year (2018) progresses we will probably see support for this added. After Gizmo has the ability to create pop-able windows it will be upto IXEG to modify their scripts to utilize the new functionality. As for the cockpit builder market, you're in an incredibly small niche within a niche. Time and resources must be dedicated to the largest possible audience to generate a viable and sustainable return. Add the growing VR market into the mix and things get even more "fun".