mgh

Is it possible to have multiple instances of FSUIPC executing at the same time - each having its own shared memory area?

The right hand columns in my FSUIPC4 Offsets Staus.pdf are headed 'FSX Read' and 'FSX Write' and are No-SimC+ and No respectively. I misinterpreted them I think you meant 0x31C8 rather than 0x3168

Thanks. I'm obviously looking in the wrong place. I can't see the 'No' entries in FSUIPC4 Offsets Status.pdf - where should I be looking? EDIT:Answer FSUIPC for Programmers.pdf Does FS no longer provide this information in G units?

According to the documentatiion offset 0x30D0 is "Vertical acceleration in G‘s. This is in double floating point format (FLOAT64)." With an aircraft on the ground it returns 1226.4665... which I can't relate to anything. I'm reading it as a 8 byte double using version FSUIPC 3.9.9.9 with FS9.

Thanks for your helpful reply. I did mean Lua with FSUIPC. I think I'll stick with what I know on the old dogs/new tricks principle. I use Borland C++ Builder and creatde a component that encapsulates the published FSUIPC code. This means I can simply drag&drop the component onto a windowed application, or create in on-the-fly with a single line for a non-windowed one. I can use the normal Borland debug facilities to check my application running with Flight Simulator and to make changes while it's still running.

What are the relative merits of using Lua and C/C++ with FS, specially for those who have a good understanding of C/C++ programming?

Why not read aircraft latitude (0x0560 or 0x6010) and longitude (0x0568 or 0x6018) and set 0x0250 accordingly?

That's the answer - not the one I was hoping for so I'll have to write my own gauge.

It's simpler than that. Basically, I want to control a engine (1 for exmple) by writing directly to offset 0x088c. That does control the engine but has the side-effect of moving the visual throttle position to match the value written. In other words, the visual throttle position is determined by 0x088c. What I want is for the visible throttle position to be determined by the value of offset 0x332e and not to change with the value of offset 0x088c.

May be I wasn't clear enough. I've coded it in C++ as a separate process and it controls the engines correctly. By "visual" I mean the throttle position shown in the virtual cockpit: by "real" I mean the joystick physical position. What I want to achieve is that the visual throttles remain in sync with the physical one so that the visual throttles always follow the physical one. What actually happens is that the visual throttle position changes with changes in my variables f1 and f2 even though the physical position is unchanged.

For various reasons I would like to control two engines using a single throttle lever and another programmable variable as follows: Write 8 (bit 4) to 0x310a Read 0x332e to Lever Write Lever * f1 to 0x088c Write Lever * f2 to 0x0924 [/CODE] This controls the engines as I wish when I test it with a with stock FS twin-engined aircraft. The engines and individual levers follow 0x088c and 0x092c respectively. Ultimately, in my own aircraft, I need a single throttle lever which visually follows 0x332e.. Any ideas welcome!

I've uploaded to the AVSIM library the source files in tfsuipc.zip to create a component for Boland C++ Builder 4 that encapsulates FSUIPC facilitating its use.