Delphi

Hi Pete, I'm using P3DV4 / WIN10 / IvAp2. IvAp gives me a error message the the connection to FSUIPC does not work. IvAp is installed on the same computer as P3DV4 and runs external. The connection to SimConnect is ok. The IvAp logs shows the problem as follow: [2017-07-09 18:37:40] IvAp v2.0.2.2773 / Windows v6.2.9200 [2017-07-09 18:37:40] SimConnect: Linked to Acceleration Pack/SP2 version [2017-07-09 18:37:40] SimConnect: connected to Lockheed Martin® Prepar3D® v4 v4.0 with SimConnect v4.0 [2017-07-09 18:37:40] Status: Successfully connected to the Flight Simulator [2017-07-09 18:37:41] Teamspeak: trying to load sdk from D:\Program Files (x86)\IVAO\IvAp v2\TSRemote.dll [2017-07-09 18:37:41] Teamspeak: sdk found and linked [2017-07-09 18:37:41] Options: Weather is active [2017-07-09 18:37:41] Weather: locking to departure / destination active [2017-07-09 18:37:41] Weather: clear [2017-07-09 18:37:41] Weather: unlocked from [2017-07-09 18:37:41] Options: SDK active [2017-07-09 18:37:41] FSUIPC: Connect #0 has failed [2017-07-09 18:37:42] ServerPing: EU3 has a ping of 125 and a load of 0.251000 [2017-07-09 18:37:42] ServerPing: EU2 has a ping of 172 and a load of 0.238000 [2017-07-09 18:37:42] ServerPing: EU6 has a ping of 250 and a load of 0.244000 [2017-07-09 18:37:42] ServerPing: EU4 has a ping of 250 and a load of 0.253000 [2017-07-09 18:37:42] ServerPing: best server is EU2 [2017-07-09 18:37:42] FSUIPC: Connect #1 has failed [2017-07-09 18:37:43] FSUIPC: Connect #2 has failed [2017-07-09 18:37:44] FSUIPC: Connect #3 has failed [2017-07-09 18:37:45] FSUIPC: connection failed, giving up I could not fine any information about the connectivity problem at the FSUIPC log. Any idea what the problem could be? I know it's an IvAp problem, but you might have the insides what the problem coud be :-) Kind regards, Ruediger

Pete, we need you.... Ruediger

Hi Paul, currently I'm working on a RAAS system. The FSUIPC DLL Longitude/Latitude Helper Classes is a big help in the realization of the project. I wonder if it is possible to calculate the distance from a aircraft position and track to a runway FsLatLonQuadrilateral, based on Longitude/Latitude Helper Classes functions. Thanks for your help! Rüdiger

Thanks... Ruediger

Hi Paul, thanks... Could I please get it for the 4.0 framework. Ruediger

Hi Paul, during the initialization my program reads the FS installation path. Dim FSInstallationPath As Offset(Of String) = New Offset(Of String)(&H3E00, 256) After reading the path once I want to disconnect that offset: FSInstallationPath.Disconnect() The issue is that it seems that the offset does not get disconnected. The FSUIPC logfiles shows that it is continually reading the offset with each FSUIPCConnection.Process(). I do not do any reconnect in the whole application. I use the FSUIPC DLL 3.0.5937.1 Kind regards, Ruediger

For a automated gate kiosk system I need the information on which gate the aircraft is located. In a frist step it would be sufficient to have the information regarding the selected gate of the WORLD / GoTo Airport/... dialog. I'm looking for proposal how I could retrieve this information. Ruediger

Hi Paul, the new DLL seems to have an issue. The name space does not get imported. All offset definitions are shown as error in vb.net. Replacing the FSUIPCClient dll with the version form 26.02.2016 the name space is imported. Ruediger

Hi Paul, many thanks for your fast response. Have a nice weekend, Ruediger

Hi Paul, my problems seem to find no end. Bit operation does not work with FSUIPC Client DLL anymore. Setting offsets to values works. For years I used the following operation to manipulate bits: Dim PMRecallMomentary As Offset(Of BitArray) = New FSUIPC.Offset(Of BitArray)(&H56F9, 1) PMRecallMomentary.Value.Set(1, True) Worked perfect. Now the bits do not change anymore. For further tests I used a slightly different code, as you propose in your documentation: Dim lights As Offset(Of BitArray) = New FSUIPC.Offset(Of BitArray)(&HD0C, 2) Me.lights.Value(5) = True Also does not work. Tried the followng work-around: Lights.Value = Lights.Value Or (2 ^ x) In that way it works. However, the work-around is not an option, because of to too many required code changes. Environment: - VB 2010 - .Net framework: v4.0.30319 - FSUIPC client DLL version: 3.0.5898.3 I hope you can help me again. Ruediger

Hi Paul, many thanks for your help. The key was to insert a FSUIPCConnection.Process after the generation of some dynamic offsets with startup of the application. I can not explain why this suddenly became a problem, because I did not touch that part of the program for a year or more. However, problem seems to be solved, that the importend point. Ruediger

Hi Paul, I have a serious issue which I could not solve in hours of troubleshooting. The problem occured after some code changes in my application. I get the following exception with FSUIPCConnection.Process: FSUIPC Error #65540: FSUIPC_WRITE_OFFSET_NEVER_READ. An attempt was made to write a value to an offset that has never been read. Offsets must be read at least once so thier values are in sync with the Flight Sim. If this offset is only ever writen to, mar... Well, I do understand what the message tells me, but 'Im not able to identifier the problem. Can you give me some more information regarding the background of the message which might help me to find the problem. I use FSUIPC client DLL version: 3.0.5898.3 Thanks! Kind regards, Ruediger

