Jump to content
The simFlight Network Forums

Kurt2404

new Members
  • Posts

    3
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Austria

Kurt2404's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi Pete, you safed my day! I don't operate my FSX in windowed mode, so no information line is present --> solved The Windows-Firewall needed just the port 8002 to be added as outgoing and incoming rule --> solved Your hint for the CTRL-key worked perfect --> solved Many thanks for your perfect service! Kind regards Kurt
  2. Hi Pete, thanks for your fast reply! In the meantime I did: update FSUIPC to version 4.743 update WideFS to version 6.86 (registration with the present key worked perfect for both) invent exception rules for the Windows firewall of my stationary FSX-PC for incoming and outgoing data traffic to and from WideClient.exe on my laptop The result was none - no change at all. The only thing I realised was that FSX does not show the message line "waiting for clients". FSUIPC reacts normal, PlanG (installed on the PC) connects easily with FSX. The most disturbing thing is that I did nothing but copying the complete content of the FSX-folder from one location to another. :angry: And I don't have any clue what kills the data transfer between FUIPC and WideClient... Any other ideas how to find the reason for this problem? Regarding the second topic: Thats the problem when someone is using a keyboard which is designed for a different language (my native tongue is German)... My STRG-key is exactly your CTRL!:oops: I got the confirmation from your answer that the CTRL-key may only be transmitted in connection with any other key. And this exactly my problem: This CTRL+xx combinations influence other programs quite often. TS accepts easily just the CTRL as push to talk key and the CRTL-key alone does not interfere with any other software. Regards Kurt
  3. Good morning everbody, I had FSX + FSUIPC 4 + WideFS successfully running on my main PC (Win 7 Home Permium 64 bit) in connection with a networked Laptop and PlanG since almost a year or so. Some days ago I decided to move the complete FSX installation from my main HDD to a much faster SSD. To keep all settings I mounted the SSD as "Microsoft Flight Simulator X" on the same location in the tree as FSX has been before and simply moved the whole content of the (perviousley safed) original folder into this new drive. Everything worked so far perfect (less stutters due to slow texture loading), just ASE (whicht remained on the HDD) requested a new registration verification. Now to my first problem: FSUIPC seems to work so far but I can't connect to my Laptop via WideFS any more. The network itself seems to work, because I could mount net drives pointing to folders on my main PC from my Laptop. I enclose below the contents of the ini and log files for both WideFS server and client. Anybody any idea what I'm doning wrong? WideServer log: ********* WideServer.DLL Log [version 7.53] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 31/10/11, Time 07:12:35.591: Server name is GABI-PC-2010 15710 Initialising TCP/IP server 15710 Initialising IPX/SPX server 15710 IPX/SPX socket() failed [Error=10044] Socket type not supported 15710 Failed to start IPX/SPX Server 15710 Initialising UDP/IP server 16100 Broadcasting service every 1000 mSecs WideClient log: ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 31/10/11, Time 07:23:57.478: Client name is KURT-LAPTOP_11 187 Attempting to connect now 187 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 187 ... Okay, IP Address = 192.168.0.186 21232 Error on client pre-Connection Select() [Error=10060] Connection timed out 21232 Ready to try connection again 22246 Attempting to connect now 38173 New Client Application: "PlanG" (Id=440) 66363 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 66363 ... Okay, IP Address = 192.168.0.186 132507 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 132507 ... Okay, IP Address = 192.168.0.186 198714 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 198714 ... Okay, IP Address = 192.168.0.186 264921 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 264921 ... Okay, IP Address = 192.168.0.186 331190 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 331190 ... Okay, IP Address = 192.168.0.186 397444 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 397444 ... Okay, IP Address = 192.168.0.186 463713 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 463713 ... Okay, IP Address = 192.168.0.186 529857 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 529857 ... Okay, IP Address = 192.168.0.186 596126 Trying TCP/IP host "GABI-PC-2010" port 8002 ... 596126 ... Okay, IP Address = 192.168.0.186 FSUIP 4 ini: [General] UpdatedByVersion=4530 History=R7PEZ77A2FCQOGP8QNH27 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 Console=No MouseWheelTrim=No MouseWheelTrimSpeed=1 FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=No [JoyNames] AutoAssignLetters=No 0=Saitek X52 Flight Control System 1=Saitek Pro Flight Rudder Pedals [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [buttons] ButtonRepeat=20,10 1=H0,4,K68,8 [AutoSave] AutoSaveEnabled=No [GPSout] GPSoutEnabled=Yes Port=WideFS Speed=4800 Interval=2000 PosTo6Decimal=Yes Sentences=GGA,GSA,GSV [GPSout2] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [ClientNames] 1=KURT-LAPTOP_11 WideFS client ini: ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=32000,32000,160,38 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 ServerName=GABI-PC-2010 Protocol=TCP ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== *************************************************************************************************************************************************************************************** The second problem: I'm mainly flying helicopters using a Saitek X52 + Proflight pedals. When flying online we use Teamspeak as communication base and I want to designate the button no. 4 of the stick as send button. There are just very few keys left to be used as send button without interfering other functions - one of them is the STRG, which works perfectly on the keyboard in cooperation with the TS client. But I did not find a solution to tie by stick button 4 with the STRG key via FSUIPC. Any hint would be appreciated. Thanks in advance to all helpers! Kind regards Kurt
×
×
  • 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.