Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About peterk54

  • Rank
    Advanced Member
  • Birthday 07/19/1938

Profile Information

  • Gender
  • Location
    Oberglatt / ZH (LSZH)
  • Interests

Recent Profile Visitors

1,033 profile views
  1. Sorry, WideClients was meant. OK, got it. We will give the two Subnets a try as we want to remove our issues. Peter
  2. Hello Pete We configured according above advise from you, thank you for this support. At the same time we are considering the following: Both our sims are in the same SubNet. Going thru UDP specs we found: "... The broadcast address for a LAN is either the highest address in the local subnetwork or the universal broadcast address: ..." To our understanding broadcast messages have no source identifier who sent the message. Are both FSUIPC's sending to same broadcast adress ? If so we shall divide up into two subnets each with one router, soubnet-mask would than be rather Question to you: does WideServer know who sent (=IP address) broadcast messages ? With best regards Peter
  3. Hello Pete Thanks for fast response. Swiss German as mother-language is slightly different from English ... Server = FS station with FSUIPC.INI, Section [WideServer], ProtocolPreferred=TCP Clients = My stations with WideClient.INI, Section [Config], ServerName=B737-222-FS, Protocol=TCP Thats it ? Anyway I will restudy the paper, sorry Peter
  4. Dear Pete See attached WideCLient.ini files from 2 different stations. We checked the others stations, I believe all are the same: [Config] ProtocolPreferred=UDP BroadCastMode=Yes //ServerName=B737-222-FS ServerIPAddr= To my opinion they are according the document we have read Best regards Peter WideClient - 02.ini WideClient - 01.ini
  5. Dear Pete These are attached the logfiles from the B737-222-FS Server (FSUIPC running) and of one WideClient running. I saw nothing bad, except that WideClients try to connect with the "B737-222-FS" server rather than 192.169.x.x. When I start all clients with WideClient, and only than P3D v4, they connect. With best regards Peter B737-222-FS 20180115 FSUIPC5_prev.log B737-222-01 20180115 WideClient.log B737-222-FS 20180115 FSUIPC5.log
  6. Hello Pete WideClients are all running on different PC's. 1 FSServer + 7 WideClients for one sim, 1 FSServer + 6 WideClients for another sim. Thanks for the lead. I will write protocolls and have a look myself first. We get all data and very fast. So once all connected everything is perfect. I'll come back to you, Peter
  7. Dear Pete Happy X-Mas and New Year ! I know you are away from the computer until 7th January. No hurry on this matter please. We tried Protocol=UDP and IP-Adress ratherTCP and server-names. No changes of the symptoms. Each simulator starts and runs perfectly, if the other is not running. But: the first of the sims starts perfectly. We start the second: on the second sims client computer we need to stop the WideClient run by Windows Autostart and manuall restart with the desktop icon. Then they runs as well. We checked Administrator rights, programm run by administartor, Windwos compatibilty and such stuff. No idea anymore were to search. Best regards Peter
  8. Dear Pete Thanks for your fast reaction and advise as ever ! I will check carefully all our settings and introduce IP adresses rather names. Yes, they should be defined to each sim. Yes, we mean WideClients. Cool, I do not need to check SimConnect. As many of our hardware is running over TCP/IP with have quite some mebers in the network. We will advise results in the next days. Best regards Peter
  9. Hello I have 2 simulators running in one network. One P3D v3, the other P3D v4. Both SDK's installed. Each latest versions. Each simulator uses the Server and some PC's as client to show (non P3D) instruments and performing aircarft system task. Data sent thru FSUIPC and WideCLients, each newest versions. Each sim does run by itself in an excellent way. Each sim-system is setup that after WideClients is connected, our programms start automatically. No issues to connect with other appllications i.e. Sim Commander. Issues starts when both sims run together. FIrst starts with no issues. The second one however we need to stop and restart the Wideclients before they connect. Once done, everything seems to be perfect. - Do we need to configure SimConnect on the servers and the respective clients manually ? - FSUIPC is configured with the servers name, not the IP ? Do we need to change ? - All computers using WideClients on the same IP ports. Do we need to change ? - Any comments where we shall start to search ? Thanks and greetings from Switzerland Peter
  10. Dear hkhoanguyen We use VB6. You may adopt to .NET our proposal. You can use the Windows API FindWindow and search for class "FS98MAIN". Take the hadle received to read with Windows API GetWindowText. The P3D windows does change from "Lockheed Martin® Prepar3D® v3 with WideServer: waiting for clients" to "Lockheed Martin® Prepar3D® v3 with WideServer: 1 connected" where 1 shows total clients connected. when this is up, P3D and FSUIPC do run properly. During flying check offset &H3F02, 2, VarPtr(FS_FLTSTN_RELOAD) against a variable xxx_OLD if it does increase. If it does, wait until reloaded with offset &H3365, 1, VarPtr(FS_MENUDIALOG_FLAG). Wait until not anymore 1 but 0. Reload all new data required into your application. Hope this assists. Regards Peter
  11. Dear Volker You know my respect for your work ! Just a very small unconvenience: 1. Prepar3D / 2. FSUIPC* 4.966c/ 5.103 and WideFS 6.999c 3. I use the FSC in a network! Yes 4. FS Commander 9.6 v9 01-July-2017 and Database Manager 9.6 v9 Build 7-July-2017 5. Navigraph AIRAC Cycle 1501 Rev 1 Jan08-Feb04/15 6. Simmarket download version 7. Operating System Windows 7 -32/-64 Professional 8. How many monitors are used = 1 When flight plan is opened the menu item "Show Plan" under "Flight-Plan" should be marked ON. Now to remove two mouse-clicks are required. Thanks & best regards Peter
  12. Guten Abend Volker 1. Prepar3D / 2. FSUIPC* 4.966c/ 5.103 and WideFS 6.999c 3. I use the FSC in a network! Yes 4. FS Commander 9.6 v9 01-July-2017 and Database Manager 9.6 v9 Build 7-July-2017 5. Navigraph AIRAC Cycle 1501 Rev 1 Jan08-Feb04/15 6. Simmarket download version 7. Operating System Windows 7 -32/-64 Professional 8. How many monitors are used = 1 Die Angabe Total Fuel welche FSUIPC - oder sogar SimConnect - zur Verfügung stellt ist falsch. Um welchen Betrag ist mir unklar, scheint Prozentual zu sein. Die korrekte Menge kann mittels Daten aus FSUIPC berechnet werden. Wir müssen das für unsere Programme auch so lösen. Sende gerne den Quellcode in VB6 zu. Herzliche Grüsse Peter
  13. Good afternoon Volker As ever fast reply ! OK, I accept your system and will read the manual. We mostly do "dirty" flight plans not using SID / STAR nor Transitions. And we fly VOR to VOR or Intersec. Best regards Peter
  14. Dear Volker, Dear janar737 I respond as I found similar issue using FSC flightplans. This is a part of the plan created in FSC 9.6 rev 7: VHHH ... BARUG LNZ SBG KPT ... LSZH At creation everything is fine. But if OK button in the Flight Plan window is pushed or the plan is reopened, SBG is not anymore close to Salzburg. Now it is Strathbogie, Australie. We assume this error: The flightplan at reloading does take the first entry in the database rather to check with the correct coordinates found saved in the "pln" file. we tried several NDB's, VOR with same name and had alltime the same error. We use FSX or P3D v3.4, Win7-32, local or FSUIPC 4.966c with Wideclient 6.999z4, FSC Database Manger 9.6 rev 7 NET. We may found a solution ? Best regards, Peter
  15. Dear sxa1376 Great ! Such things happened to me as well ! Let me know if you have other questions. Best regards Peter
  • 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.