No add_on menu...

[Alex_Cha]

Hi Pete.

I used FSUIPC 4.60a. It worked perfect.

Today I installed new version of FSUIPC(4.70) and run fsx.. but there is no add_on menu (FSUIPC 4.70 is not working) and also WideServer doesnt work.

Therefore I deleted 4.70 and reInstall 4.60a. It works well.

I have already check dll.xml, FSX.cfg. These files are OK.

this is FSUIPC4 Install.log

Installer for FSUIPC4.DLL version 4.70a

Looking in registry for FSX install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"AppPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

AppPath="C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61355.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.600 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Alex.Innosim\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\Alex.Innosim\AppData\Roaming"

Found FSX.CFG in "C:\Users\Alex.Innosim\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Users\ALEX~1~INN\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

===========================================================

All installer tasks completed okay!

Registration check for FSUIPC4 and WideFS was successful! (result code 00)

*************** End of Install Log ***************

FSUIPC4.log is old file(I think FSUIPC 4.70 didnt work, so this file was not changed)

how can I solve this problem..

best regards

Alex.

[Pete Dowson]

I used FSUIPC 4.60a. It worked perfect.

Today I installed new version of FSUIPC(4.70) and run fsx.. but there is no add_on menu (FSUIPC 4.70 is not working) and also WideServer doesnt work.

Therefore I deleted 4.70 and reInstall 4.60a. It works well.

I have already check dll.xml, FSX.cfg. These files are OK.

...

FSUIPC4.log is old file(I think FSUIPC 4.70 didnt work, so this file was not changed)

How strange. I can think of possible reasons for 4.70 loading when 4.60a might not, but not the other way round.

I'd need to see the DLL.XML file in any case, though I know you say you've checked it. When you changed back to 4.60 did you reinstall 4.60 or merely put back a saved copy of the DLL?

Can you make a SimConnect log for me to look at, please? You'll find instructions here: Logging SimConnect

Regards

Pete

[KENNETHHILL]

I have the same exact problem after installing 4.70a.

[guenseli]

I have had the same issue yesterday:

installed 4.70 just over my existing 4.6X (latest and last incremental update)

First flights where good, everything fine - FSX started and closed several times, than suddenly after a new start FSUIPC was gone.

Next time I was restarting FSX FSUIPC was there again, but then after that it was gone "forever".

I "rearanged" the DLL.XML, deleted the "[trusted] section in the FSX.cfg, copied in the FSUIPC part from an old backup - without effort.

What helped was to copy the FSUIPC code at the first place of the Dll.xml.

Since then it is working without any problems....

Günter

edit: system: FSX with acceleration

Win7 with Admin rights and UAC off.

[Pete Dowson]

What helped was to copy the FSUIPC code at the first place of the Dll.xml.

Since then it is working without any problems....

How odd.

I need to see the DLL.XML files of those with problems to see what possible other add-on is suddenly clashing with FSUIPC during the SimConnect loading sequence. I also could do with some SimConnect log files showing the problem. I put a link to details of how to get a log in my first reply here.

There's been no recent change in FSUIPC which could possibly have such an odd result, so I could also do with knowing if all those with this problem were replacing 4.60 or one of the later interim versions (there have been many in the year since 4.60a was released). If an interim I'd like to know which one, please. For instance, Guenseli says:

just over my existing 4.6X (latest and last incremental update)

Would that have been 4.669?

If merely rearranging the entries in the DLL.XML so that FSUIPC loads first fixes it, I'd most certainly like to know what the other entries are!

Regards

Pete

[Alex_Cha]

I have had the same issue yesterday:

installed 4.70 just over my existing 4.6X (latest and last incremental update)

First flights where good, everything fine - FSX started and closed several times, than suddenly after a new start FSUIPC was gone.

Next time I was restarting FSX FSUIPC was there again, but then after that it was gone "forever".

I "rearanged" the DLL.XML, deleted the "[trusted] section in the FSX.cfg, copied in the FSUIPC part from an old backup - without effort.

