Jump to content

done everything / no Addon in menu ?! / gets worse every try


Recommended Posts

I did by the book.

simconnect works when "AI traffic.exe" slave notebook test: "Connected .." says finds objects

AxtiveSkyX works via Notebook when fsuipc.dll is renamed fsuipc.dll.XXX and CRASHES with a started fsuips.dll

FSUIPC4 Install.log says all is wonderfull

Firewalls OFF

No Virus prog running

I can remember after instaling FSCopilot / there was an addon and fscopilot working

several installs of 4.11 but Addon in menu is gone

********* FSUIPC4, Version 4.11 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

Running inside FSX on Windows Vista (SimConnect SP1 May07)

Module base=61000000

DebugStatus=0

78 System time = 18:21:02

78 FLT UNC path = "\\DUAL\wd200\TEKST\Flight Simulator X Files\"

78 FS UNC path = "\\DUAL\FSX\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

749 N.B. Axis Intercepts are disabled!

749 LogOptions=00000001

858 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

15912 **** Retrying SimConnect connection****

16006 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

31028 **** Retrying SimConnect connection****

31122 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

46129 **** Retrying SimConnect connection****

46223 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

61230 **** Retrying SimConnect connection****

61339 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

76378 **** Retrying SimConnect connection****

76487 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

91510 **** Retrying SimConnect connection****

91604 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

106611 **** Retrying SimConnect connection****

106720 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

121774 **** Retrying SimConnect connection****

etc etc

just purchased fsuipc/widefs upgrade

I cannot enter Registration because there is no ADDON in the menu

???

THX

MT

have a double SimConnect.xml entry

<?xml version="1.0" encoding="Windows-1252"?>

SimConnect

SimConnect.xml

False

False

IPv4

global

192.168.1.9

64

8002

4096

False

False

IPv4

local

127.0.0.1

64

4096

False

this is my dll.xml

<?xml version="1.0" encoding="Windows-1252"?>

Launch

dll.xml

False

False

FSCopilot

False

Modules\FSCopilot.dll

Object Placement Tool

True

False

..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll

Traffic Toolbox

True

False

..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll

Visual Effects Tool

True

False

..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll

FSUIPC 4

False

Modules\FSUIPC4.dll

and like I stated above ASX and AItraffic run OK

FSX installed on Vista Ultimate Core 2 Duo 6600

Notebook T5500 with Vista Premium

network running no problems

using only Windows Firewall and disabled for tests

Link to comment
Share on other sites

simconnect works when "AI traffic.exe" slave notebook test: "Connected .." says finds objects

But does it work on the FSX PC? FSUIPC runs on the FSX PC, inside FSX. It needs SimConnect working there. The fact that it is working on a separate Client PC is not really all that relevant.

AxtiveSkyX works via Notebook when fsuipc.dll is renamed fsuipc.dll.XXX and CRASHES with a started fsuips.dll

But I expect ASX would not work on the FSX PC, like FSUIPC.

FSUIPC4 Install.log says all is wonderfull

Yes, the installation is fineI can see that from later details.

Firewalls OFF

No Virus prog running

Well, it looks like something is blocking SimConnect locally, on the FSX PC.

several installs of 4.11 but Addon in menu is gone

Once an install works okay there's really little benefit of running it again, unless something else you have run messes one of the XML files up. More about the latter below.

The FSUIPC Log simply shows that SimConnect won't respond correctly:

858 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

This is normally down to a block by a security program -- even if they are disabled, some security programs still place hooks into the TCP/IP protocol path.

I cannot enter Registration because there is no ADDON in the menu

Since FSUIPC cannot operate in any case, it follows that whether you enter a registration or not is irrelevant. It won't do anything because it cannot. It isn't being allowed to.

have a double SimConnect.xml entry

Yes, that should be okay. But just to test, try renaming the SimConnect.XML so it doesn't get used. Maybe there's another SimConnect bug we need to report.

If it still doesn't work, please obtain a SimConnect log, as described in the FSX Help announcement above, and I will try to get help from Microsoft.

Note that I am running ASX on a separate PC along with FSUIPC4 on FSX with no trouble, but I am using XP Pro on both, with no firewall enable and no security programs even installed, and also I have a simpler "Local" section of the SimConnect.xml file, thus:

False

Auto

local

Maybe, if it works without the SimConnect.xml at all, you could try changing yours to have this as the Local section. (It is what the FSUIPC4 installer would add if it found no "local" section).

