After install no buildings...

[Mickey]

All tree files are in the decriben folders.
C++ is installed again.

No changes.
Good night Umberto

[Mickey]

Was this the end?
No solution?
We give up?

Thanks for trying to help me.
Max

[virtuali]

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.

[Cthulhus]

Their is an incompatibility between FSinn (VATSIM client) and FS Addon manager...

[virtuali]

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

Code: [Select]

<?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

Code: [Select]

<?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]

[fbass]

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

[virtualstuff]

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

Anyway thanks for the update...

[virtuali]

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.

[markS]

Just to let you know that I have the same problem. I lost addon manager after 1.3 install.

Regards,
Mark

[virtuali]

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.

[markS]

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

[virtuali]

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:

Code: [Select]

<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.

[markS]

virtuali,

That solved the problem.

 Thankyou !

Regards,
Mark

[virtuali]

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:

Code: [Select]

<?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:

Code: [Select]

<?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.

[virtualstuff]

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 
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

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