MADDOG menu options non-functional in FSX/Vista Options

[bob_r]

Hi,

I have an interesting problem which is currently preventing me from continuing to fly the MADDOG sim.

The MADDOG menu options, found under the FSX "Add-ons" menu, although present, do not work. For example, if I select "Maddog - Ground Communication...", and hit enter, the menu just closes immediately. This behavior occurs for all MADDOG options - "Crew communication...", "Save panel state", etc.

Here is some extra info:
- I am running MADDOG under FSX and Windows Vista
- I am running version 4.152 of FSUIPC (interesting to note that this add-on menu option works just fine)
- I have confirmed that all my FSX-related folders are owned by me, and that "full control" has been granted for all users
- I always choose "Run as administrator" when I run FSX

Can anyone offer suggestions/tips? Thanks!

- Bob

[EC-TLG]

Hi,

I have an interesting problem which is currently preventing me from continuing to fly the MADDOG sim.

The MADDOG menu options, found under the FSX "Add-ons" menu, although present, do not work. For example, if I select "Maddog - Ground Communication...", and hit enter, the menu just closes immediately. This behavior occurs for all MADDOG options - "Crew communication...", "Save panel state", etc.

Here is some extra info:
- I am running MADDOG under FSX and Windows Vista
- I am running version 4.152 of FSUIPC (interesting to note that this add-on menu option works just fine)
- I have confirmed that all my FSX-related folders are owned by me, and that "full control" has been granted for all users
- I always choose "Run as administrator" when I run FSX

Can anyone offer suggestions/tips? Thanks!

- Bob

It's because Windows Vista s***s , try Win XP SP2 better for fly the MADDOG.

[bob_r]

It's because Windows Vista s***s , try Win XP SP2 better for fly the MADDOG.

With the amount of trouble I have had since installing Vista, I have to agree with you. Sometimes I get so many errors I think that I have hardware problems, but from the sounds of it, it's just Vista.

I'm re-installing FSX and all related add-ons right now just to see if that will help. As for your suggestion of using XP instead, I was under the impression that FSX was designed to run better under Vista (when it works), performance-wise. Is this not the case?

Thanks for your reply.

- Bob
]

[bob_r]

I'm re-installing FSX and all related add-ons right now just to see if that will help. As for your suggestion of using XP instead, I was under the impression that FSX was designed to run better under Vista (when it works), performance-wise. Is this not the case?

An update on this....

I carefully re-installed everything (FSX + patch, FSX SDK + patch, MADDOG + patch) as the admin user, making sure to uninstall/delete everything FSX-related beforehand. Also, I made sure to check and re-check directory permissions as I went, ensuring that full access was granted for all users.

I'm now worse off than before - now I get no "Add-on" menu at all! I'm able to actually fly the MADDOG, I just have no menus available, for it or for any other add-on.

I found out how to create a SimConnect log file, since I understand thta SimConnect and the Add-on menu are related, and here is what it contains:

0.00000 SimConnect version 10.0.61242.0

4.04907 DLL Failed to load. Check for missing dependencies.
4.04912 DLL Load Failed: Error=-3 Path="D:\Flight Simulation\Microsoft Flight Simulator X\Modules\LeonardoSH.dll"
6.02457 Panels data export found and set to 20A819B8
6.93360 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.1.2.0"

Can somebody please help me out? I'd really like my Add-on menu back.

Thanks for any advice!

- Bob

[bob_r]

Can somebody please help me out? I'd really like my Add-on menu back.

Another update - I have my add-on menu back. Basically, I had to delete every registry entry that I could find related to SimConnect, plus a SimConnect.dll file that was present in C:\Windows\System32, prior to trying the re-install.

So, now I am where I was before. I have fresh installs of SimConnect.dll, but although the add-on menu is present, the MADDOG menu options simply close when selected.

Any suggestions appreciated.

Thanks.

- Bob

[VulcanB2]

I was under the impression that FSX was designed to run better under Vista (when it works), performance-wise. Is this not the case?

No, it isn't, and I'm still waiting to see if Trading Standards do anything about misleading advertising. Vista supports DX10, but it isn't available yet, so I don't know how MS can say this. I wonder how many people bought Vista based on that statement? It certainly won't be quicker on Vista - the same at best.

Best regards,
Vulcan.

This post has been edited by VulcanB2: 17/09/2007, 22:25

[bob_r]

I wonder how many people bought Vista based on that statement? It certainly won't be quicker on Vista - the same at best.

Interesting! Well, count me as one of those people - I bought Vista for just that reason. Yes, it certainly is tempting to switch back to XP now, but I'll try a little longer for a Vista solution first. I just don't want to go through all that re-installation unless it's absolutely necessary.

Thanks for the info. Cheers.

- Bob

[bob_r]

