Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I have a fully registered FSUIPC and Wide client. I had them working properly but for some reason they lost connection. I am running both computers with Windows 7. Wide Client log reads as follows: -

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 16/03/10, Time 15:23:14.190: Client name is MAIN-PC

297 Attempting to connect now

1297 Trying to locate server: Need details from Server Broadcast

1297 Failed to connect: waiting to try again

3312 Attempting to connect now

67578 Trying to locate server: Need details from Server Broadcast

2184625 ****** End of session performance summary ******

2184625 Total time connected = 0 seconds

2184625 Reception maximum: 0 frames/sec, 0 bytes/sec

2184625 Transmission maximum: 0 frames/sec, 0 bytes/sec

2184625 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

2184625 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

And the FSUIPC log reads: -

********* FSUIPC4, Version 4.60a by Pete Dowson *********

Reading options from "J:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Robert Ross"

User Addr="rross@vernonbc.ca"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

141 System time = 16/03/2010 15:47:32

172 FLT UNC path = "\\ROBROSS-PC\Users\Rob Ross\Documents\Flight Simulator X Files\"

172 FS UNC path = "\\ROBROSS-PC\J\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

906 LogOptions=00000000 00000001

906 SimConnect_Open succeeded: waiting to check version okay

5797 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

5797 Initialising SimConnect data requests now

5797 FSUIPC Menu entry added

5906 \\ROBROSS-PC\Users\Rob Ross\Documents\Flight Simulator X Files\KCTM.FLT

5906 \\ROBROSS-PC\J\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR

132859 Sim stopped: average frame rate for last 33 secs = 11.3 fps

727875 Sim stopped: average frame rate for last 433 secs = 7.6 fps

734906 System time = 16/03/2010 15:59:47

734906 *** FSUIPC log file being closed

Average frame rate for running time of 466 secs = 7.9 fps

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

Any help would be appreciated.

Rob

Posted

As far as I can tell. Not listed on Server Computer but would it be as FSUIPC not a program file? Is listed on client computer"FS Eliminator for FSUIPC client applications" .

Posted
I have a fully registered FSUIPC and Wide client. I had them working properly but for some reason they lost connection. I am running both computers with Windows 7. Wide Client log reads as follows:

...

67578 Trying to locate server: Need details from Server Broadcast

As it says, it isn't seeing the Broadcasts from the Server which tell it where to go. That's probably because you have the two PCs with different Workgroup names. Please check the WideFS User guide about this. If you don't want to match workgroup names you must specify both the Server name (or IP address) and the Protocol in the WideClient INI file, else it cannot know where to connect.

The WideClient log is only half of the story in any case. There might be more clues in the WideServer log which is in the FSX Modules folder.

And the FSUIPC log reads: -

The FSUIPC log isn't relevant.

Regards

Pete

Posted

Same workgroup for both computers.

Wide server log: -

********* FSUIPC4, Version 4.60a by Pete Dowson *********

Reading options from "J:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Robert Ross"

User Addr="rross@vernonbc.ca"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

125 System time = 16/03/2010 16:53:55

125 FLT UNC path = "\\ROBROSS-PC\Users\Rob Ross\Documents\Flight Simulator X Files\"

125 FS UNC path = "\\ROBROSS-PC\J\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

860 LogOptions=00000000 00000001

860 SimConnect_Open succeeded: waiting to check version okay

5250 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

5250 Initialising SimConnect data requests now

5250 FSUIPC Menu entry added

5344 \\ROBROSS-PC\Users\Rob Ross\Documents\Flight Simulator X Files\KCTM.FLT

5344 \\ROBROSS-PC\J\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR

303250 Sim stopped: average frame rate for last 135 secs = 9.1 fps

314954 System time = 16/03/2010 16:59:10

314954 *** FSUIPC log file being closed

Average frame rate for running time of 146 secs = 9.3 fps

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

Posted
Same workgroup for both computers.

But the broadcast isn't being seen. I don't know anything other than workgroup difference which can stop broadcasts.

Wide server log: -

********* FSUIPC4, Version 4.60a by Pete Dowson *********

No, that's the FSUIPC4 log again!

Did you try adding the ServerName and Protocol to the WideClient.INI file as I suggested, and as documented for this type of problem?

Pete

Posted

Yes I did attached is the WideClient.ini file

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=480,86,246,66

ServerName=RobRoss-PC

Protocol=TCP

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

Posted
Yes I did attached is the WideClient.ini file

Still you don't show the WideServer Log file? Why not? It shows the other half of the story. I've asked three times now!

I am away now till next Monday.

Regards

Pete

Posted

Sorry thought I had: -

********* WideServer.DLL Log [version 7.60a] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 16/03/10, Time 19:49:12.796: Server name is ROBROSS-PC

Posted
Sorry thought I had: -

********* WideServer.DLL Log [version 7.60a] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 16/03/10, Time 19:49:12.796: Server name is ROBROSS-PC

Where's the rest?

Pete

Posted

That is all there was. I have since re-installed everything including Windows 7 and everything works. I wounder if the original install of Windows was corrupt as I had several other issues.

Rob ross

Posted
That is all there was.

Seems that FSX must have crashed soon after loading then. But that certainly wasn't so when the FSUIP4 log was made, ass that ends after at least 5 minutes of operation with a normal closure:

314954 *** FSUIPC log file being closed

Average frame rate for running time of 146 secs = 9.3 fps

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

I have since re-installed everything including Windows 7 and everything works. I wounder if the original install of Windows was corrupt as I had several other issues.

Rob ross

Maybe. Glad everything is okay now.

Pete

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