Scotfleiger Posted March 14, 2022 Report Share Posted March 14, 2022 Hi John The MyOffsets.txt means of the user defining SimVars is a great step forward. It has the disadvantage of requiring developers to define and distribute a copy of this file which may overwrite user's own files and would require a different file for each aircraft. Would it be possible to define such offsets using LUA? For example, ipc.defineOffset(0x66c0,1,CIRCUIT SWITCH ON:18,I32,Bool). Link to comment Share on other sites More sharing options...
John Dowson Posted March 15, 2022 Report Share Posted March 15, 2022 Hi Andrew, 13 hours ago, Scotfleiger said: Would it be possible to define such offsets using LUA? For example, ipc.defineOffset(0x66c0,1,CIRCUIT SWITCH ON:18,I32,Bool). No, I'm afraid not. Allowing additional simvars to be added once the simconnect connection has been opened and simvars already requested poses many issues that I am not willing to look into at the moment. It will have to be up to the user and the software developers to handle this correctly. I could allocate a specific offset area (i.e. not in the 'free for general use' offsets) for use by LINDA to prevent the same offsets being used by other utilities, if that helps. If you let me know the size required, I can take a look and see if I can find an area to allocate for this. Cheers, John Link to comment Share on other sites More sharing options...
Scotfleiger Posted March 15, 2022 Author Report Share Posted March 15, 2022 Thanks for the quick response. I fully understand your reasoning. I will hold off in requesting any reserved offsets at the moment. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now