December 11, 201015 yr So I have a weird issue where grass textures are bleeding through ground scenery at most of my add on airports and in an effort to fix that I thought I'd try reinstalling textures from REX and Ground Environment, as well as opening up UTX to make sure everything was healthy. After pushing a new set of textures from REX, and checking the boxes in Ground Environment to install their textures, FSX is not loading any add-on dll's. LevelD, Ezdok, bglmanx, FSUIPC, none of them load up when I launch FSX. The FSX.cfg file looks ok as the modules are still listed there, as is the dll.xml file, but still none of them load. Instead of fixing the texture problem (which is still a problem by the way) none of my other add-ons work anymore.Any thoughts?Just when I had a pretty stable system... - Aaron
December 11, 201015 yr This dll.xml is a sensible part of FSX so it might look intact while just one character is missing or something.What you can read in the [Trusted] section of the fsx.cfg aren't the modules that are getting loaded but were and received permission to constantly do so. So you could delete some of those dll entries there and see if FSX asks again for permission. If he does, they actually get loaded. If not, go back to the dll.xml and check for errors there.A virgin one looks like this if you have e. g.the "Gold" version of FSX installed (the paths might differ, be aware!) <?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>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon></SimBase.Document> <Launch.Addon> opens the section for a new dll while </Launch.Addon> closes it. </SimBase.Document> closes the whole file.
December 11, 201015 yr Author DLL.xml file is unmodified from 10 days ago, so it doesn't seem to be the contents of the file. Seems more like the file isn't being called anymore at all. - Aaron
Create an account or sign in to comment