Hi to all guys, I installed perfectly maddog under FSX:SE and all works like a charm. The only problem is that I can't save the panel state because under FSX:SE addon menu there is no Maddog item. Does anyone know how to workaround this issue? Is there anything to add to exe.xml or dll.xml?

 

Anyone of you that use maddog under FSX can check if there is any particular entry in exe.xml or dll.xml?

 

Thanks a lot in advance

 

 

Anyone of you that use maddog under FSX can check if there is any particular entry in exe.xml or dll.xml?

 

If it's the Maddog 2010 Pro, should have these in dll.xml

 

  <Launch.Addon>
    <Name>Fly the Maddog</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Flight Simulator X\Modules\LeonardoSH.dll</Path>
  </Launch.Addon>

 

Change "D:\Flight Simulator X\" to wherever your FSX-SE is

Thanks so much Gerald, I'll try and report back asap.

 

Ric

Mmmhh very strange, the entry lines are present in my dll.xml but no Maddog menu is present.

 

Any help? maybe a simconnect problem?

Make sure that the shown path in the <Path> line of DLL.XML does accurately show the drive letter and correct FSX folder name actually in use in your FSX-SE installation. The Maddog installer may have used a default path to the "modules" folder, rather than the path you actually have.

 

Insure that the <Disabled> line shows "false" rather than "true"

 

Check in the FSX Modules folder to see if the LeonardoSH.dll is indeed present.

 

Do other installed add-ons that are specified in DLL.XML (like FSUIPC) show up in the FSX add-on menu? It may be that your DLL.XML file is partially corrupt due to a syntax error. XML files are very prone to this problem - one extra white space character where it does not belong, a period or comma out of place, an extra carriage return or line feed character embedded in the text, a missing open or closing brace "<" or ">".... any of these things can render an XML file inop.

 

Some add-ons that add new entries to DLL.XML during initial installation are known to cause syntax errors in certain cases. Some of the installers used by FeelThere aircraft are known to be prone to do this. I recently installed the FeelThere EJets EMB175/195 to my FSX-SE system, and lost all entries in the FSX add-on menu after doing so. When I looked at DLL.XML in Notepad, I did not see any obvious error at first. I finally discovered that the FeelThere installer, for some reason, had placed a single period character at the very end of the file, right after the last closing brace. It was enough to make the file unreadable by FSX.

 

I edited out the character and re-saved the file, after which everything worked once more.

Hi Jim and thanks first of all for your reply:

 

1) Path is correct

2) "false" variable is set, not "true"

3) LeonardoSH.dll is present

 

Here is 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>RAASPRO</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>Fly the Maddog</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>E:\SteamLibrary\steamapps\common\FSX\Modules\LeonardoSH.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Options</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDGOptions.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Events</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDGEvents.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Sounds</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDGSounds.dll</Path>
  </Launch.Addon>
</SimBase.Document>

I open it usually with notepad so can't see if there is a format error or space/wrong carriage return, I'll try with a xml editor.

 

As you can see all other stuff is present and work fine, PMDG, FSUIPC, GSX, EZCA etc

 

Apparently seems all is okay, but Maddog menu is not present at all.

Riccardo,

 

Everything does look OK in your DLL.XML

 

One thing you might try - make a backup copy of your DLL.XML first, then edit the <Path> line for the Leonardo DLL to show just the relative path (similar to the FSUIPC listing).

 

In other words shorten the <Path> line to simply: <Path>Modules\LeonardoSH.dll</Path>, save the file and load FSX again.

 

It seems that FSUIPC and the PMDG DLLs do not actually require the full path name - perhaps the Leonardo DLL does not need it either...

 

In a few hours, when I get home, I will check my version of DLL.XML as I also have the Maddog, and it does appear in the FSX Add-On menu.

Thank a lot Jim, I have already tried relative path changing, but with no success.

 

I tried manual dll load (true mode) in dll.xml and effectively FSXSE ask me if I want to load LeonardoSH.dll, I answer YES butthere is no Maddog menu in the game. So FSXSE load correctly the dll but it seems to do not appear in the menu. Do you think it would be a SimConnect problem?

 

I installed only legacy simconnect of Acceleration Pack (XPSDK), not SP1 or SP2. I installed it for PMDG MD11, remeber? And the other simconnect version are from EZCa and the last one of FSXSE if I well remember, so I miss only legacy SP1 and SP2.

 

If I well remeber you installed sp1,2 and xpsdk, correct? Do you have The Maddog installed in FSXSE?

 

Thanks for report back, it's very kind of you.

Hi Riccardo,

 

Yes, I installed all three legacy simconnect versions found in the FSX-SE SDK, which I believe were from original FSX, SP1 and Acceleration (SP2)

 

It does seem like you might have a simconnect problem. The original code for the Maddog goes back to FS9, then it was updated for FSX in 2006, so there is a good chance it might need one of the earlier simconnect versions. There is no problem having all three versions installed on your SE computer at the same time.

 

I do have the Maddog running under SE, and the plane works great AND the Maddog menus do appear in the FSX-SE add-on menu.

Hi Jim, you are great! Thanks so much, all now works perfectly.

 

I installed RTM (10.0.60905) and SP2 (10.0.61242) version of SDK and Maddog menu appears correctly.

 

Now I can save my panel state! Thanks

Hi Jim, you are great! Thanks so much, all now works perfectly.

 

I installed RTM (10.0.60905) and SP2 (10.0.61242) version of SDK and Maddog menu appears correctly.

 

Now I can save my panel state! Thanks

You're welcome! Enjoy the Maddog!