Stickbender
SYSOP
Infamous Blowhard
Attaboy Points: 114
Offline
Posts: 5324
Since August 24, 2007, 06:45:10 PM
Got Thief?
|
 |
« Reply #10 on: July 25, 2010, 01:42:42 PM » |
|
Well, its working now. Here is what I did.
First, I edited all the file paths in the dll.xml file thats in the applications data\microsoft\FSX folder under my user account. I removed the ...\Microsoft Flight Simulator stuff and just made a direct link. KA938 also thought of this. And I had done it a couple days ago and it didn't work. But there was a step or two needed still, read on.
Then I edited FSX.CFG and removed all references to the SDK folders in the TRUSTED list. There were many. ANd they were messed up, see?
E:\FSX\Microsoft Flight Simulator X\GAUGES\BoeingGeneric.DLL.btlknnlqwuaboztceuhtbaibillrqzwblwklrcti=2 E:\FSX\Microsoft Flight Simulator X\SDK\Mission Creation Kit\object_placement.dll.irltbqwtniwukebkiubnukoubbbukqnaucezlnbt=0 E:\FSX\Microsoft Flight Simulator X\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll.kaeobhzcatthcowuztenzzihqntnrnzhkqwthlkn=0 E:\FSX\Microsoft Flight Simulator X\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll.zuozlclokqqahelwriirekhtlceiqoaottezzoui=0 E:\FSX\SDK\SDK\Mission Creation Kit\object_placement.dll.owbotlouczuhotkkucoetreebhbkkuqlwalckleb=1 E:\FSX\SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll.akuhntrqkoolwhequiwtlbzbwkkczklncbwzlkwt=1 E:\FSX\SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll.ttlkwwaicickorcrokeehcuuwchzlrqwuqhurqcq=1
What tripped me up is that the SDK got installed in a place other than stock and the silly program assumed it was elsewhere. Manually editing the file, to give a direct path, instead of using the assumed string. See red highlights in dll.xml below.
I have an FSX folder on the E: drive, inside of that I have several folders, one is FSX itself, the FSE client, and other tools. So in other words all the FSX related stuff lives in that folder. For some reason, the SDK landed here..E:\FSX\SDK\SDK which I guess means I created a folder first, then installed into that folder. I was in a bit of a hurry to get up and running because it was around New Years Eve and we did the ski resort stuff.
After I edited the the files, I ran the ConfigSDK.EXE in the SDK folder. It runs through and links everything to the root of the FSX install path. Fixed..
<?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>E:\FSX\SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\FSX\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>E:\FSX\SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> </SimBase.Document>
I forced them to look elsewhere. Normally FSX will assume the SDK is installed inside of the ...\ Microsoft Flight Simulator X\ folder. See? And it was not smart enough to know that, so manually changing the files, then running that utility lined it all up. I can now make new SAR's and Missions. Yay!
Thanks for all the input, I hope this helps others as well.
Look this over Ian, and maybe share your info, we get that working but I am thinking this might be a clue for you..
|