Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.
Comments
Hi Steve,
The logic is fine, like you said it does work. Internally and probably not perceptiable by anyone is that it would run slower because you are causing a variable value to be fetched twice (two If statements). A Goto is simple and very fast. An If statement is slower because it has to determine a variables position in memory (a list), retrieve the value and then check the logic of the If statement.
In reality no-one would notice the difference unless it was called continuously.
Best wishes
Steve
Hi Steve,
The Rotate code is the same code in all GIT versions. I'm guessing that FSX/Prepar3D see repeated commands and go into some sort of acceleration mode.
What I can do is tweak the code for X-Plane so instead of it being a linear mapping (e.g speed = 2, so send 2 commands), I cold do an exponential map onto the speed so say 2 would send 3 commands, 3 would send 9 commands etc. Its easy enough to do so I'll add it to the dev plan and try and get it out ASAP.
Best wishes
Steve
I have got the rotary acceleration working a treat. I also have the display blanking working and the separate file for BespokeEvents.xml and BespokeVariables.xml.
I just want to do an EFIS default config and then I'll release it, probably late tomorrow.
Best wishes
Steve
Version 1.3 is now available in your account to download.
Best wishes
Steve
Commands are processed within X-Plane so they always have up-to-date DataRefs to run against. Bespoke Events run outside of X-Plane and access DataRefs via a shared memory area between GIT and the GIT plugin.
So when a task sends an update to a DataRef, the command is processed by the plugin and then the shared memory area is updated. This happens extremely fast but there is a delay non the less.
The Rotate function is also operating extremely fast so many of the task updates on a DataRef are actually just setting the DataRef to the same value because the shared memory area has not yet been updated.
The trick is to add a Sleep task before or after the Set task to give the GIT Plugin chance to update shared memory. You want the Sleep task to use a very small number (its in milliseconds), so try a few values until it works better.
PS: This thread now bears no resemblance to the title. Can you open up new threads please unless its about crashes, otherwise all the useful stuff being talked about will be missed by others.
Best wishes
Steve
The logic applies to every rotary so long at the Event Action is ROTATE.
Best wishes
Steve