<r>Adam, please disregard this error. In trying to debug issues related to the discussion in this post here -> ...<br/> <br/> <br/> <br/> <URL url="http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=264"><LINK_TEXT text="http://www.prepar3d.com/forum-5/?mingle ... opic&t=264">htt...

<t>when you say "Win32" platforms, i assume you mean"x86". These are C# applications. The only platform targets are x86, x64, and Any CPU. and again, yes, the platforms being targeted in my applications are indeed "x86". yes, we are targetting Prepar3D 1.1 using Prepar3D SDK 1.1. I will email the te...

<t>yes, .NET 4.0 and P3D 1.1 SDK were installed in the correct order on the development machine. .NET 4.0 was installed months ago prior to any Prepar3D client development, so all the subsequent installs of P3D SDK updates were installed post-.NET 4.0.<br/> <br/> <br/> <br/> since the client program...

yes, the application is already being built as x86 only, error remains.



note: have also verified that it is indeed running as a 32-bit process in the task manager

<t>more information regarding the same problem above ^<br/> <br/> <br/> <br/> I’m trying to run a Prepar3D SimConnect client in a Windows 7 Professional 64-bit environment and am encountering the following exception whenever my client tries to reference anything in the LockheedMartin.Prepar3D.SimCon...

<t>thanks, Adam. I have not had to do anything with sim object creation so I was not as familiar with the information contained within that section of the SDK but I will keep it in mind for future reference. In the interest of improving the SDK in future releases, the ChangeVehicle() example is a li...

<r>it would be nice if, in addition to being able to receive the usual notifications when things are beginning to load, i.e. flight files, aircraft files, etc., SimConnect clients could also receive notifications when these things are finished loading as well. Often times I would like to do some add...

also, the problem of the aircraft seeming to start with landing gear slightly in the ground seemed to be related to trying to pause the sim too soon after reloading the aircraft. not pausing the sim after loading a vehicle did not cause the same problem

<t>figured it out i think. ChangeVehicle() seems to work off of the "title" field for each "fltsim.X" object in the aircraft configuration file for that aircraft model. for example, to get an F-35C from Abacus to load through SimConnect, I had to pass the title of "Abacus PC F-35C Lighting II" from ...

when changing aircraft with SimConnect_ChangeVehicle(), the new aircraft will load slightly slanted to where the back end of the aircraft is underneath the ground.



also, how do i determine the correct name for each vehicle to pass through SimConnect?

ah ok, that makes sense. thanks, Beau.

whats the deal with the new external sim APIs? it is not clear to me what benefit they provide. why were they created and what are some examples in which they might be used?

<t>i'm trying to create some malfunction control from an IOS via my SimConnect client and would like to determine how I can directly cause the failure actions and determine when they have occurred and when they have been removed.<br/> <br/> <br/> <br/> what would the correct way to raise and lower a...

a couple more questions...is it necessary to call WeatherSetModeCustom() when setting global weather with SimConnect or is it sufficient to call WeatherSetModeGlobal() in conjunction with "GLOB" in the metar string? will one override the other depending on the order that I call them in?

ok, thanks Tim.