rdmann
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by rdmann
-
-
Pete, I've send a note to tell fs, as you suggested with a description of the problem, so will see what they respond with. I need FSUIPC because I run other apps (ActiveSky, etc.) on a networked pc through WideFS (registered).
Will see what happens with that route.
Regards
Rod
-
Jumping in on this discussion. I've been dealing with an issue that I simply could not resolve. When alt/tab out of FSX to use another application (didn't make any difference which one), FSX would freeze on me and I couldn't get back into it, even though it was still running (even could here the sound). Looking at the task mgr in WinXP I saw the #1 cpu was running at 100% and consuming all resources. (I'm running a CoreDuo E6600 with 2 Gig of DDR2)
Anyway, I reinstalled FSX completely and then proceeded to figure out what could be causing the freeze up. Nothing did until I reinstalled FSUIPC. From that point I got the freeze up, exactly as described above. I happened to see this thread and thought, what if I removed the fsuipc.dll? I did and then started FSX again. No problem with alt/tab. So, something is going on and it may be the same SimConnect issue being discussed here. I don't know, but thought I'd pass on my experience.
Pete, maybe the update you are planning tonight will address this issue, but it may be a SimConnect issue as well?
Cheers.
Rod
-
I didn't realize I needed FSUIPC registered to use it, if the product I'm using it with is registered. I saw the message but since I was using it with ActiveSky 6.5 I assumed registering FSUIPC again was not required, since the folks who developed AS6 pay a fee. Obviously I was mistaken.
Frankly, while I really appreciate the quick reply Pete, I think your reply was a bit abrupt. I did read the log. I did read the manual, but before I started paying for registrations I thought I should make sure what I was doing (or not doing) was causing the problem. WideFS was where I expected I was having the problem, not both FSUIPC and WideFS.
Just to be clear I have no problem purchasing registrations, as I did for versions 3, since I think your product is great. I am disappointed that your reply suggests I should have simply figured it out. If I knew the answer I wouldn't have emailed the request.
The user guide says in the Intro- "This aspect of FSUIPC4 is available to applications irrespective of the user's status. In other words, user purchase and registriton of FSUIPC4 has no bearing on the local FSX PC support of FSUIPC-interfacing programs (support for networked clients of WideFS does however still need purchase of the WidefS key).
The above doesn't say I needed to purchase another registration for FSUIPC for a networked application, only WideFS. Nothwithstanding the above it appears from your advice above I need to register both FSUIPC4 and WideFS to get things working on a networked client.
I did not with versions 3 and do not with versions 4 have any issue with paying for what I need. It isn't a money thing at all. But I did want to be clear on this in relation to what I was experiencing. That was why I emailed you.
Absent follow up from you I will therefore purchase registrations for both FSUIPC 4 and WideFS and that from what you say will resolve my connection problem?
Thank you
Rod
-
I have a good connection using WideFS (6.7)and FSUIPC 3.7 with FS9, but cannot get any connection with FSX. ActiveSky 6.5 works great with FS9 but not then with FSX.
I've installed FSUIPC4 on the server machine and FSX shows a modules folder and a fsuipc.dll, etc. Do I need a new registered version of WideFS? I thought not (I have both FSUIPC 3 and WideFS 3 registered. But have not yet registered the new FSUIPC4 or WideFS.
Follows are the logs that I think are important
I'm sure its something simple, but I can't figure it out.
Thanks Pete
Rod Mann
FSUIPC log
********* FSUIPC4, Version 4.01 by Pete Dowson *********
User Name=""
User Addr=""
FSUIPC not user registered
WIDEFS not user registered, or expired
Running inside FSX
Module base=61000000
LogOptions=00000001
DebugStatus=0
141 System time = 13:46:24
141 FLT UNC path = "\\PRIMARY\Documents and Settings\Rod\My Documents\Flight Simulator X Files\"
141 FS UNC path = "\\PRIMARY\Data (D) Primary\FSX\"
17954 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)
17954 C:\Documents and Settings\Rod\My Documents\Flight Simulator X Files\Victoria Default.FLT
17954 D:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR
22266 System time = 13:46:46, FSX time = 13:46:41 (20:46Z)
109157 Advanced Weather Interface Enabled
2258141 System time = 14:24:02, FSX time = 13:21:38 (21:21Z)
2258141 *** FSUIPC log file being closed
Memory managed: 3092 Allocs, 3092 Freed
********* FSUIPC Log file closed ***********
FSUIPC.ini
[General]
History=9KK6BXS2T0E40JXSMD7SS
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
WeatherReadSeconds=1
[WideServer]
WideFSenabled=Yes
[GPSout]
Port=
Speed=4800
Interval=1000
PosTo6Decimal=Yes
Sentences=
WideClient.ini
; PLEASE SEE WideFS documentation for parameter details
; =====================================================
[Config]
Port=8002
Window=32000,32000,160,34
Visible=min
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
Protocol=UDP
ServerName=Primary
; -----------------------------------------------
[user]
Log=Errors+
; ===============================================
********* WideClient Log [version 6.70] Class=FS98MAIN *********
Date (dmy): 21/10/06, Time 14:07:48.906: Client name is SECONDARY
187 Attempting to connect now
187 Trying UDP/IP host "Primary" port 8002 ...
187Okay, IP Address = 192.168.0.103
187 UDP connectionless mode set up okay!
5187 New Client Application: "ASv6" (Id=4004)
36515 Timed out response: connection assumed lost!
36515 Ready to try connection again
36578 Timed out response: connection assumed lost!
37515 Attempting to connect now
37515 UDP connectionless mode set up okay!
55703 Timed out response: connection assumed lost!
55703 Ready to try connection again
55765 Timed out response: connection assumed lost!
56703 Attempting to connect now
56703 UDP connectionless mode set up okay!
74828 Timed out response: connection assumed lost!
74828 Ready to try connection again
74890 Timed out response: connection assumed lost!
75843 Attempting to connect now
75843 Trying UDP/IP host "Primary" port 8002 ...
75843Okay, IP Address = 192.168.0.103
75843 UDP connectionless mode set up okay!
93968 Timed out response: connection assumed lost!
93968 Ready to try connection again
94031 Timed out response: connection assumed lost!
94968 Attempting to connect now
94968 UDP connectionless mode set up okay!
113343 Timed out response: connection assumed lost!
113343 Ready to try connection again
113406 Timed out response: connection assumed lost!
114343 Attempting to connect now
114343 UDP connectionless mode set up okay!
132718 Timed out response: connection assumed lost!
132718 Ready to try connection again
132781 Timed out response: connection assumed lost!
133718 Attempting to connect now
133718 UDP connectionless mode set up okay!
152093 Timed out response: connection assumed lost!
152093 Ready to try connection again
152156 Timed out response: connection assumed lost!
153093 Attempting to connect now
153093 Trying UDP/IP host "Primary" port 8002 ...
153093Okay, IP Address = 192.168.0.103
153093 UDP connectionless mode set up okay!
171422 Timed out response: connection assumed lost!
171422 Ready to try connection again
171484 Timed out response: connection assumed lost!
172422 Attempting to connect now
172422 UDP connectionless mode set up okay!
190531 Timed out response: connection assumed lost!
190531 Ready to try connection again
190593 Timed out response: connection assumed lost!
191531 Attempting to connect now
191531 UDP connectionless mode set up okay!
192828 ****** End of session performance summary ******
192828 Total time connected = 0 seconds
192828 Reception maximum: 0 frames/sec, 0 bytes/sec
192828 Transmission maximum: 0 frames/sec, 0 bytes/sec
192828 Max receive buffer = 0, Max send depth = 1, Send frames lost = 0
192828 **************** Individual client application activity ****************
192828 Client 4004 requests: 40 (Ave 40/sec), Data: 2160 bytes (2160/sec), Average 54 bytes/Process
192828 ********* Log file closed (Buffers: MaxUsed 2, Alloc 476 Freed 476 Refused 0) *********
WideServer.ini
; PLEASE SEE the documentation for parameter details
; ==================================================
[Config]
Port=8002
ServerName=FlightSim and Imaging
; -----------------------------------------------
[user]
Log=Errors+
; ===============================================
-
There is one thing I've accomplished today, confusing everyone!!
Pete, it was a matter of terminology confusion on my part and once I read your post and realized the computer that I called "server" and the one client, were for purposes of FS9 and WideFS, totally reversed, for the reasons you mentioned. As soon as I figured that out, I walked myself back through the install process and ensured I had computers named appropriately and pointed to in the ini files.
Problem solved!!
It had nothing to do with the router!
Thanks for your patience.
Rod
-
Pete, I've posted in the FlightSim forum, but also wanted to follow up with you here too. I'm not sure its' my router/firewall that is the problem, and wanted to post my ini files here just to ensure they are properly set up. Here is how my ini's are set up right now:
My ini files on the server side (where WideFS is installed) are as follows:
Wideclient ini
Port=8002
Window=43,44,886,589
Visible=Yes
UseTCPIP=Yes
ServerName=Base.
; -----------------------------------------------
Log=Errors+
Wideserver ini
Port=8002
UseTCPIP=Yes
ServerName=Base.
; -----------------------------------------------
Log=Errors+
On the client side (where FS9 runs), my
Wideserver ini
Port=8002
UseTCPIP=Yes
ServerName=Base.
I've got wideserver.dll and wideserver.ini on FS9 in the modules folder and, on the server side I have a folder for WideClient, with wideclient.exe; wideclient.ini; wideserver.dll and wideserver.ini
As far as I can tell, this is as per the installation instructions. Does all this look ok? Anything else from a WideFS point of view to look at?
-
Pete, it may be my router. As I said, I'm new to the whole networking thing and I will check out the firewall in my router and see if that is where the solution lies (it's a DLink DI-604). I didn't really understand what the log file was saying, so knowing it relates to the server refusing to communicate offers me some clues.
thanks, and I will check with Katy too.
Any others who have experience with routers, input much appreciated.
thx.
Rod Mann
-
I've checked forum messages and read the manual with WideFS, but still stumped.
I've just set up a network (two computer, running Windows XP Home). Using FS9 on one computer and WideFS and AS2004 on other. Not sure if my problem is a WideFS one or AS2004 or both, so my apologies in advance. I don't think WideFS is connecting and I know AS2004 cannot connect to FS (it says so!).
Here is my log file:
********* WideClient.DLL Log [version 6.101] Class=FS98MAIN *********
Date (dmy): 16/01/04, Time 11:48:17.010: Client name is BASE
341 Attempting to connect now
361 Trying TCP/IP host "Base." ...
361Okay, IP Address = 192.168.0.100
1382 Error on client pre-Connection Select() [Error=10061] Connection refused
1392 Ready to try connection again
1412 Attempting to connect now
20259 Reception maximum achieved: 0 frames/sec, 0 bytes/sec
20259 Max receive buffer = 0, Max send depth = 0
20259 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********
Any help is appreciated, and if more info needed I'd be pleased to provide it.
Cheers
Rod Mann
memory problem caused by FSUIPC 4
in FSUIPC Support Pete Dowson Modules
Posted
Pete, sorry another follow up. Updated FSUIPC to latest (appreciate you didn't think this would resolve issue). I had same problem but I did notice one thing I had forgotten about in earlier email. I got FSX into a window mode (still frozen however), and the title bar said (and it said this before)-"Flight Simulator X-Wideserver-waiting for client". Not sure if this helps figure this out, but I will also pass on to tell fs.
thanks
Rod