FSDreamTeam forum
Products Support => Zurich scenery for FSX/P3D => Topic started by: Mickey on December 25, 2007, 08:18:41 pm
-
Hi
Configuration: VISTA, FSX, SP1 and SP2.
After Installation ther are no buildings and there is no Addon-Menu. What a pity. I tried with the newest Vesion 1.2.1, datet at 25.12.2007. No chance! Do you hve any ideas?
Max
-
Your configuration probably prevented Addon Manager to run.
Please read the "Troubleshooting" section of the fsdt_install_guide.pdf, found at fsdreamteam\zurichx folder under the FSX root folder, and try to follow all suggestions. If none is working, please report back.
-
Thanks for responding so fast.
I made some new trials. Antivirus deactivated an new Installation. Result: As before. No Buildings, but traffic, planes an ramps. No Addon-Menu. After 2 hours of deep frustration, finaly i have removed the Software.
Max
-
The product didn't run because probably something was wrong with your FSX config. Most probably, a Simconnect issue or something else in Windows, or a Vista permission issue.
The issue would have surely been resolved with further help (I asked to follow the standard suggestions in the manual, just to eliminate the most common problems first), because the product is confirmed to be working.
By uninstalling it, the only result you obtained is to lost a chance to fix something in your system on in your FSX config that, sooner or later, will eventually surface with something else.
-
I expected more help in "Troubleshooting" an this forum.
-
I have installed the Software again and repeat shortly:
VISTA, FSX, SR1 and SR2
Installation LSZH as User or Adminstrator
Installation with ans without Antivirus
No buildings visible
No addon menü visible
Please give me your instruction.
Thank you
Max
-
After installing, you should have seen two security warnings about running Addon Manager, one coming from Windows and the other (if you replied Yes to the first request) from FSX, asking to trust the module. You have to reply Yes to both questions, then it might be the Addons menu will still not be there. Exit FSX normally, launch it again and see if the menu is there.
If is still not there and if you haven't seen the two security questions, check if your DLL.XML file has been updated with the bglmanx.dll module. File is located at %APPDATA%\Microsoft\FSX. Open this file with a text editor, and check if the lines with the Addon Manager has been added.
-
I found the relating file, but not in the sent path.
C:\Users\Max\AppData\Roaming\Microsoft\FSX
Text:
<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>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
</SimBase.Document>
Max
-
I found the relating file, but not in the sent path.
C:\Users\Max\AppData\Roaming\Microsoft\FSX
That's exactly the same thing. %APPDATA% it's just a shortcut you can use to find C:\Users\YourUserName\Appdata\Roaming. If you type %APPDATA%\Microsoft\FSX on the search area of the Vista Start button, it will show up the same folder.
Your DLL.XML looks fine.
Next step: I've asked you if you have seen or not the 2 security warnings about executing the Addon Manager, one coming from Windows, the other coming from FSX.
-
At the first installation i have accepted the messages. Later at the new installation the warnings did not appear.
-
All right. Before going forward with the questions, can you please try downloading and installing the Addon Manager stand-alone installer we just relased ?
The link it's on the "Products" page.
-
Ok Umberto
Dowload was done. Installation no Problem. There were no Questions to answer. Still no Addon-Menue.
Thank for helping to solve the Problem.
Max
-
All right, try to do the following to activate diagnostic mode for the Simconnect:
Open notepad, and copy the following text:
[SimConnect]
level=verbose
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files
At the next FSX launch, you should see a text window with diagnostic message, that should tell you what's going wrong. Let me know what you are getting, so we can have an idea what's happening.
-
OK. Here ist the text:
0.00000 SinConnect version 10.0.61259.0
0,02296 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SinConect, MaxClients=64
0,03737 Server: Scope=local, Protocol=IPv6, Adress=::1, Poer=49900. maxClients=64
0.04412 Server: Scope=local, Protocol=IPv4 Adress=127.0.0.1. Poer=49909, MaxClients=64
0.26978 DLL Failed to load. Check for missing dependecies.
0.26988 Load Failed: Error=3 Path="bglmanx.dll"
Max
-
0.26978 DLL Failed to load. Check for missing dependecies.
0.26988 Load Failed: Error=3 Path="bglmanx.dll"
All right, we are getting there, a DLL required by the Addon Manager is missing. The ones not available in a standard Windows installation are all provided by the installer, and are:
in the FSX folder:
msvcr71.dll
python25.dll
in c:\ProgramData\Esellerate
esellerateengine.dll
Check that all of these are in place.
Plus, there are the MS Visual C++ updated runtimes, that are automatically installed by the installer. You can separately download the redistributables here:
http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
If you still have the same problem after checking all of these, it means it's nothing related to the Addon Manager. Instead, some other DLL that should be supplied in every Windows installation, it's missing. Sometimes, reinstalling .NET runtimes fixes a lot of Windows missing files.
-
All tree files are in the decriben folders.
C++ is installed again.
No changes.
Good night Umberto
-
Was this the end?
No solution?
We give up?
Thanks for trying to help me.
Max
-
I tried all possible solutions related to the Addon Manager itself. The diagnostic message about a missing DLL (unfortunately, Simconnect doesn't exactly tell which one is) means a DLL file is missing on your machine.
Our installer supplies all DLL that are not part of a normal Windows installation and, since you said all of these are in place, it means something else that should normally come with Windows is missing. Or, something that FSX itself is supposed to install.
As I've said in my last message, you might try updating all your important Windows runtimes, like the .NET (we don't use it, but it might restore something that is actually missing on your machine), or perhaps IE7, or all the latest Windows updates, or the latest DirectX runtimes.
You can also try if there's something in the Application log of the Event Viewer related to FSX that might tell something more about the missing DLL.
-
Their is an incompatibility between FSinn (VATSIM client) and FS Addon manager...
-
UPDATE:
Just downloaded FSInn, and I can confirm it's a problem of their FSCopilot.dll module. IF FSCopilot.dll is loaded *before* bglmanx.dll (Addon Manager) in the DLL.XML file, Addon Manager will be unable to call Simconnect to create its own menu.
Also, even with a clean DLL.XML file, just FSCopilot.dll active and nothing else (no Addon Manager at all), FSX crashes when exiting. It seems FSCopilot leaves FSX in an unclean state, that's probably why Addon Manager can't run if loaded after it. It might be also some obscure security problem, because Addon Manager is a proper digitally signed executable (as requested in FSX), and FSCopilot isn't, that might create unexpected issues depending on the loading order.
By reversing the order of the modules in DLL.XML, and putting Addon Manager *before* FSCopilot, the problem is fixed, and Addon Manager will work together with FSCopilot.
I already wrote in January last year to FSCopilot authors about issues between our modules, because we already hit another problem related to menu creation, but we both agreed we didn't had the slightest idea why it would happen. I found a workaround within code but, it looks like this has been broken again, probably by more recent FSCopilot releases.
To defend ourselves by this issue, that is not related to our software, I modified the installer to automatically put Addon Manager lines *before* anything else in DLL.XML, it should be available tomorrow.
However, if you already have Addon Manager lines (you surely have it, if you ran our installer at least once), you have to move the sections manually. The section lines containing bglmanx.dll, starting from <Launch.Addon> to </Launch.Addon> tags included, should be moved before FSCopilot section.
For example:
Bad
<?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>FS Copilot</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>modules\fscopilot.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
</SimBase.Document>
Good
<?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>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FS Copilot</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>modules\fscopilot.dll</Path>
</Launch.Addon>
</SimBase.Document>
[/quote]
-
I have the very same problem as the rest who posted here. I've been using the Zurich package since the V1.0 release. I installed 1.1, 1.2, and now 1.3. I never had any problems until this latest attempt.
I checked the troubleshooting guide - no joy. I checked all the files that are required and they are present - FSX folder, Program Data folder, etc. Simconnect is working properly. All the *.dll files are present. I downloaded the latest Addon Manager and installed it.
There was no Addon Manager entry on the FSX menu bar. With the exception of the ground textures, the entire scenery disappeared. I have Acceleration installed in FSX. My settings remain the same as with V1.2 (no problems at all).
When I tried to install V1.3 there was a momentary error message but the installer continued to work.
I ran the Simconnect diagnostic but it just kept on running and running. The first part of it is as follows:
0.00000 SimConnect version 10.0.61259.0
0.02120 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simul
ator\SimConnect, MaxClients=64
0.02761 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49206, MaxClients=
64
0.03073 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49207, MaxCl
ients=64
Here is my dll.exe file:
<?xml version="1.0" encoding="Windows-1252" ?>
<SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>True</Launch.ManualLoad>
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<Name>GoFlight Hardware Interface</Name>
<Path>C:\Program Files\GoFlight\GFDevFSX.exe</Path>
<CommandLine></CommandLine>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>3wirex</Name>
<Path>3wirex.exe</Path>
</Launch.Addon>
</SimBase.Document>
[/quote]
Thus far, I cannot get this new scenery update to work nor can I get the addon manager to work. BTW - I have to add the appropriate entries to the dll.exe file manually. The addon manager did not add them when I installed it.
Frank
-
UPDATE:
Same problem here both installs don't work:
FS9 doesn't work with the default FS9 exe SP1 file solution is to use the NOCD exe file or patch it...
You should do better your home work and I find bglman still very user unfriendly...
FSX version just no buildings
All the above has nothing to do with it serious both install aren't just correct (ps... I have a bit more understanding of the inner works)
My guess is that the dll.xml is corupt by your installer going to have a look into it...
All previous versions worked just fine you need to do a bit more homework and testing before releasing ;-)
Cheers,
André Folkers
Ok just tested and found that the insert from the bglmanx.dll into the dll.xml was missing a tag for the next section...
</Launch.Addon>
So working know... but both install routines aren't correct to say the least,
hence it's strange that the FS9 version only work with a not original FS9.exe SP1 file ;D
Anyway thanks for the update...
-
FS9 doesn't work with the default FS9 exe SP1 file solution is to use the NOCD exe file or patch it...
This is clearly explained in the 1.3 update announcement message. Users asked to be able to use >2GB patch in FS9 but that, unfortunately, lost compatibility with FS9 CD protection. Note, this is true regardless if you patched or not FS9.EXE to support more than 2GB. We think it's way better to get rid of OOM errors that the >2GB patch fix, than having to keep the CD in the drive.
In fact, this new version of the Addon Manager has been out already for about 10 days, in the Stand Alone version, about 200 people downloaded it, and we got just 2 messages in the FS9 section about it, that was of course fixed by applying the no cd patch to FS9.
We used this days as a test trying to assess how many people are still using FS9 with the CD inside. Since the ratio was so low, we decided to put it also in the Zurich installer and make it permanent.
You should do better your home work and I find bglman still very user unfriendly...
That's exactly the opposite, it's now way more compatible with everything, DEP, UAC, Vista 64, Antivirus programs, and the >2GB patch, all things that the previous version didn't support very well. The only thing that doesn't work with, it's the FS9 CD check.
All the above has nothing to do with it serious both install aren't just correct
I don't understand were the FS9 installer is wrong.
My guess is that the dll.xml is corupt by your installer going to have a look into it...
That's possible, I'll look into it, it would be useful if you could send me your DLL.XML file.
All previous versions worked just fine you need to do a bit more homework and testing before releasing
Of course we tested it, and of course it worked absolutely fine on all our machines, but the truth is, you really never know, until it goes in the user's hands, most of the work in the installer, is to defend itself against hand-edited files with syntax errors (expecially in scenery.cfg).
hence it's strange that the FS9 version only work with a not original FS9.exe SP1 file
It's either that, or we lose compatibility with the >2GB patch, that was requested by several users.
-
Just to let you know that I have the same problem. I lost addon manager after 1.3 install.
Regards,
Mark
-
Please, have a look here:
http://www.fsdreamteam.com/forum/index.php?topic=300.msg1589#msg1589
If you had the Wilco 737 PIC, its installer corrupted the DLL.XML file, making it difficult to read using standard methods, and that is probably confusing our installer, and other products installers as well (like PMDG)
We'll try to fix the installer to be able to cope with such file, in the meantime, look for a missing </Launch.Addon> tag in the file.
-
virtuali,
I do not have the Wilco 737 installed. Here is what my DLL.XML file looks like if that helps.
<?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>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<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>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Maddog 2006</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\LeonardoSH.dll</Path>
</Launch.Addon>
</SimBase.Document>
Regards,
Mark
-
I do not have the Wilco 737 installed. Here is what my DLL.XML file looks like if that helps.
Your case appears to be different. It's still a problem of a non closed tag, but it's in the section related to MS SDK Visual effect tool
Just add a </Launch.Addon> line after it, so the section will look like this:
<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>
It should work.
Note, you probably already had this problem before, but since the Visual Effect Tool had the <Disabled> set to True, you didn't realize it. Now, when looking for the Zurich missing buildings, by opening the XML file in IE, you found it's corrupted, but it hasn't been corrupted by Zurich installer, it was it already before.
-
virtuali,
That solved the problem.
Thankyou !
Regards,
Mark
-
When I tried to install V1.3 there was a momentary error message but the installer continued to work.
I replied to you in a different post. This might be related to scenery.cfg, but I would like to see both your scenery.cfg and dll.xml files as well, to be sure. If it's related to scenery.cfg, the Addon Manager shouldn't have problems with it. Meaning, you will not have the scenery in the Scenery Library (in that case, simply add it yourself), but the Addon Manager menu should be there.
Here is my dll.exe file.
I do see problems here:
First, there's no dll.exe file at all. Maybe you were referring to EXE.XML, instead. There are TWO Simconect config files. One for external executable modules containing only EXE files, and it's named EXE.XML. The other is for internal modulels, containing only DLL files, and it's named DLL.XML
You can't load a DLL in the EXE.XML file, so you shouldn't have manually added Addon Manager to EXE.XML, it has to go in DLL.XML instead.
The addon manager did not add them when I installed it.
Please, check if the DLL.XML file has been updated, and remove the Addon Manager from the EXE.XML
Also, I see another potential problem here:
<?xml version="1.0" encoding="Windows-1252" ?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>EXE.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>True</Launch.ManualLoad>
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
As you can see, if this is EXE.XML, there shouldn't be another <launch> section with DLL.XML listed.
The correct start of the file should probably look like this, instead:
<?xml version="1.0" encoding="Windows-1252" ?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>EXE.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>True</Launch.ManualLoad>
with the rest of the file following normally.
-
This is clearly explained in the 1.3 update announcement message. Users asked to be able to use >2GB patch in FS9 but that, unfortunately, lost compatibility with FS9 CD protection. Note, this is true regardless if you patched or not FS9.EXE to support more than 2GB. We think it's way better to get rid of OOM errors that the >2GB patch fix, than having to keep the CD in the drive.
What if i have no OOM errors ;-) actually the patched version didn't work either only the illegal NOCD FS9 exe file
Hence you are doing advertisement for illegal files :o
As for the compatibility you could have write a more user friendly install routine with an adjusted BGLMAN file based on the FS9 exe file found ;-) that's actually real easy to do...
It's the FS9 CD check.
Lol serious but for guys protecting there own software thats the only legal file we are talking here about ;D
I don't understand were the FS9 installer is wrong
It doesn't work with the only original legal file ;-)
That's possible, I'll look into it, it would be useful if you could send me your DLL.XML file.
See my message above already solved missing tag isn't checked by the installer no rollback (more error routine checking in the installer ;-))
Of course we tested it, and of course it worked absolutely fine on all our machines, but the truth is, you really never know, until it goes in the user's hands, most of the work in the installer, is to defend itself against hand-edited files with syntax errors (expecially in scenery.cfg).
You be surprised what you can do with ease with a simple install executable ;)
It's either that, or we lose compatibility with the >2GB patch, that was requested by several users.
Or change the install routine to check a bit more and based on the installed FS9.exe install the correct bglman file ;)
Hope the comments are useful
Thanks anyway for a great scenery love the stuff :)
André Folkers
-
Hi Andrè,
please read this post from Umberto: (http://www.fsdreamteam.com/forum/index.php?topic=298.0 (http://www.fsdreamteam.com/forum/index.php?topic=298.0))
Fixed installer is up. Just download the stand-alone Addon Manager installer:
http://www.fsdreamteam.com/download/setup_addonmanager.exe
The installer it's now able to detect which FS9 version you have (with CD check or not), and it will install the correct Addon Manager version.
Note, since the CD-protection-friendly version it's not compatible with the >2GB patch, if you already patched the CD protected FS9.EXE with the >2GB patch, it will not start. If you want to use the stock CD-protected FS9.EXE, the >2GB patch and our product (and Cloud9's), all together, you need to use a no cd FS9.EXE.
In the next hour or so, even the two Zurich installers for FS9 (Standard and CH-Pro) will be updated as well, with the same installation method.
-
As for the compatibility you could have write a more user friendly install routine with an adjusted BGLMAN file based on the FS9 exe file found
This is exactly what the installer that is online now does, it was updated just a couple of hours after the first one so, it's a non issue right now.
Strictly speaking, the whole issue has been only brought up since we listened to users asking to be compatible with the >2GB patched FS9.EXE.
-
As for the compatibility you could have write a more user friendly install routine with an adjusted BGLMAN file based on the FS9 exe file found
This is exactly what the installer that is online now does, it was updated just a couple of hours after the first one so, it's a non issue right now.
Strictly speaking, the whole issue has been only brought up since we listened to users asking to be compatible with the >2GB patched FS9.EXE.
Thanks guys for the great support and I applaud you for listing to your customers
but there are some of us that aren't willing to use the patched version because they don't have OOM ;-)
Hope i didn't offended anyone just sharing my experience with the first installer and
maybe some ideas to improve for future fellow simmers....
Your next scenery is high my list to purchase due to the great quality
and trying to find solutions around SP2 for the ground stuff and last but not least the support...
-
Hello,
first sorry for my bad English ;)
Ok now my Problem. I reinstalled FSX with all my Addons and had maked a new Install on a new Harddisc (same System, only FSX is going to a new Harddisc).
I installed FSX, SP1, SP2.
ZurichX I bought some weeks ago and worked fine on my old Installation.
But on the new Installation I have no chance to get the AddOnMenu in FSX. I read this Thread and a lot more in www (now 8 Hours lost only for ZurichX).
my dll.xml
<?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>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<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>
Message:
0.32512 DLL Failed to load. Check for missing dependencies.
0.32518 DLL Load Failed: Error=-3 Path="bglmanx.dll"
I reinstall FSX and install new, I reinstall all .net`s 1-3, I reinstall SimConnect and and and. FSMap (Aerosoft) use also SimConnect and I installed today this Tool and it will works fine. ZurichX no Chance.
Can you help me?
Greets Frank
-
ZurichX I bought some weeks ago and worked fine on my old Installation.
That's more than enough proof that the product *works*. And if it didn't, you never had the chance to buy it in the first place...
FSMap (Aerosoft) use also SimConnect
That doesn't mean anything. Not every problem is because Simconnect doesn't work. In your case (see message below) it's a system file missing. If Simconnect didn't worked, you would't be able to launch it in diagnostic mode.
DLL Failed to load. Check for missing dependencies.
This is important: a system DLL in your Windows installation is missing. Unfortunately, Simconnect diagnostic doesn't tell exactly which one, so we can only guess.
First, to exclude a problem coming from our installer, be absolutely sure you are running the latest version of it. There's no need to download the whole Zurich again (unless you still are using an older version like 1.2 or less), just download again the Stand-alone installer for FSX, that one is guaranteed to put all the DLL we need that do not come with a standard Windows installation.
If still doesn't work, it's 100% sure it's a Windows DLL that is missing.
It might be the Visual C++ 2005 SP1 runtimes missing or outdated. Our installer will automatically install those runtimes by launching the Microsoft redistributable installer at the end of the installation. If that installer failed or was interrupted for some reason, you'll have problems.
You can try separately downloading it from here:
http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
And, as a precaution, try running the installer in Administrator mode.
Some other things you can try to fix your Windows installation, are installing IE7 (it's not clear from your message if you are running XP or Vista), and installing ALL hotfixes suggested by Windows Update. Some of these fixes might restore the missing files.
-
Now (3 more hours later) I found nearly same Problem in a other Forum. I installed FSUIPC4 and the AddOn Manager will work fine :)
That's strange, because the Addon Manager doesn't use FSUIPC at all, doesn't require it and it shouldn't be affected by its presence/absence. But it might be that FSUIPC installer did some additional Windows fixing that helped the Addon Manager as well.
I think my deinstallation of FSX delete the importend Files and the new Installation dont`t copy this Files.
Unfortunately, the FSX uninstaller, especially the RTM release has still big issues: for example, I think that if you have FS9 and FSX on the same machine, and remove FSX RTM, you'll also lose the FS9 registry keys, confusing all FS9 installers as well.