August 31, 201114 yr Commercial Member Hi, I just had a support request from an FSUIPC user which includes this text: I understand 66C0 is marked as free for general use and till now have not found it a problem using this offset. I recently began using LINDA to assign my hardware switches to controls and have found that LINDA also uses the same 66C0 (64 bytes) offset as a communication pipe for GUI and LUA. It is a shame that the offsets reserved for private user application are being hijacked for a program which is becoming more and more popular. This is going to cause much more support work and folks requesting dedicated offsets for one-off private applications. I won't be able to accede to all of these. Please reconsider the use of these offsets and request a proper dedicated allocation for LINDA. It will be easy for me to oblige (write to me at [email protected] saying how much you need), and will solve a lot of future hassle. Thanks & RegardsPete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
September 2, 201114 yr Commercial Member Don't be so sensitive. :-)Pete has implemented couple of features in FSUIPC by our request. Artem Crum, EASA PPL•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••LINDA → Lua Integrated Non-complex Device Assigning•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
February 5, 201214 yr Hi Artem,Hopefully I can revive this old thread because I have found a similar problem with another offset made available by Pete Dowson for private user application. It concerns offset 66C1. I wanted to use it as a switch in a simple Lua script of my own by toggling its value between 0 and 1 through FSUIPC. This works fine as long as I do not have your plug-in Linda.lua in my FSX Modules folder. But when Linda.lua is in my FSX Modules folder (it gets loaded when FSX starts), the toggling does not work : 66C1 remains =0 as shown in the FSX title bar using FSUIPC's logging functionality. Therefore it looks to me like Linda.lua does use offset 66C1 for something or other.Offset 66C0 works fine for me even with Linda.lua present in the FSX Modules folder, and so do the other ones I checked i.e. 66C2 to 66CF. It's just 66C1. You may want to look into this. For the meantime I will just not use 66C1. Thanks for your time ! Cheers, Emile Bax.
February 27, 201214 yr Commercial Member Emile, are you sure you're using the latest version of LINDA? Search through the files shows, that LINDA do not use 66C1 offset in any way. Artem Crum, EASA PPL•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••LINDA → Lua Integrated Non-complex Device Assigning•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
February 28, 201214 yr Emile, are you sure you're using the latest version of LINDA? Search through the files shows, that LINDA do not use 66C1 offset in any way.Hi Artem,Thanks for your reply and it turns out that I owe you an apology : my version of LINDA was indeed quite outdated. I've now updated to the latest and can use 66C1 OK. Sorry for the false alarm :(. Cheers, Emile Bax.
Create an account or sign in to comment