Yes, it certainly is tempting to switch back to XP now, but I'll try a little longer for a Vista solution first. I just don't want to go through all that re-installation unless it's absolutely necessary.

Just doing a 'bump' on this topic. Still looking for a solution to this issue. Anyone in tech support reading this?

My issue again is that when I select any "MADDOG" menu option from the "add-ons" menu, the menu simply closes with no action taken.

I'm running MADDOG 2006 in FSX/Vista.

Thanks for any help.

- Bob

[Scandi426]

Hi, my menu show but most of the items are greyed-out, so they dont work.
The only menu item working is the "PA/ Emergency Light Test"
(I have both ASX and ASG installed but tried not running them, but same result )

Perhaps stupid qstn, but do I need fsuipc to work the "addon-menu"?

Runnning FSX on XP(SP2)

regards
Scandi426

Yes, it certainly is tempting to switch back to XP now, but I'll try a little longer for a Vista solution first. I just don't want to go through all that re-installation unless it's absolutely necessary.

Just doing a 'bump' on this topic. Still looking for a solution to this issue. Anyone in tech support reading this?

My issue again is that when I select any "MADDOG" menu option from the "add-ons" menu, the menu simply closes with no action taken.

I'm running MADDOG 2006 in FSX/Vista.

Thanks for any help.

- Bob

This post has been edited by Scandi426: 02/10/2007, 10:00

[VulcanB2]

Hi,

No issues here with the MD in FS9 or FSX under XP.

There is a problem with FSX under Vista however - from another forum, here is a potential fix:

The disappearing Add-on menu issue seems to be connected to the ORDER of programs being loaded in FSX, but in some cases, it is tied to VISTA user access during the initial installation of the program.

Start with trying the solutions offered in this first post. Some users have added other ways they have fixed the problem.

PLEASE BACKUP THE DLL.XML FILE.

1. Open the dll.xml file with NOTEPAD.
XP: DLL.XML is located by default at C:\Documents and Settings\USERNAME\Application Data\Microsoft\FSX.
VISTA: C:\Users\username\AppData\Roaming\Microsoft\FSX\dll.xml
NOTE: USERNAME=your assigned username

The DLL.XML file will look something like this:

<?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>FSCopilot</Name>
<Disabled>False</Disabled>
<Path>Modules\FSCopilot.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>
<Launch.Addon>
<Name>FeelThere PIC737X Helper</Name>
<Disabled>False</Disabled>
<Path>FeelThere\B737\PIC737XH.dll</Path>
</Launch.Addon>
<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>
</SimBase.Document>

2. You will need to REARRANGE where the FSCopilot and FSUIPC sections are. This will mean you will have to COPY (CUT) and then PASTE the relevant sections to EITHER side of the Level-D 767 section.

3. HIGHLIGHT and CUT this section...

<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>

...and PASTE BEFORE the Level-D section:

<Launch.Addon>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>

It should look like this:

<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>

4. HIGHLIGHT and CUT this section...

<Launch.Addon>
<Name>FSCopilot</Name>
<Disabled>False</Disabled>
<Path>Modules\FSCopilot.dll</Path>
</Launch.Addon>

...and PASTE AFTER the Level-D section:

<Launch.Addon>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>

The last entires in the DLL.XML file should look like this (note that the final tag line </SimBase.Document> should be AFTER the FSCopilot section):

<Launch.Addon>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSCopilot</Name>
<Disabled>False</Disabled>
<Path>Modules\FSCopilot.dll</Path>
</Launch.Addon>

5. The completed file may look like this (depending on which add-ons you have installed):

<?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>
- <Launch.Addon>
<Name>FeelThere PIC737X Helper</Name>
<Disabled>False</Disabled>
<Path>FeelThere\B737\PIC737XH.dll</Path>
</Launch.Addon>
- <Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
- <Launch.Addon>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>
- <Launch.Addon>
<Name>FSCopilot</Name>
<Disabled>False</Disabled>
<Path>Modules\FSCopilot.dll</Path>
</Launch.Addon>
</SimBase.Document>

6. SAVE the DLL.XML file. Close NOTEPAD.

Try this for the Maddog in Vista. No guarantees. Substitute Level-D for MD2006.

Best regards,
Vulcan.

This post has been edited by VulcanB2: 02/10/2007, 19:14

[Scandi426]

Hi, Vulcan.

Only have myself to blame - did not notice that the User Manual clearly states you need to switch on the INT mic in the Audio Panel, otherwise Ground Communication is not operational. So now this part work, but.. I cant get the Crew Communication menu items to work. What am I missing?

kind regards
Scandi426

EDIT: Works now. My fault - again It seems you will have to do the PA/Emergency Light test procedure before the crew dears to enter the cabin ;-)
Once again: realistic. Im really falling in love with this add-on!

This post has been edited by Scandi426: 08/10/2007, 9:07