Hi Paul, works perfect now, thanks.... Ruediger

Hello Paul, today I played with FSUIPCConnection.SendControlToFS, latest beta of V3 from January 2016 (at least what I could find in one of the threads) As I understand it is not necessary to send a FSUIPCConnection.Process after FSUIPCConnection.SendControlToFS. Works basically, but the performance is much slower than when I fill 0x3110 and 0x3114 by myself and initiate a FSUIPCConnection.Process afterwards. I did not do any exact performance benchmarks between both methods. Played just a bit around with the encoder of COM1 STBY WHOLE (65636, 65637). The subjective observation is that the COM1 STBY display is 3x slower with FSUIPCConnection.SendControlToFS compared the 'old fashion' way. Because FSUIPCConnection.SendControlToFS would save me some lines of code, I would rather use that method then the old way. Perhaps you will find some time to look into the issue. Best regards, Ruediger

Thanks.....

Hi Pete, X-Plane is not one of the target patforms. I can use the range 6F00 - 6F7F. No Problem. Hopefully no other software will use this range too. Meanwhile FSSymphony has more that 200 registerd users and I'm limited in spare time to give support if unexpected things are happen. Ruediger

Hi Pete, due to some additional feature of the upcomming Version 3 of FSSymphony I need a additional offset range of 128 Byte, mainly required for an offset range of 80 bytes for a 4x20 LCD display. Thanks in advance! Ruediger

Hi Paul, so far all my test cases worked very well. Starting now with the implementation. If I find an issue I will inform you. Thanks again... Ruediger

Hi Paul, today I had less spare time than expected. I could only test IntersectDMENauticalMiles. Works perfect. That exactly what I need. Tomorrow I will be out of town. The final test I will perform on Thursday. Rüdiger

Hi Paul, how did you do that so fast? :-) Many, many thanks...... I will test it and give you a response by tomorrow afternoon. Ruediger

Perfect, thanks.... Ruediger

Hallo Paul, currently I'm working on a program which generates map overlays for flight path, filed flight plan, approach and depature procedures. I use your fsuipc.dll for all the coordinates calculation. Works great :-), thanks. In order to complete my program I would need some additional coordinate calculations as part of your Longitude/Latitude Helper Classes: 1. Calculation of a Lat / Lon given by the following descripition (example): Track yyyy (degree) from XXXX (Lat / Lon) until intercepting radial ZZZ (degree) from a given coordinate (Lat / Lon) 2. Calculation of a Lat / Lon given by the following descripition (example): Track yyyy (degree) from XXXX (Lat / Lon) until a certain distance (DME) to a given coordinate (Lat / Lon) Would be great if version 3.0 of your fsuipc.dll would have these additional features. Regards, Ruediger

I really did not want you to put a lot of work in it. Was just a question if it would be possible. I'm fine with your answer. Best regards, Ruediger

Snippet from runways.txt: Runway 14L/32R centre: N50:52:04.1813 E007:08:50.5801 302ft Start 14L: N50:52:48.3995 E007:07:46.4148 302ft Hdg: 137.5T, Length 12495ft Computed start 14L: Lat 50.880466 Long 7.129046 Start 32R: N50:51:19.9630 E007:09:54.7454 302ft Hdg: 317.5T, Length 12495ft Computed start 32R: Lat 50.855190 Long 7.165721 Hdg: 137.520 true (MagVar 0.800), Asphalt, 12495 x 197 ft Primary ILS ID = IKES Primary ILS: IKES 110.90 Hdg: 137.5 , Flags: GS BC "CAT II ILS 14L" Secondary ILS ID = IKEN Secondary ILS: IKEN 109.70 Hdg: 317.5 , Flags: GS BC "CAT III ILS 32R" *** Runway *** EDDK0141 Lat 50.880466 Long 7.129045 Alt 302 Hdg 137 Len 12495 Wid 197 ILS 110.90, Flags: GS BC *** Runway *** EDDK0322 Lat 50.855190 Long 7.165721 Alt 302 Hdg 317 Len 12495 Wid 197 ILS 109.70, Flags: GS BC Snippet from runways.xml: <ILSHdg>318.5</ILSHdg> <ILSid>IKEN</ILSid> <ILSslope>3.00</ILSslope> <Lat>50.855190</Lat> <Lon>7.165720</Lon> <FSStartLat>50.853893</FSStartLat> <FSStartLon>7.164522</FSStartLon> ************************************************ With <FSStartLat> / <FSStartLon> some add-on sceneries place the aircraft on the hold line, which needs an other heading than the runway heading. If you wish put the <FSStartLat> / <FSStartLon> into Google Earth. This will show the problem. Mea culpa, if I read the data in a wrong way. Best Regards, Ruediger

Hi Pete, thanks for you fast response and your proposual to add the required information to the Runways.xml (new tag <FSStartHdgT>). Let give me an example to make sure that we are on the same page: Environment: FS9 + AS Add on EDDK (I could make the example also on an other installation with P3D V2.4 if you wish) Airport selection: EDDK, RWY 32R Result: The FS places the Aircraft to the short holding of rwy 32R with a heading of 040 If I place the aircraft with the FSStart coordinates for for RWY32R the aircraft is placed correct to the short hold coordinates, but with the rwy heading, not hdg 040 as required at this point. I checked the runways.txt. Could not find the required information. Best regards, Ruediger