August 13, 201411 yr I have installed Microsoft Acceleration version 10.0.61637.0 and the Microsoft Acceleration SDK version 10.0.61637.0 on my computer. I am able to use Airport Design Editor without a problem and I installed the SKDs according to all the installation guides online. I have FSX running on my i drive and the sdk is on the c drive I am not sure if that is causing an issue. I however do not have the tools menu displayed. I have done all the suggested items i could find on the forums and it is not working for me. Jason Spiskey Win 10 64bit, AMD Ryzen 7 3800k 3.8GHz, MSI NVIDIA GTX1660ti 32gb RAM
August 15, 201411 yr I have FSX running on my i drive and the sdk is on the c drive I am not sure if that is causing an issue. Yupp you just quoted your issue, You might try using full paths <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> But I doubt it will work, as it seems some paths may be hard wired into the exe's and registry settings and for example that object_placement.dll is referenced by a host of other programs to do it's job. And if any ONE of them does not know about a Drive I then it will not work, FSX was made in September 26, 2007 for the XP operating system. Hard drives were sold by Megabytes not GIG's. Bite the bullet and put it all in the default folders, THEN play with edits. Rule Number ONE<, Always install all programs into their default directory then mess with it after it is running flawlessly.
August 15, 201411 yr Hi Folks Vortac - For any non-standard SDK location dll.xml's entries for the SDK components require explicit paths. Please see FSDeveloper - Wiki - SDK Installation (FSX) To prevent further dissemination of misleading information - - There is zero requirement for FSX & SDK to be on the same drive/path/whatever. - There is zero requirement for the SDK to be in default path. - There is zero requirement to reinstall FSX to fix this. - There is zero requirement to reinstall the SDK to fix this. - configsdk.exe corrects the non-xml paths. for example that object_placement.dll is referenced by a host of other programs to do it's job. And if any ONE of them does not know about a Drive I then it will not work, Pardon ? Personal suggestion - NEVER EVER install into their default directory, particularly with post XP OS's. HTHATBPaul ODG Preview
Create an account or sign in to comment