
cknipe
Members-
Posts
54 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by cknipe
-
Hi, Brand new FSX installation with SP1, FSUIPC Version 4.1.6.0. When starting up FSX, I gives the error: Flight Simulator was unable to load some program files and will now exit. Please reinstall Flight Simulator to restore or repair the program installation Fair enough, but surely FSX can't be buggered. When I dug a bit deeper, I found critial errors in Vista's Administrative Event Log: Activation context generation failed for "C:\Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll". Dependent Assembly Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61245.0" could not be found. Please use sxstrace.exe for detailed diagnosis. my FSUIPC Install Log: Installer for FSUIPC4.DLL version 4.16 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" SetupPath="C:\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: ... Okay, Probe Manifest matches installed SimConnect 60905 (Original) Found later build SimConnect 61234 (SP1 May07) Checking if there's already a version of FSUIPC4 installed in: C:\Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... No previous valid version found. FSX Modules folder created okay! Okay -- installed FSUIPC4 into "C:\Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Chris\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Chris\AppData\Roaming" Found FSX.CFG in "C:\Users\Chris\AppData\Roaming\Microsoft\FSX\FSX.CFG"! Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. No previous FSUIPC4 entry found, so adding it now ... ... 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\Chris\Application Data\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Contacts\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Cookies\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Desktop\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Documents\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Downloads\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Favorites\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Links\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Local Settings\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Music\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\My Documents\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\NetHood\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Pictures\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\PrintHood\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Recent\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Saved Games\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Searches\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\SendTo\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Start Menu\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Templates\Roaming" No FSX.CFG there Looking in "C:\Users\Chris\Videos\Roaming" No FSX.CFG there Now installing additional files into the Modules 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 All installer tasks completed okay! *************** End of Install Log *************** It did run properly for about 2 or 3 times, and now it is giving this error everything I try to start FSX. No other software, modules, planes, utils, etc are installed (yet)... Hmm, help? Ta, Chris.
-
Pete, I know how you feel about VB :D But uhm, I also know that you do semi understand the code... A nice example on how to do this with .NET... http://www.codearchive.com/dl.php?dlid=1350 Hopefully, it's helpful; A feature like this would indeed, be very nice! PS: Is the offset list up to date in the FSUIPC For Programmers.doc ? If not, where's the best place to get a complete list? Just wondering! -_ Chris
-
FSUIPC Shell VB .NET - Very Basic Question
cknipe replied to Pat Dotson's topic in FSUIPC Support Pete Dowson Modules
You have to call Process()... FSUIPCConnection.Open() Dim airSpeed As Offset(Of Integer) = New FSUIPC.Offset(Of Integer)(&H2BC) FSUIPCConnection.Process() Me.txtIAS.Text = airpeedKnots.ToString() FSUIPCConnection.Close() Something to that effect... -
Also 2003 (doesn't perform well), and I'm forced to due to my external storage (which only supports 2003). Replaced the WideClient PC last night with XP, problem went away... Guess I'll have to get myself a dedicated server and drop XP on my main workstation as well again....
-
Just out of curiosity... Is anyone sucessfully running WideClient (6.60 or higher preferred) on Windows 2003??? If there's anyone with something like VMWare Server/Workstation arround here (Come on, I know there's more PC nerds sitting and flying planes with 1TB of storage by their knees :lol:), can anyone test it please? It would seem the way Windows 2003 deals with Processor switches and Memory management, it makes it very difficult for WideClient to operate... In my case, I'm getting very spiky CPU usage from WideClient (100% for a couple of seconds, every other couple of seconds), so I'm just wondering whether this is something on my side, or whether this is something OS side... Thank you!
-
Some wideclient problems?
cknipe replied to Jorge Diogo's topic in FSUIPC Support Pete Dowson Modules
Aaah, Time for some plane spotting at KATL then and let's debug... To answer your questions quickly... I may stand corrected, but I believe I only registered FSUIPC towards the middle / end of 2005. I've included my .key file for you to have a look at if you can get the date from there, otherwise, I'll have to go and look what the order date at SimMarket was... 6.47 *may* have just been the first version I got, and hence, put it on CD. I'm pretty sure I have used later versions since then, working. Said in the same breath however, I have been hecticly busy and did not fly to much for the last 6 months or so. Naturally when I started flying again now, the first thing I did, was update my nav databases, FSUIPC, WideFS, etc etc etc... This is where I picked the problem up. The ini was changed/updated when I updated WideFS/WideClient to 6.70. If you want, I'd be happy to look at a couple of less older versions and maybe try and see from my side which version started giving the problem - you'd have to supply the binaries though :wink: Perhaps even if we can try 6.50 (and if memory served me right, was working correctly - the version number rings a bell). As to "does it work"... Up to a point! It works as far as yes, it connects to WideServer, yes, it reads / updates data in WideServer, and yes, everything populates through to the simulator. The problem however is because the CPU is spending so much time in WideClient, CPU cycles are VERY limited for the addons. The addons thus, give utter crap performance, and some even crash!!! Logs and Key (for tracking purposes I guess) attached... I'll run a search through the forums as well as Im sure I made previous posts... Perhaps I get the latest 'known' version that I ran, from there somewhere! -- Chris. PS: It just occurred to me, posting my key on here in a zip is not a good idea :twisted: SimMarket states I purchased FSUIPC+WideFS in July 2005 WideClientLogs.zip -
Some wideclient problems?
cknipe replied to Jorge Diogo's topic in FSUIPC Support Pete Dowson Modules
My apologies then Pete, and sorry for stealing the thread it seems 8) Interestingly, I have not changed *anything* yet as far as configs go. Same WideServer, I've downgraded WideClient to 6.47 (The only one I have on CD) - NO problem WHAT SO EVER. New WideClient 6.70, wham. Even after changing the AutoRestart=0, 6.70 still 100% CPU, 6.47 works flawlessly.... :? And this is being done on exactly the same client PC obviously, merely coping the 6.47 and 6.70 exe's the whole time.... -
Some wideclient problems?
cknipe replied to Jorge Diogo's topic in FSUIPC Support Pete Dowson Modules
Pete, I'm afraid to say, same thing here! The moment a application connects via WideClient, 100% CPU (WideClient idle's at 0% with no applications running). I have now tried with *only* FSRealTime (which is VERY trival as far as usuage goes).... WideClient.ini: [Config] ApplicationDelay=5000 Port=8002 Port2=9002 Protocol=TCP ServerIPAddress=192.168.1.10 ServerName=SUPERMAN Visible=Yes WaitForNewData=500 Window=32000,32000,112,27 ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 ResponseTime=18 TCPcoalesce=No MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 [User] ;CloseReady1=Yes ;CloseReady2=Yes ;CloseReady3=Yes ;CloseReady4=Yes ;DelayReady1=30 ;DelayReady2=5 ;DelayReady3=5 ;DelayReady4=10 ;Log=Errors+ Log=Yes ;RunReady1=C:\Games\FS2004\ActiveSky\Modules\ASv6\ASv6.exe ;RunReady2=C:\Games\FS2004\AISmooth\AISmooth.exe ;RUNReady3=C:\Games\FS2004\FSRealTime\FSRealTime.exe ;RunReady4=C:\Games\FS2004\RCV4\RCV4.exe ShowRcFrameRate=Yes WideFS.ini: [Config] AdvertiseService=1 AutoRestart=5 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port=8002 Port2=9002 Protocol=TCP RestartTime=10 SendTimeout=15 TCPcoalesce=No [User] Log=Errors+ [ClientNames] 1=MICROMAN WideFS.log: ********* WideServer.DLL Log [version 6.70] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 29/09/06, Time 17:43:01.703: Server name is SUPERMAN 391703 Initialising TCP/IP server 391703 Initialising IPX/SPX server 391703 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 391703 Failed to start IPX/SPX Server 391703 Initialising UDP/IP server 392344 Broadcasting service every 1000 mSecs 403016 Restarting service due to total lack of use 403016 Failed to start IPX/SPX Server 674250 Incoming connection Accepted ok (skt=4136) TCP 674484 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 674969 Auto restart due to low frame rates! 674969 Failed to restart IPX/SPX Server! 674984 Incoming connection Accepted ok (skt=3972) TCP 675062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 680969 Auto restart due to low frame rates! 680969 Failed to restart IPX/SPX Server! 680984 Incoming connection Accepted ok (skt=4092) TCP 681109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 686969 Auto restart due to low frame rates! 686969 Failed to restart IPX/SPX Server! 687000 Incoming connection Accepted ok (skt=3944) TCP 687125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 692969 Auto restart due to low frame rates! 692969 Failed to restart IPX/SPX Server! 692984 Incoming connection Accepted ok (skt=3852) TCP 693172 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3852) TCP 698969 Auto restart due to low frame rates! 698969 Failed to restart IPX/SPX Server! 698984 Incoming connection Accepted ok (skt=3948) TCP 699031 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 704969 Auto restart due to low frame rates! 704969 Failed to restart IPX/SPX Server! 704984 Incoming connection Accepted ok (skt=4136) TCP 705031 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 710969 Auto restart due to low frame rates! 710969 Failed to restart IPX/SPX Server! 710984 Incoming connection Accepted ok (skt=3972) TCP 711125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 718312 Auto restart due to low frame rates! 718312 Failed to restart IPX/SPX Server! 718344 Incoming connection Accepted ok (skt=4160) TCP 718516 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 724969 Auto restart due to low frame rates! 724969 Failed to restart IPX/SPX Server! 724984 Incoming connection Accepted ok (skt=3944) TCP 725062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 730969 Auto restart due to low frame rates! 730969 Failed to restart IPX/SPX Server! 730984 Incoming connection Accepted ok (skt=4136) TCP 731109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 736969 Auto restart due to low frame rates! 736969 Failed to restart IPX/SPX Server! 737000 Incoming connection Accepted ok (skt=3948) TCP 737109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 742969 Auto restart due to low frame rates! 742969 Failed to restart IPX/SPX Server! 743000 Incoming connection Accepted ok (skt=4092) TCP 743094 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 748984 Auto restart due to low frame rates! 748984 Failed to restart IPX/SPX Server! 749016 Incoming connection Accepted ok (skt=3972) TCP 749141 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 758172 Auto restart due to low frame rates! 758172 Failed to restart IPX/SPX Server! 758281 Incoming connection Accepted ok (skt=4160) TCP 758656 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 765047 Auto restart due to low frame rates! 765047 Failed to restart IPX/SPX Server! 765078 Incoming connection Accepted ok (skt=3944) TCP 765156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 770969 Auto restart due to low frame rates! 770969 Failed to restart IPX/SPX Server! 771000 Incoming connection Accepted ok (skt=4136) TCP 771203 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 776969 Auto restart due to low frame rates! 776969 Failed to restart IPX/SPX Server! 777000 Incoming connection Accepted ok (skt=3948) TCP 777203 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 783000 Auto restart due to low frame rates! 783016 Failed to restart IPX/SPX Server! 783453 Incoming connection Accepted ok (skt=4092) TCP 783641 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 789016 Auto restart due to low frame rates! 789016 Failed to restart IPX/SPX Server! 789016 Incoming connection Accepted ok (skt=3972) TCP 789234 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 795000 Auto restart due to low frame rates! 795000 Failed to restart IPX/SPX Server! 795000 Incoming connection Accepted ok (skt=4160) TCP 795312 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 800984 Auto restart due to low frame rates! 800984 Failed to restart IPX/SPX Server! 801437 Incoming connection Accepted ok (skt=3944) TCP 801578 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 806984 Auto restart due to low frame rates! 806984 Failed to restart IPX/SPX Server! 807328 Incoming connection Accepted ok (skt=4136) TCP 807578 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 813016 Auto restart due to low frame rates! 813016 Failed to restart IPX/SPX Server! 813047 Incoming connection Accepted ok (skt=3948) TCP 813312 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 818984 Auto restart due to low frame rates! 819000 Failed to restart IPX/SPX Server! 819500 Incoming connection Accepted ok (skt=4092) TCP 819625 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 825000 Auto restart due to low frame rates! 825000 Failed to restart IPX/SPX Server! 825500 Incoming connection Accepted ok (skt=3972) TCP 825594 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 831516 Auto restart due to low frame rates! 831516 Failed to restart IPX/SPX Server! 831750 Incoming connection Accepted ok (skt=4160) TCP 831750 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 837000 Auto restart due to low frame rates! 837000 Failed to restart IPX/SPX Server! 837016 Incoming connection Accepted ok (skt=3944) TCP 837125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 842984 Auto restart due to low frame rates! 842984 Failed to restart IPX/SPX Server! 843016 Incoming connection Accepted ok (skt=4136) TCP 843109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 849000 Auto restart due to low frame rates! 849000 Failed to restart IPX/SPX Server! 849016 Incoming connection Accepted ok (skt=3948) TCP 849156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 854984 Auto restart due to low frame rates! 854984 Failed to restart IPX/SPX Server! 855469 Incoming connection Accepted ok (skt=4092) TCP 855703 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 861000 Auto restart due to low frame rates! 861000 Failed to restart IPX/SPX Server! 861016 Incoming connection Accepted ok (skt=3972) TCP 861156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 867000 Auto restart due to low frame rates! 867000 Failed to restart IPX/SPX Server! 867016 Incoming connection Accepted ok (skt=4160) TCP 867172 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 872984 Auto restart due to low frame rates! 872984 Failed to restart IPX/SPX Server! 873016 Incoming connection Accepted ok (skt=3944) TCP 873172 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 879000 Auto restart due to low frame rates! 879000 Failed to restart IPX/SPX Server! 879031 Incoming connection Accepted ok (skt=4136) TCP 879219 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 885000 Auto restart due to low frame rates! 885000 Failed to restart IPX/SPX Server! 885016 Incoming connection Accepted ok (skt=3976) TCP 885266 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 891000 Auto restart due to low frame rates! 891000 Failed to restart IPX/SPX Server! 891031 Incoming connection Accepted ok (skt=4092) TCP 891250 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 896984 Auto restart due to low frame rates! 897000 Failed to restart IPX/SPX Server! 897516 Incoming connection Accepted ok (skt=3944) TCP 897828 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 903000 Auto restart due to low frame rates! 903000 Failed to restart IPX/SPX Server! 903484 Incoming connection Accepted ok (skt=4160) TCP 903531 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 909000 Auto restart due to low frame rates! 909000 Failed to restart IPX/SPX Server! 909484 Incoming connection Accepted ok (skt=4288) TCP 909594 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4288) TCP 915000 Auto restart due to low frame rates! 915000 Failed to restart IPX/SPX Server! 915484 Incoming connection Accepted ok (skt=4136) TCP 915562 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 920984 Auto restart due to low frame rates! 920984 Failed to restart IPX/SPX Server! 920984 Incoming connection Accepted ok (skt=3976) TCP 921078 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 930062 Auto restart due to low frame rates! 930062 Failed to restart IPX/SPX Server! 930094 Incoming connection Accepted ok (skt=4092) TCP 930531 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 937000 Auto restart due to low frame rates! 937000 Failed to restart IPX/SPX Server! 937078 Incoming connection Accepted ok (skt=3944) TCP 937156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 943047 Auto restart due to low frame rates! 943047 Failed to restart IPX/SPX Server! 943047 Incoming connection Accepted ok (skt=4160) TCP 943187 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 949062 Auto restart due to low frame rates! 949062 Failed to restart IPX/SPX Server! 949109 Incoming connection Accepted ok (skt=3948) TCP 949344 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 955000 Auto restart due to low frame rates! 955000 Failed to restart IPX/SPX Server! 955047 Incoming connection Accepted ok (skt=4136) TCP 955359 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 960984 Auto restart due to low frame rates! 960984 Failed to restart IPX/SPX Server! 961281 Incoming connection Accepted ok (skt=3976) TCP 961281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 966984 Auto restart due to low frame rates! 966984 Failed to restart IPX/SPX Server! 967047 Incoming connection Accepted ok (skt=4092) TCP 967281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 972984 Auto restart due to low frame rates! 972984 Failed to restart IPX/SPX Server! 973016 Incoming connection Accepted ok (skt=3944) TCP 973281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 978984 Auto restart due to low frame rates! 979000 Failed to restart IPX/SPX Server! 979000 Incoming connection Accepted ok (skt=4160) TCP 979297 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 985000 Auto restart due to low frame rates! 985016 Failed to restart IPX/SPX Server! 985016 Incoming connection Accepted ok (skt=3948) TCP 985312 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 991000 Auto restart due to low frame rates! 991016 Failed to restart IPX/SPX Server! 991016 Incoming connection Accepted ok (skt=4136) TCP 991328 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 996984 Auto restart due to low frame rates! 996984 Failed to restart IPX/SPX Server! 997016 Incoming connection Accepted ok (skt=3976) TCP 997094 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 1003016 Auto restart due to low frame rates! 1003016 Failed to restart IPX/SPX Server! 1003016 Incoming connection Accepted ok (skt=4092) TCP 1003062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1009000 Auto restart due to low frame rates! 1009000 Failed to restart IPX/SPX Server! 1009484 Incoming connection Accepted ok (skt=3944) TCP 1009609 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 1015016 Auto restart due to low frame rates! 1015016 Failed to restart IPX/SPX Server! 1015016 Incoming connection Accepted ok (skt=4160) TCP 1015109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1021016 Auto restart due to low frame rates! 1021016 Failed to restart IPX/SPX Server! 1021531 Incoming connection Accepted ok (skt=3948) TCP 1021703 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 1027000 Auto restart due to low frame rates! 1027016 Failed to restart IPX/SPX Server! 1027016 Incoming connection Accepted ok (skt=4136) TCP 1027156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1033000 Auto restart due to low frame rates! 1033016 Failed to restart IPX/SPX Server! 1033016 Incoming connection Accepted ok (skt=3976) TCP 1033187 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 1044984 Auto restart due to low frame rates! 1044984 Failed to restart IPX/SPX Server! 1045000 Incoming connection Accepted ok (skt=4092) TCP 1045219 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1050984 Auto restart due to low frame rates! 1051000 Failed to restart IPX/SPX Server! 1051000 Incoming connection Accepted ok (skt=3944) TCP 1074000 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 1074984 Auto restart due to low frame rates! 1074984 Failed to restart IPX/SPX Server! 1075000 Incoming connection Accepted ok (skt=4160) TCP 1075078 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1080984 Auto restart due to low frame rates! 1080984 Failed to restart IPX/SPX Server! 1080984 Incoming connection Accepted ok (skt=3948) TCP 1081125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 1087031 Auto restart due to low frame rates! 1087031 Failed to restart IPX/SPX Server! 1087031 Incoming connection Accepted ok (skt=4136) TCP 1087062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1092984 Auto restart due to low frame rates! 1093000 Failed to restart IPX/SPX Server! 1093016 Incoming connection Accepted ok (skt=3976) TCP 1106359 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 1106984 Auto restart due to low frame rates! 1106984 Failed to restart IPX/SPX Server! 1106984 Incoming connection Accepted ok (skt=4092) TCP 1107062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1112984 Auto restart due to low frame rates! 1113000 Failed to restart IPX/SPX Server! 1113422 Incoming connection Accepted ok (skt=3944) TCP 1113609 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 1119000 Auto restart due to low frame rates! 1119000 Failed to restart IPX/SPX Server! 1119031 Incoming connection Accepted ok (skt=4160) TCP 1119094 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1149016 Auto restart due to low frame rates! 1149031 Failed to restart IPX/SPX Server! 1150437 Incoming connection Accepted ok (skt=4820) TCP 1183141 Client socket unused for too long: removing (skt=4820) TCP 1183156 Incoming connection Accepted ok (skt=4820) TCP 1219391 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4820) TCP 1221250 Auto restart due to low frame rates! 1221250 Failed to restart IPX/SPX Server! 1221687 Incoming connection Accepted ok (skt=4136) TCP 1221812 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1227000 Auto restart due to low frame rates! 1227000 Failed to restart IPX/SPX Server! 1227000 Incoming connection Accepted ok (skt=4828) TCP 1227297 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1233000 Auto restart due to low frame rates! 1233000 Failed to restart IPX/SPX Server! 1233469 Incoming connection Accepted ok (skt=4092) TCP 1233562 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1239000 Auto restart due to low frame rates! 1239000 Failed to restart IPX/SPX Server! 1239047 Incoming connection Accepted ok (skt=4840) TCP 1239281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4840) TCP 1244984 Auto restart due to low frame rates! 1244984 Failed to restart IPX/SPX Server! 1245016 Incoming connection Accepted ok (skt=4160) TCP 1245078 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1251000 Auto restart due to low frame rates! 1251000 Failed to restart IPX/SPX Server! 1251016 Incoming connection Accepted ok (skt=4820) TCP 1251062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4820) TCP 1257000 Auto restart due to low frame rates! 1257000 Failed to restart IPX/SPX Server! 1257453 Incoming connection Accepted ok (skt=4136) TCP 1286406 Client socket unused for too long: removing (skt=4136) TCP 1286422 Incoming connection Accepted ok (skt=4136) TCP 1304109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1305000 Auto restart due to low frame rates! 1305000 Failed to restart IPX/SPX Server! 1316047 Failed to start IPX/SPX Server 1346781 Incoming connection Accepted ok (skt=4828) TCP 1347000 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1347000 Auto restart due to low frame rates! 1347000 Failed to restart IPX/SPX Server! 1347000 Incoming connection Accepted ok (skt=4088) TCP 1347234 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4088) TCP 1353000 Auto restart due to low frame rates! 1353000 Failed to restart IPX/SPX Server! 1353000 Incoming connection Accepted ok (skt=4840) TCP 1353234 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4840) TCP 1359000 Auto restart due to low frame rates! 1359000 Failed to restart IPX/SPX Server! 1359031 Incoming connection Accepted ok (skt=4824) TCP 1359266 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4824) TCP 1365000 Auto restart due to low frame rates! 1365000 Failed to restart IPX/SPX Server! 1365000 Incoming connection Accepted ok (skt=4820) TCP 1365266 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4820) TCP 1370984 Auto restart due to low frame rates! 1371000 Failed to restart IPX/SPX Server! 1371484 Incoming connection Accepted ok (skt=4092) TCP 1371578 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1376984 Auto restart due to low frame rates! 1376984 Failed to restart IPX/SPX Server! 1376984 Incoming connection Accepted ok (skt=4828) TCP 1377047 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1382984 Auto restart due to low frame rates! 1382984 Failed to restart IPX/SPX Server! 1383469 Incoming connection Accepted ok (skt=4088) TCP 1383609 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4088) TCP 1389000 Auto restart due to low frame rates! 1389016 Failed to restart IPX/SPX Server! 1389469 Incoming connection Accepted ok (skt=3972) TCP 1389641 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 1395016 Auto restart due to low frame rates! 1395016 Failed to restart IPX/SPX Server! 1395469 Incoming connection Accepted ok (skt=4824) TCP 1395625 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4824) TCP 1401937 Auto restart due to low frame rates! 1401937 Failed to restart IPX/SPX Server! 1401984 Incoming connection Accepted ok (skt=4828) TCP 1402187 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1406984 Auto restart due to low frame rates! 1407000 Failed to restart IPX/SPX Server! 1407031 Incoming connection Accepted ok (skt=4092) TCP 1407109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1413000 Auto restart due to low frame rates! 1413000 Failed to restart IPX/SPX Server! 1413437 Incoming connection Accepted ok (skt=4840) TCP 1413672 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4840) TCP 1419031 Auto restart due to low frame rates! 1419031 Failed to restart IPX/SPX Server! 1419062 Incoming connection Accepted ok (skt=4088) TCP 1419156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4088) TCP 1424984 Auto restart due to low frame rates! 1424984 Failed to restart IPX/SPX Server! 1425000 Incoming connection Accepted ok (skt=3972) TCP 1425203 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 1430453 Error 10053: client socket disconnected at Client: removing (skt=3972) TCP Interesting how it still wants to use IPX, even though I have a protocol=tcp??? Even minutes after I closed WideClient, I still get messages from FSRealTime in my simulator as well. It seems there are *massive* delays between WideServer and WideClient as far as communications go... WideClient.log attached due to size... WideClientLog.zip -
Problem programming fsuipc
cknipe replied to djlidgley's topic in FSUIPC Support Pete Dowson Modules
I guess not even Pete's to old to learn :D These things are not called Rotary Switches, they are Rotary Encoders. They generate a pule 'x' degrees out of phase in the one direction, and 'y' degrees out of phase in the other direction (In relation to a common input). IMHO, These switches should be connected to a Encoder IC (Mostly PICs) - which makes the outputs from the IC operate similarly to a standard Rotary Switch. These switches are normally controlled by things like PICs and Digital Circuitry - it won't be the best bet to tie them up as is, directly to a software interface... -- C -
After going through the documentation (like you should have done) possibly: OBC4 OBC6 0C00 0C01 If you search and read the relavent sections in the manual, you'll soon notice that there are actually plenty of things that would help you.
-
Hi Pete, I see what you meant in some rather ancient posts about this. It's not really worth the effort :( Did have a look at the DebugAll logs, but ja... Didn't make me any wiser. The contents of the TCP packets are definately there, but as to what it is actually sending / receiving in layman's terms... Urgh. For one, the debug log only indicates (for example), Requesting offset xyz. It never actually logs *how* it requests it (i.e. what is sent to wide server). Then it receives the packet on the Ethernet, and it shows the packet dump of the data it has received. Same goes for DebugAll on WideServer... I guess I'm kinda hoping to a more 'communications' orientated log, i.e. Client -> Server: this is how I request offset xyz Server -> Client: offset xyz = whatever I won't know whether this is possible or feasable for you, but you can't perhaps include a TX and RX dump? Some other detailed logging on what it is receiving / transmitting other than the actual packet, might be usefull as well. If that's not possible, I'm definately not going to fiddle with this - will take ages to figure this out. I guess, as you said in previous posts about this topic, the most feasable way to accomplish this would be to simply write your own module for FS9, and have your remote OS talk to the module, rather than WideFS... That might also actually be *allot* easier I reckon... Thanks for the input Pete. Much appreciated :) -- Chris.
-
Will bring in the ol' ethernet packet dumper and see what I can come up with them. Shouldn't be to hard unless you're using some form of encryption and the like, which I doubt. :) As long as there's no violations in regards to licensing and the like, I guess, I am allowed to do this right? Thanks Pete, Chris.
-
Something *really* weird with WideFS
cknipe replied to cknipe's topic in FSUIPC Support Pete Dowson Modules
Thanks for the suggestions Pete and welcome back!!! FSRealTime... Yes. That hasn't been updated in a LONG time. I'll check for updates on that. FSUIPC also seems to have been over written by something again (I hate it when that happens). FSRealTime reports 3.520 :oops: I'll do some updates tonight and see if the problem presist. AI is only IVAO planes and Just Flight Traffis 2005 (not to old). I think the problem is the perhaps old FSUIPC and FSRealTime. I didn't pick this up at the time of posting, so thanks for pointing it out ;) -
Hi, Hope someone can help me. When ever WideServer is running with 1 WideClient connected, my fs9 crashes when loading scenery. WideClient only serves FSRealTime, and ASv6. The crash occurs when I move from one Airport to another (World->Select Airport). I suspect, this is because fs9 takes time to load the scenery and as such WideServer cannot process the data received (or something similar). This is the only time it happens, I can reproduce this every single time. The only way I can move to another airport is to either slew (not really usefull to slew from FAJS to KJFK), or, shutdown WideClient before I move to another airport. This started happening about a day ago now, after I removed some unused airplanes from my simulator - and I cannot see how that would affect WideServer/Client. Something I haven't tried yet was reinstalling WideServer & FSUIPC, but I see that as a last resort. On occasion right after the crash, WideServer would give a Winsock error. Hopefully someone can help me out here. Thanks, Chris
-
Hi Pete, Any chances perhaps of a WideServer SDK type of document? Nothing definate yet, but I might want to access WideServer from another OS and not Windows... Would be extremely nice if it would be possible. Will understand if not :) -- Chris
-
Since when do you modify the fs9.cfg to install modules??? :?
-
Module creation using a C# Project
cknipe replied to bfalcao's topic in FSUIPC Support Pete Dowson Modules
There are very good examples in the C# .NET SDK, available as part of the FSUIPC SDK. I'd suggest you download the SDK, look at the libraries, and the examples provided. -
Hi, I don't know about VB6 and how similar it is to .NET, but please have a look at some of my posts. There are lots of code for VB.NET. http://forums.simflight.com/viewtopic.php?t=47736 <-- Contains a whole property to get the data, and you can simply add to the property to write to the offset. -- Chris.
-
Ok, I'm only going to take the crash detection for now... Dim IPCOnGround As Boolean = True Public ReadOnly Property OnGround() As Boolean Get Dim dwResult As Integer = 0 Dim dwToken As Integer = 0 Dim myInt As Integer = 0 Try myFSUIPC.FSUIPC_Read(&H366, 2, dwToken, dwResult) myFSUIPC.FSUIPC_Process(dwResult) myFSUIPC.FSUIPC_Get(dwToken, myInt) Finally If myInt = 0 Then IPCOnGround = False Else IPCOnGround = True End Try Return IPCOnGround End Get End Property And again... By typing over my example code from the one PC into this here text box... I saw my mistake already... Wrong variables!!!!! Thanks for the WideClient info.. What you explained seems to be spot on. And yes, I'm definately going to start doing less reads, 10ms is definately to much... I do need a 'smooth' flow of the data though, but I recon 250ms (4 times per second) should be fine... I'll play some more with the code and DOUBLE CHECK things giving problems before running here again :) Thanks Pete. PS: Don't you ever sleep?
-
Hi Pete, I've managed to sort out most of my problems (believe it or not :D ). Slap me with a rotten trout, but I only realised all the formulas and var types are *also* in FSI2 - STUPID of me, I know... Ok, so now everything is running and working, and reporting correctly. I can finally proceed to actually do things with the data now. With some of my data, I also call a couple of boolean values (plane on ground, stall warning, overspeed warning, and crashed). My application pulls this data every 10ms (and it does put quite a bit of stress on WideFS - CPU load arround 50% on a P4 1.7GHz). However, all my data returns correctly, except the booleans. They would *sometimes* at *random* indicate wrong. The airbourne boolean is about the only one that's always correct. Stalling and overspeed goes true very often for a couple of seconds, to minutes, and then back to false (0), the same with the crashed flag (but significantly less than overspeed and stalling). When these values goes high in my application, there is no indication in the Simulator that they are true (i.e. overspeed / stall warning does not go off in the cockpit) I know updating every 10ms may be asking allot, I will more than likely update less later (like say, every 250ms or something), but, can these controls be trusted from FS? It's funny to me how it can magically say, I crashed (even through I have crash detection disabled in the simulator), and then later, it says that I didn't crash? The simulator must be confused 8) Is this pointing back to my code again, or is it because I call them to often / fast, or is it merely a matter of using additional functionality to determine, or rather, confirm, these booleans? This is about the last thing I have a problem with - hopefully this is something simple as well... On another issue related to WideFS... Pete have you had any reports of WideFS using 100% CPU when it looses it's connection to FSUIPC? I have my Sim running, WideFS connected (with no application running from WideFS). When I close my Sim (and FSUIPC), WideFS on the second computer will consume 100% CPU... Not a big problem, just a bit of a annoyance. Yes, latest version of both FSUIPC and WideFS. Thanks as always, -- Chris.
-
I am using signed Ints Pete... :( Int32, 4 Bytes, 32-Bit, Signed Integer, and Long, 8 Bytes, 64-Bit, Signed Integer (Which I have to use for the calculation, otherwise VB gets Overflow errors). For interest sakes, http://www.startvbdotnet.com/language/datatypes.aspx Result is always the same... When pitch is 4 Degrees UP, I get 356. When it should in fact be, -4. The strange part, is that it works for Bank, as well as MagVar (virtually the same code, just different offsets and formulas where needed). It's *just* pitch that's doing this... VB does something strange to * 360 / ( 65536 * 65536 ). Before I do the calculation, my data from FSUIPC matches on the spot with the data that FSI2 gives. After the calculation, I sit with the wrong answer. I'm starting to hate VB more and more now... Thanks anyways Pete (as always)... Time to go learn Delphi perhaps. -- C
-
Hi, Pete, I think there's a small error in the documentation... 0578, Pitch control: FSInterrogate gives: 4,261,696,370 (-2.78874 Factored) Documentation says: Pitch * 360 / (65546 * 65536). Ok, now let's do some math. 4,261,696,370 * 360 = 1,534,210,696,440 65536 * 65536 = 4,294,967,296 1,534,210,696,440 / 4,294,967,296 = 357.21 <-- A rather steap pitch, don't ya think? :shock: However, subtracting 360 from the answer, gives me -2.79 (Yes, my HP Calc rounds it off). Should the formula in the documentation thus not read: Bank * 360/(65536*65536)-360 ? Just want to make sure I get this right :) -- Chris.
-
Interesting... Anyways Pete. You where right. The overloads determine the size of the variable - for 0262, the variable sent must be a short, and yes, it works. For interest sakes, it seems the boolean is 4 bytes long, I presume thus it is converted to a integer. You suggested this exact same thing before, I'm sure I tried it... Don't know why it didn't work then... Oh well. As always, thanks... -- Chris
-
Hi Pete, The token thing makes semi sense to me (perhaps it's because I'm a VB kid :) ) - it basically adds a additional step to reading data from FSUIPC... I'm just a tad sad that Bob didn't go into the writing aspect in his reply. I'll more than likely just send him another quick one asking about the writing. I did check with the logging on FSUIPC now, the offset is never written to the simulator - nevermind the data, so I'm presuming that there are other funtions that needs to be called to actually get the data to the simulator (just like Read requires Get). I'm sure the writing must work though, it's just a matter of what and how. Just had a thought while reading through my 2nd mail to Bob, Pete... In the VB Write... Why would a token be needed at all (Given what a Token actually is - from the above). Is it not safe to presume (because of the Token reference), that the Write will also go into the FIFO Buffer? There is no function to work with Write to push data out of that buffer (which, the Get basically does for a Read after the process call), so I'm wondering now.... It's going to be interesting to see what Bob says. IMHO and based on how I am understanding this entire thing, there should be something like the Get, for a Write call as well... -- Chris.
-
Hmmm... I *hate* it when this happens. It seems things *really* changed in the .NET port.... Examples from the C# source, in the SDK: result = fsuipc.FSUIPC_Write(0x05DC, 1, ref token, ref dwResult); offset, value, 'token', and result. No size specified. Functions for writing in the FSUIPC Class for .NET: Overloads Function FSUIPC_Write(ByVal dwOffset As Integer, ByVal Param As Byte, ByRef Token As Integer) As Boolean) Overloads Function FSUIPC_Write(ByVal dwOffset As Integer, ByVal Param As Short, ByRef Token As Integer) As Boolean) Overloads Function FSUIPC_Write(ByVal dwOffset As Integer, ByVal Param As Integer, ByRef Token As Integer) As Boolean) Overloads Function FSUIPC_Write(ByVal dwOffset As Integer, ByVal Param As Long, ByRef Token As Integer) As Boolean) Overloads Function FSUIPC_Write(ByVal dwOffset As Integer, ByVal Param As Double, ByRef Token As Integer) As Boolean) Not one of them reference the size... Functions definately seem different however. Something that got added for the .NET Classes (VB and C# it seems). All I know is, if I don't specify it, it doesn't work. From the comments in the example code, it's a Variable holding a returned token index. Not by default it doesn't. I'm sure there's a setting for it in the compiler though, or I always have Option Explicit On. Hmmm... It's definately different Pete.... :( Guess I'll have to figure this one out on my own... I don't unfortunately have the clean C lib close by as I laying in bed with my laptop -grin-, but just from the example you gave below, the functions must be different... -- C