I cannot get TrafficToolBox running in FSX.I may have a path wrong in the DLL.xml ??? maybe.The question I have first is:Is the original traffictoolbox.dll that came with FSX SDK (on the disk #1) ok to use after applying the FSX SP1 and SP2 updates?If not, that could be my problem.Or, is it, if you do SP1 update to FSX then you have to download a new FSX SDK which I assume would contain a newer traffictoolbox.dll?I downloaded a new FSX SDK SP2 ... but when I went to install it it said I needed to install FSX SDK SP1a first.So, I downloaded SP1a and it said I needed NET framework 2 first.So, before Iget involved with Vasta NET2 I figured I would ask the question.My system:Windows Vista Home premium 32 bit SP2Net frameworks 1.1 , 1.1 hotfix and NET 3.5I installed MS FSX FSX SP1FSX SP2The TrafficToolBox is whatever initially came with FSX.The traffictoolbox.dll I have (checking properties on the file) is dated modified on 9-4-2006 (160kb).<Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX-SDK\SDK\Environment Kit\Traffic Toolbox SDK\TrafficToolbox.dll</Path> </Launch.Addon> <Launch.Addon>I changed it from true to false above.(<Disabled>False</Disabled>) originally True.

The short answer is that you must use the same version of the TrafficToolbox.dll as the version of the sim installed.SDK Installation Versions

Fr Bill,Thanks for the help, appreciated.I did have the 'Path" wrong in the above post .. so I edited it to correct it.But it still did not load and no errors either.Initially I thought if versions of software were "mixed" nothing would work or an error would tell you it is wrong.Yes, the link you gave, I was there but I did not know if it would apply to just my problem with Traffictoolkit or not.That is where I found out about SP1a, mentioned above. It also mentioned Russian for some reason.Darn! now I have to get NET2 ... I really do not like messing with "net framework downloads" at all!

Fr Bill,Thanks for the help, appreciated.I did have the 'Path" wrong in the above post .. so I edited it to correct it.But it still did not load and no errors either.Initially I thought if versions of software were "mixed" nothing would work or an error would tell you it is wrong.Yes, the link you gave, I was there but I did not know if it would apply to just my problem with Traffictoolkit or not.That is where I found out about SP1a, mentioned above. It also mentioned Russian for some reason.Darn! now I have to get NET2 ... I really do not like messing with "net framework downloads" at all!

I am in the process of reinstalling vista and fsx, and even though i use sp2 i have to start the whole sdk thing from scrath1 - install fsx cd then the sdk on disk 12 ---start fsx launch free flight---------3 - sp1, then sp1 sdk4---start fsx launch free flight---------5 - sp2, then sp2 sdk.6----start fsx launch free flight---------i did not delete my .net from last install so did not have to redo it

Fr. Bill,,Quick follow up.FSX SP2 and FSX SDK SP2, matched pair ... is a must!I all worked great.

askanFactor,Your procedure:I am in the process of reinstalling vista and fsx, and even though i use sp2 i have to start the whole sdk thing from scrath1 - install fsx cd then the sdk on disk 12 ---start fsx launch free flight---------3 - sp1, then sp1 sdk4---start fsx launch free flight---------5 - sp2, then sp2 sdk.6----start fsx launch free flight---------i did not delete my .net from last install so did not have to redo it ***********************************************************************Note: It is easy to get SP1 and SP2 for Vista references mixed up with SP1 and SP2 for FSX and FSX SDK's SP1 and 2!IMO, there are far too many SP1's out there for many products.IMO, every update should have a uniqueRname.Well, I had to also install FSX "SDK1a" before FSX SDK 2.0!I did not have to start all over:I installed FSX (rebooted the PC between installs.Each new SDK will uninstall the previous (older) one before the new version is installed.FSX SP1FSX SP2FSX SDK (form disk 1)FSX SDK SP1aFSX SDK SP2.0Then I modified the dll.xml