What helped was to copy the FSUIPC code at the first place of the Dll.xml.

Since then it is working without any problems....

Günter

edit: system: FSX with acceleration

Win7 with Admin rights and UAC off.

Yesterday, I deleted [Trusted] section in FSX.cfg and delete FSUIPC4.*(4.60a) in modules folder. Next reinstall 4.70. and now (after reboot) FSUIPC4 works well....

Strange -_-;;;;

anyway FSUIPC4 works well..

I will test more and report.

thanks everyone

[guenseli]

<?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>FSUIPC 4</Name>
		<Disabled>False</Disabled>
		<Path>Modules\FSUIPC4.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>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>
  <Launch.Addon>
		<Name>VistaMare Core</Name>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Path>VistaMare\ViMaCoreX.dll</Path>
	</Launch.Addon>
  <Launch.Addon>
		<Name>FSLOptions</Name>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Path>FSLabs\DLLs\FSLOptions.dll</Path>
	</Launch.Addon>
  <Launch.Addon>
		<Name>FSLEvents</Name>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Path>FSLabs\DLLs\FSLEvents.dll</Path>
	</Launch.Addon>
  <Launch.Addon>
		<Name>FSLSounds</Name>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Path>FSLabs\DLLs\FSLSounds.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>Kokpit</Name>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Path>SimObjects\Airplanes\HUGHES_H1B\panel\Cockpit_Sound.dll</Path>
		<DllStartName>module_init</DllStartName>
		<DllStopName>module_deinit</DllStopName>
	</Launch.Addon>

</SimBase.Document>

just for your interest: that is the old simconnect.ini.

I have changed this to your suggestions in the simconnect logging thread.

[SimConnect]
level=off
console=0
;OutputDebugString=0
;file=c:\SimConnect%03u.log
;file_next_index=1
;RedirectStdOutToConsole=0

I will send you a mail with the simconnect.log file immediatelly...

I have had Active sky Evolution activated and started FSX for one time

and a sidenote:

if you have a german OS you will have another folder

"Flight Simulator X-Dateien" beside the english Flight Simulator X Files"

The modified simconnect.ini have to be placed in the german "Dateien" folder.

Maybe in other languages theres a similar difference...

Günter

[Pete Dowson]

just for your interest: that is the old simconnect.ini.

Er, sorry. I don't understand. How many "simconnect.ini"s do you find?

I have changed this to your suggestions in the simconnect logging thread.

The thread in the FAQ? Sorry, I am still confused.

Your new SimConnect.ini is just:

[SimConnect]
level=off
console=0

since you commented a load of lines outt with ';'

I will send you a mail with the simconnect.log file immediatelly...

Thank you. I really need one from a failed load of FSUIPC4, to see why SimConnect didn't load FSUIPC4. Your log is for a correct load by the look of it.

There's a large number of DLLs being loaded by SimConnect. Can you confirm they all work okay? I can't see why FSUIPC4 would load if it is first in the list but not last. That's a bit weird.

1.46240 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.7.0.0"

1.50131 DLL Loaded: Path="PMDG\DLLs\PMDGOptions.dll" Version="10.0.61355.62"

1.50889 DLL Loaded: Path="PMDG\DLLs\PMDGEvents.dll" Version="10.0.61355.62"

1.52314 DLL Loaded: Path="PMDG\DLLs\PMDGSounds.dll" Version="10.0.61355.62"

1.52587 DLL Loaded: Path="VistaMare\ViMaCoreX.dll" Version="10.0.0.13"

1.59052 DLL Loaded: Path="FSLabs\DLLs\FSLOptions.dll" Version="10.0.61355.65"

1.60098 DLL Loaded: Path="FSLabs\DLLs\FSLEvents.dll" Version="10.0.61355.65"

1.60745 DLL Loaded: Path="FSLabs\DLLs\FSLSounds.dll" Version="10.0.61355.65"

1.77129 DLL Loaded: Path="Modules\LVLD.dll" Version="1.4.2.1"

