Thanks for confirming. Good to know.

Hi adiemus, well...I am not super proficient with this stuff, but as I am able to do the following: ExecuteCalculatorCode("(>C:fs9gps:FlightPlanWaypointIndex, number)", nullptr, &waypointNo, nullptr) in order to set the current waypoint index of the GPS system And it actually changes ...

As the author of both the TacPack and linked doc, at least at the time I wrote it (back before Prepar3D even existed) it wasn't possible to access C: vars inside the version of execute_calculator_code() exposed by the Panels interface. Now, I've not ever tried ExecuteCalculatorCode() from IPanelSyst...

You're going to need to provide far more detail on what you've actually tried, likely with example code and explicit test results explaining how those results differ from what you'd expect.[1] Otherwise it just seems like you're trying to get someone else to not just build it for you, but also expla...

Works fine here in P3D v4, going all the way back to FSX. That structure is returned by the "Frame" event you can subscribe to via SimConnect_SubscribeToSystemEvent(). This will call your SimConnect callback with RECV_ID set to SIMCONNECT_RECV_ID_EVENT_FRAME, which in turn carries a popula...

Is there a way to programmatically control the state of the "ShowWeather" boolean for a camera? I can't find anything via the PDK or SimConnect. (I'm looking to simulate an imaging pod with multiple sensors, some of which can see through atmospheric moisture and some which can't) In theory...

Having read more about COM versioning, I think now that the headers are fine, it was me that was mistaken. For anyone confused as I was how you'd use IBaseObjectV410, for example, when ISimObjectManagerV410::GetUserObject() takes a **IBaseObjectV400 argument, you have to get the IBaseObjectV400 firs...

Looks like IBaseObjectV410 has the same issue.

The v4.1 PDK added some new functionality I wanted to try, so I switched our existing code to use the new headers. This worked fine (while my code was still referencing the V400 stuff) but as soon as I started trying to use IWindowV410 or ICameraSystemV410 it all refused to compile, seemingly becaus...

Actually, in fairness, we (VRS) are trying to help FSX@War with P3D v4 support but the FSX@War project is running at reduced strength right now which slows the process down and imposes some limits on what can be done.

In any case, not sure why people are bringing it up on LM's forums.

And actually, it's worse than I realized. Moving the call to SimConnect_RequestDataOnSimObject() before SimConnect_RequestClientData() does fix the SIMCONNECT_RECV_ID_CLIENT_DATA callbacks, but breaks the SIMCONNECT_RECV_ID_SIMOBJECT_DATA callbacks expected from RequestDataOnSimObject(). So either y...

Seems I keep running into SimConnect bugs of late. See: http://www.prepar3d.com/forum/viewtopic.php?f=6311&t=127917 This time, the issue is with ClientData. Long story short, on P3D v4.1 (and v3.4hf3, and v2.5) if you call SimConnect_RequestDataOnSimObject() after SimConnect_RequestClientData(),...

Given the timing of my initial report, perhaps this got missed due to the holidays, but it seems critical enough to warrant bumping it.

This seems to be related to the issue I posted here: http://www.prepar3d.com/forum/viewtopic.php?f=6311&t=127900 If I invoke P3D v4.1 with a bad command-line argument, ala: c:\path\to\Prepar3D v4>Prepar3D.exe -badarg then SimConnect behaves differently than if no bad command-line argument was pa...

This will be a weird bug to describe, but know that it was FAR weirder to track down. :-) If we invoke Prepar3D v4.1 thusly: C:\path\to\Prepar3D v4>Prepar3D.exe -badarg we'd expect it to load, then display a dialog that says: The requested scenario, from command line arguments, is either corrupt or ...