Jump to content
The simFlight Network Forums

peterk54

Members
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

About peterk54

  • Rank
    Advanced Member
  • Birthday 07/19/1938

Profile Information

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

Recent Profile Visitors

1,233 profile views
  1. Dear John Thank you for advise. I assume you are very busy with more important topics for the community. I try myself to fix. Yes, we copied the FSX XML gauges including our models. The autopilot panel is a set of various switches (change switch picture, send command i.e. AP APP HOLD ...) and displays. No real logic behind. It uses the FSX / P3D internal autopilot which was fine until now. The moesl we use our ones as they are very simple and do not use a lot of resources. We fly real cockpit sections and never look from outside to the aircraft. Just used as externeal view without panel
  2. P3D v5.1.8.26742 FSUIPC v6 latest version Several hardware unchanged Windwos 10 Prof, updated to latest updates available Aircraft: FSX 747-400, original panel Our software: VB6 external programm connected thru FSUIPC or WideFS Since approx 2 weeks (we assume it was updating to this latest version of P3D) we have the problem that APP mode when engaged thru our software and FSUIPC does only capture VORLOC and not anymore the GS. However when we engaged thru mouse click on the panel button APP it works fine. The values of the variables are write and read correctly by FSUIPC W
  3. @Ing Nieto I think you have to use: / Creo que tienes que usar: Offset &H07CC, 2 Bytes, Autopilot heading value, as degrees *65536/360 Offset &H07CC, 2 bytes, valor de rumbo del piloto automático, como grados * 65536/360 It is not heading TRUE or MAGNETIC / No se dirige a VERDADERO o MAGNÉTICO Hope this helps / Espero que esto ayude Peter / Pedro
  4. Dear Thomas Thank you for the feedback, I appreciate. I was saying - at least I wanted to say and state - that an error is on our side, I was not giving any fault to FSUIPC. Yes, I'm looking in offset 3308, I have to check what I messed up because backups of software shows P3d v4.5. I will search there. Still I have also to find out why my writings are broken. Best regards, thanks for help Peter
  5. Good evening I do since many years VB6 programming thru FSUIPC. No issues and running alltime smooth. Since yesterday I get back just FS version 12, rather then before correctly up to 45.Over network thru WideFS or local, the same. We still get correct data from P3D but it seems values can not be written anymore. My system: - Prepar3D v4 SDK 4.5.12.30293 - Windows 10 Pro, Build 18362.19h1_release.19318-1202, Default language German, Swiss keyboard - Lenovo X1 Extreme, all updates done, latest BIOS installed, with nVidia 1050 - FSUIPC5, Version 5.153 (12th December 2019) -
  6. Sorry, WideClients was meant. OK, got it. We will give the two Subnets a try as we want to remove our issues. Peter
  7. 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: 255.255.255.255. ..." 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
  8. 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
  9. 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=192.168.0.150 To my opinion they are according the document we have read Best regards Peter WideClient - 02.ini WideClient - 01.ini
  10. 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
  11. 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
  12. 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, W
  13. 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
  14. 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
  15. 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. I
×
×
  • 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.