Regards

Pete

Link to comment
Share on other sites

Maybe, if it works without the SimConnect.xml at all, you could try changing yours to have this as the Local section. (It is what the FSUIPC4 installer would add if it found no "local" section).

hi

could register fsuipc and widefs by Deleting SimConnect.xml and ADDON in menu showed up

FSX PC:

no SimConnect.xml then

fsuipc widefs work, ASX not simconnect, ASX local only

remote Widefs will connect (not for ASX)

ADDON in menu

as soon as:

FSX PC:

simconnect.xml 'any version' with or without , detailed or simple

then:

07219 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

ADDON disappears ALSO for other modules (FSCopilot)

FSX PC:

no FSUIPC.dll

simconnect works flawless, ASX remote, AI traffic tests OK

??

MT

Asus P5N32-E Plus SLI, Nvidia 8800GTS640, E6600, 2GB ram, Vista Ultimate all updates

adendum:

oddity:

a working simconnect.xml connection (without FSuipc)

makes my ADDON menu disappear ALSO for the 1 other addon FSCopilot

so it must be my simconnect setup, that only works Without Addons / disables them (am i thinking right here?)

??

I tried / have reinstalled SDK, but cannot delete the /winsxs/xxx subdirectory Even, when I login Save Mode.

help

Link to comment
Share on other sites

oddity:

a working simconnect.xml connection (without FSuipc)

makes my ADDON menu disappear ALSO for the 1 other addon FSCopilot

so it must be my simconnect setup

SimConnect seems okay. If that was wrong you'd not get anything working correctly.

You haven't said whether you tried the simplified / different SimConnect.xml I suggested. I am not using a SimConnect.xml which looks like yours -- I'm not sure where you got yours from. Try deleting the local section and substituting the one I suggested.

Pete

Link to comment
Share on other sites

[quote="Pete Dowson

False

Auto

local

did try

have tried dozen versions, differnt port, auto protocol

change, start FSX, view log

change again, FSX, view log, etc

Why would simconnect fail not only fsuipc, but also FSCopilot.

Reading forums now, and MS did a horendiously awfull job with this simconnect.

They should have hired you :)

Perhaps XP works better, but thats rather a defeat towards bad programming

Anyway, I cannot delete winsxs subdirectory, even in Safe Mode. So How would I go about something like 'repairing' Simconnect? Since appearantly it doesnt interface with the modules, prevents them loading?

thx

mt

Link to comment
Share on other sites

YIPPIE

found it

I have FSX installed on a partition FSX with drive number Y

and the paths in dll.xml are wrong

MS SDK is expecting FSX on C-drive (WHY?)

finding the \modules folder appears no problem

not finding the SDK (demo?) dll's crashes the whole lot

and all generated automaticaly

really clever :twisted:

anyway, both ASX work now on laptop with simconnect, and Flightsim Commander with Widefs

for anyone interested

here's my dll.xml with full windows long path names written, replacing the ..\etc .. and with FSCopilot.dll also in the \modules:

<?xml version="1.0" encoding="Windows-1252"?>

Launch

dll.xml

False

False

FSCopilot

False

Modules\FSCopilot.dll

Object Placement Tool

True

False

c:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll

Traffic Toolbox

True

False

c:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll

Visual Effects Tool

True

False

c:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll

FSUIPC 4

False

Modules\FSUIPC4.dll

going to bed now :) :D

Link to comment
Share on other sites

MS SDK is expecting FSX on C-drive (WHY?)

I think the SDK installer installs the SDK in a fixed standard place. There's a utility someplace in the package which you run to fix the paths.

finding the \modules folder appears no problem

not finding the SDK (demo?) dll's crashes the whole lot

The Modules folder is inside the FSX path, so that part can be omitted -- FSX assumes that bit if a complete path isn't given.

Strange though. Having the path wrong shouldn't have made SimConnect fail locally, it should simply result in the incorrectly pathed modules not being loaded. They are optional in any case.

What is much more likely is that the paths were/are valid, and point to older versions of the Modules, from the original FSX release. But then I thought those wouldl actually crash FSX if loaded.

anyway, both ASX work now on laptop with simconnect, and Flightsim Commander with Widefs

So when you were testing with and without FSUIPC4, you weren't doing it the 'easy' way, renaming or moving the DLL itself, but by doing something with the DLL.XML file?

Anyway, glad you got it fixed in the end.

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.