... Perhaps there may be one exception to this: All default airport and navaid data belong into an updatable database rather than hard-coded into .bgls. But even this modification should (and can) be accommodated without giving up present file formats like .bgl, .dds, .bmp and such themselves. Kind...

Your chances of getting a useful response will be much better in the iFly support forums.

Use SHGetKnownFolderPath or SHGetFolderPath to retrieve either the Program Data or the AppData folders.
That's what those folders are for.

Doug

Have a look at the C gauge sample that is included with the SDK. There are six different gauge elements included in one dll - including the FlightMap gauge, which utilizes GDI.

Doug

Clearly, the event doesn't get called when you select a failure in the menuing system.
You can certainly follow the failure variables to see if the engines are failed or not:
GENERAL ENG FAILED:index

Doug

The debug versions of the runtime libary files are not included with the redistributable package.
If your dll is still compiled as a debug build, it will only load on a system that has the appropriate version of Visual Studio installed.

Regarding xml file encoding, see two detailed posts by Virtuali of FSDT on page 7 of this thread:
https://www.avsim.com/forums/topic/5113 ... v4/?page=7

Doug

I have to confess I don't know anything about C#, so I don't think I'll be much help with this.
Does the SimConnect log on the server indicate that your app is connecting?

I am fairly certain (perhaps Elaine can confirm) that SimConnect.xml needs to be saved in Unicode format, not plain ASCII. That may be your issue.

The computer on which P3D is running (PC1 in your case) is the server.

Track the status of the SIM_ON_GROUND variable. When it becomes false, read Lat and Lon.
If you're running in-process, you can use the GPS interface to calculate the distance between here and there.
If not, you'll have to implement a great circle calculation to get your distance.

You might try arming your torpedoes with proximity fuses. If they get to within X meters of a ship, they will explode.
You would need to make the calculations somewhere (gauge, module, external app) but it should be completely do-able.
Doug

I'm wondering if you might be better off using events to do this.
I really don't know very much about modelling, but I think you can trap events with MDL xml code. If so, you could use SimConnect to send custom events to move stuff around on the carrier.

I suspect that continually calling register_named_variable() is causing at least some of the heartache. I would go with something like: void On6hzUpdate() { for (int i = 0; i < 110; i++) { int k = check_named_variable(strings[i].c_str()); if (k == 0 ) k = register_named_variable(strings[i].c_str());...

I think you're missing an operator in here:
(E:ZULU TIME, seconds) (&gt;L:APTIMER, seconds) (L:ELEV_TRIM, number) -100 max 100 min (&gt;L:YOKE_Y, number)

Doug