1.78565 DLL Loaded: Path="F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\LeonardoSH.dll" Version="<Unbekannt>"

1.78651 DLL Loaded: Path="SimObjects\Airplanes\HUGHES_H1B\panel\Cockpit_Sound.dll" Version="<Unbekannt>"

The main difference between 4.667 and 4.669 (= 4.70) is the re-compilation using MSVC 2010. I'm wondering if there's a DLL configuration setting which is stopping FSUIPC loading if a previously loaded DLL occupies its desired space (6100xxxx). Was your previous "latest update" actually 4.667 rather than 4.669 by any chance?

For now I'll do some experiments to see if there is such a setting at work ...

Regards

Pete

[Pete Dowson]

For now I'll do some experiments to see if there is such a setting at work ...

I found one setting in the Linker which may, possibly, be wrong (/FIXED). That may make it want a fixed place in memory and so not load if that space is already occupied. I can't prove it easily here because I simply can't get that space occupied with the DLLs I have available for SimConnect to load.

So, could you do some tests for me, please?

First, please edit the DLL.XML again to make FSUIPC4.DLL load last. Check that this again gives you problems. THEN, leaving DLL.XML as it then is, with FSUIPC4 loading last, please download and install FSUIPC 4.70b into the FSX Modules folder, from this link:

FSUIPC 4.70b

If that then works well, I will know I've fixed it and will replace the full 4.70a installer with a 4.70b version.

Thanks!

Pete

[guenseli]

First, I try to answer your question... hopefully easin your confusion ;-)

Er, sorry. I don't understand. How many "simconnect.ini"s do you find?

I have one found in the "Files" folder, but no one in the german "Dateien" folder.

And I realised, that an ini file in the english folder doesn't do anything!

Of course I used this simconnect.ini from your FAQ "Logging Simconnect"

I have just posted the code of the ini I found for your interest. I don't know from where and and why it is there.

But ok, as it is useless, we can forget about it...

Was your previous "latest update" actually 4.667 rather than 4.669 by any chance?

indeed you are right: I couldn't say for sure which version it was... sorry.

Could be 4.667 also.. maybe I missed the 4.699 but couldn't say it...

I have now changed the FSUIPC entry in the Dll.xml to the last position, but FSX/FSUIPC is working as it should.

FSUIPC is working and in the menu...

I have NOT used your 4.70b till now!

And yes, the simconnect.log is from a proper loading of FSUIPC and all Dll's are loaded right in the sim.

Since the last failures I haven't had a issue with FSUIPC... after changing FSUIPC position in the Dll.xml.

But obvisously it was maybe just a coincidence...?

What should I do now?

Should I let run the simconnect log the next days (hoping I could catch a failure)? (this would be a very big log file then in the end or not?)

Should I install the 4.70b anyway??

[Pete Dowson]

I have one found in the "Files" folder, but no one in the german "Dateien" folder.

And I realised, that an ini file in the english folder doesn't do anything!

Of course the "Flight simulator X Files" folder in the user's "My documents" will be translated for other language versions of FS (as will "My documents" for other Windows languages I assume). Perhaps I should say "the folder where FS saves its plans and flights", but I thought folks would understand that. I'll add such a comment now.

I have now changed the FSUIPC entry in the Dll.xml to the last position, but FSX/FSUIPC is working as it should.

FSUIPC is working and in the menu...

Hmm. Strange. I still suspect it is a problem with loading addresses for multiple DLLs. I think i will issue 4.70b in any case.

Should I install the 4.70b anyway??

Yes, just do that. Please keep FSUIPC4.DLL in its last position in the XML file, as that is where is will normally go after running the Installer.

Thanks!

Pete

[guenseli]

Many thanks, Pete!

should I let the simconnect.log still be running the next days till we maybe get another failure???

[Pete Dowson]

should I let the simconnect.log still be running the next days till we maybe get another failure???

If you wish -- it might turn out useful. I do have it on all the time, even in my cockpit. I don't think it noticeably affects performance.

Regards

Pete