Results 1 to 8 of 8
-
02-16-2008, 08:53 AM #1
- Join Date
- Feb 2008
- Location
- Germany
- Posts
- 7
Problem setting up FSUIPC and GC Demo
Hello,
I have networked 2 PCs via WideFS. The connection is established (FS window says "1 connected", Wide Client says "connected").
But as soon as the connection is established, the speed in the PFD is "41.440", the altimeter is "7560". My aircraft is for testing purposes the "Project Opensky 738"
To check my setup, I ran pmFileCheck. And here are strange results, too:
pmFileCheck recognizes, that FSUIPC/WideFS is running, but it is not able to determine the version of FSUIPC. The version of WideFS is also determined strangely: It's .002. I've installed the latest versions of both WideFS and FSUIPC and both are registered.
Then it checks the FS9 framerate. Again strange results... the values are around 10.000.
I have already re-installed anything (FS9, FSUIPC, WideFS, GC Demo) and I varied the FSUIPC and WideFS versions.
I have been trying to solve the problem all day (yesterday and today). But I can't get it working.Regards, Tobi
-
02-16-2008, 10:23 AM #2
- Join Date
- Oct 2005
- Location
- Holley, New York U.S.A.
- Posts
- 1,776
Is your version of FSUIPC and wideClient registered? Has to be to work with Pm.
Bob Reed
-
02-16-2008, 10:30 AM #3
- Join Date
- Feb 2008
- Location
- Germany
- Posts
- 7
-
02-16-2008, 10:41 AM #4
-
02-16-2008, 10:44 AM #5
- Join Date
- Feb 2008
- Location
- Germany
- Posts
- 7
Hello,
same behaviour with the default 734. I tested it also with my laptop. Same. Both OS installations are fresh...
I tested now the CDU Demo... the Set Position function seems to work. The FS sets my aircraft to the specified location. So FSUIPC and the network seem to work...Regards, Tobi
-
02-16-2008, 10:48 AM #6
- Join Date
- Oct 2005
- Location
- Holley, New York U.S.A.
- Posts
- 1,776
Sounds to me like you better go to Peter's site and jump on the forum.. No idea what is going on there. You are using the right version of FSUIPC, right? Not the one for FSX? Had to ask....
Bob Reed
-
02-16-2008, 10:54 AM #7
- Join Date
- Jan 2007
- Posts
- 496
This is a sure indication of one of the following:
1. The codesigning on the FSUIPC.DLL is bad. This could be because the GlobalSign certificate is missing (there's a fix provided for that), or that the FSUIPC.DLL file is corrupted or has been tampered with. It may even be because you have stopped some Windows services running -- the cryptographic one is needed, for instance.
The FSUIPC Log file will tell you more. You can also check the signature yourself by looking at the Digital Signatures tab in FSUIPC.DLL's Properties.
OR
2. Your system date precedes the date of purchase of your WideFS or FSUIPC Key, or both.
OR
3. One or both of your FSUIPC and WideFS keys are illegal pirate-generated versions. I hope this is not the case, but remains one of only three possibilities that I know of.
You should really come to my Support Forum for support of these programs, you know.
Regards
Pete
-
02-16-2008, 11:04 AM #8
- Join Date
- Feb 2008
- Location
- Germany
- Posts
- 7
Yeah, I'm so happy, it works
What I've done: Clear cache and delete all "offline files" and re-downloaded FSUIPC and to ensure anything WideFS.
Thanks Bob and Peter... next time I'll come with FSUIPC-related problems to you
... I'm going to fly nowRegards, Tobi
Similar Threads
-
Fsuipc offset problem??
By spitfire9 in forum Phidgets Interface & Alan Dyers' FS2PhidgetReplies: 1Last Post: 02-23-2011, 02:44 PM -
FSUIPC SETTING OF FLAPS
By shoumi in forum General Builder Questions All Aircraft TypesReplies: 8Last Post: 01-30-2011, 05:49 AM -
Encoder setting problem
By Avio in forum FS2Phidget UsersReplies: 3Last Post: 09-13-2005, 04:28 AM
Search Pretty Womans from your city for night
Fsbus ng io