Search the Community
Showing results for tags 'sdk'.
-
After installing the FSX SDK for FSX Acceleration I did not get a tools menu so I checked the dll.xml in the FSX application data folder, it only included the code added for FSUIPC. Later I was able to find a working dll and I copied it in and pasted the paths for SDK tools. Shortly later the sim started having big problems so I reinstalled it. Is it possible that this happened because I installed the Acceleration expansion pack before installing the FSX RTM? This is the code I found: <?xml version='1.0' encoding='Windows-1252'?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> I did change the paths to make them accurate for my installation.
-
Hello! I have a small problem with some selfmade sceneries for MSFS. If anyone has a solution, I'd appreciate it. Over the last year I made three sceneries for MSFS with the SDK: https://flightsim.to/file/61989/flugplatz-gstaad-saanen-lsgk-for-msfs https://flightsim.to/file/59076/flugplatz-speck-fehraltorf-lszk-for-msfs https://flightsim.to/file/54819/flugplatz-hegmatten-lsph-for-msfs But there is a strange problem with my custom groudn textures: As soon as I have more than one of my own sceneries installed, they won't load anymore. Only when I use one scenery at a time, the ground textures will load correctly. I looked trough all the files if there are duplicated GUIDs, false file names or something else. But I found nothing. I have really no idea what is causing the disappearance of those textures. Does anyone here have an idea or a solution? The tutorial I used to add my ground textures: https://www.youtube.com/watch?v=yI5iZCrkjVc
-
Hi! A few days ago I finished my own scenery for MSFS. But sadly it has some problems with my custom ground textures. It should look like this: But sometimes my textures just disappear: I don't have a clue why those textures sometimes work and sometimes not. Does anybody have a solution?
-
Voglio segnalare che dopo gli aggiornamenti di Settembre all'interno del mio simulatore di volo è IMPOSSIBILE selezionare le procedure SID, ILS, GPS, fix point ecc.. introdotti dagli utenti nelle mod e negli scenari creati e personalizzati. Purtroppo non posso allegare le MOD ed i progetti.. ma vi assicuro che da quando sono state rinnovate e aggiornate le SDK, gli scenari creati dagli utenti e personalizzati contenti ILS, GPS, Fix point ecc.. queste procedure NON sono selezionabili nel gioco.
-
I would like a way to receive goal data automatically after a scenario ends. I can see in the SDK samples there are two with features I need. First is the C++ MissionAction project which runs and connects to P3D and waits for a "Windows" event (scenario resolution) to be received before displaying result 0 = failed, 1 = crashed, or 2 = complete... from my understanding. But doesn't pass goal data. Second is the C# Managed Mission Objects project which runs and opens a GUI to let you button connect to P3D and button request goal data. I would either need to add a way to receive goal data after the "Windows" event (scenario resolution) in MissionAction or have Managed Mission Objects wait for the "Windows" event. Any assistance with this?