Paul Henty

Can you just do two quick tests for me? When you application is running can you please test the values of: FSUIPCConnection.FlightSimVersionConnected to make sure it's coming back as 'Prepar3d'. FSUIPCConnection.DLLVersion to make sure it's 2.6.5124. (This will show what dll was actually loaded, rather than checking the version number on the disk). Thanks, Paul

Here's the fix. Let me know how it goes. Two zips: one targets the .NET 2 framework, the other .NET 4 Client Profile. EDIT: Bugs in this upload. See good attachments further down. Paul

George, I really don't have the time to do this. This would be long and complicated code. All I can do is describe the process. The UserGuide shows you how the fsLonLatPoint class is used. I don't have MySQL so I cannot write the code to access the database. You need two fields, one for Longitude and one for Latitude so you can filter on them. Even92LN gave you sample code. This just shows you how to do it. It's not code you can just paste into your application. If you cannot see from that code how to make it work then you need to learn programming or c# first. I have suggested this many times. This forum is for helping people use my DLL. I cannot write your application for you one feature at a time, sorry. I just don't have the time. This isn't my Job, it's just a hobby. I will answer questions about my DLL, but not about how to write your application. Paul

Good guess. Just checked the code and that's exactly the problem. Easy enough to fix though. I'll make a fixed version of the DLL for you over the weekend. Paul

Hi Peter, I've just reinstalled my laptop so my FSX/FSUIPC stuff isn't up an running yet. I'll get it installed at the weekend and test this for you - only on FSX though as I don't have P3D. At least if it works on FSX we can rule out a problem with the DLL. Paul

Yes that's all you need to find the current airport. You would do something like this: 1. Find current player position 2. Work out the Lon, Lat coordinates of a box 5 NM around the player 3. Select the airports from the database that have coordinates within this box You can use the FsLatLonPoint class in my DLL to help with getting the coordinates of the test box. See the UserGuide.pdf for more details on this class. If you get more than 1 airport back you can measure the distance to each one and find the closest. You can use FsLatLonPoint for this also. Paul

Yes that would be the easiest and fastest way if you know SQL. Most people use text files, for example those produced by MakeRunways.exe by Pete Dowson. Text files are slower but people use them because they do not know how to use SQL databases. Paul

Hi Jens, The requirement for third-party keys was removed from FSUIPC a long long time ago. As your tests have shown your software will work on unregistered FSUIPC without any problem. However, if your software is commercial then you should speak to Pete about using FSUIPC. Paul

FSUIPC cannot tell you what airport you are at or departed from. The easiest way to get this information is to provide a text box for the user to enter the ICAO code manually. The much more difficult way is to have a database of all the airports with their longitude and latitude. You then take the player's Lon and Lat from FSUIPC and use it to work out which airport they are at. Paul

It works all of the time. So when you're taxiing it will be 1. That's why you need to test it going from 0 to 1, not just being 1. So if it's 1 you only save your data if the previous value was 0. Paul

Sorry but I don't know MySQL. Try looking for a MySQL tutorial or forum. Paul

No. That is not what is written in the example application. You need to open the example application and look at the code in there. Search for Open() and Process() and look at the try/catch blocks. The catch blocks catch the errors when FS is not loaded. Paul

You can only check this by trying the Open() or a Process(). If the simulator is not running these methods will throw an exception which you must catch. The sample application shows this. Look for the Open() and Process() calls and you will see the Try, Catch blocks that detect if the simulator is running. Paul

FSUIPCConnection.FlightSimVersionConnected.ToString() Paul

Yes, that looks good to me. This is as easy as I can make it: 1. At the top of your form with the other 'using' statements, add this: using System.Collections; 2. Declare the offset as follows: private Offset<BitArray> lights = new Offset<BitArray>(0x0D0C, 2); 3. Access each light as follows. This example is for strobe lights (bit 4). For other light numbers look up offset 0D0C in the "FSUIPC4 Offset Status.pdf". // Strobe lights (Bit 4) if (lights.Value[4]) { this.lblStrobeLights.Text = "Strobes ON"; } else { this.lblStrobeLights.Text = "Strobes OFF"; } Paul

0D0C. The sample application that I supply with the DLL shows reading (and writing) of lights. These are c# types and hold different types of data. For example 'int' holds an Integer 32 bits wide. 'String' holds text. If you don't know what different types are you really need to learn some basic c#. Here is a web page that explains the types: http://msdn.microsoft.com/en-us/library/ya5y69ds.aspx If you want to know which c# type to use with each offset you need to read the UserGuide.pdf. Page 7 has a table showing which types to use depending on the size of the offset and what kind of data is stored in the offset. You need to also need to read the information about each offset in "FSUIPC4 Offset Status.pdf" Knots is correct. To convert metres/second to Km/h you need to multiply by 3.6: double gsKMH = ((double)airspeed_gs.Value / 65536d * 3.6d); The easiest way to get this data is to use the PayloadServices in the DLL. At the top of your form (where you declare the offsets), declare a payload services object called 'ps'. private PayloadServices ps; After you Open() the connection to FSUIPC, assign this object: FSUIPCConnection.Open(); ps = FSUIPCConnection.PayloadServices; Then when you want to get the payload data you can use the code like this: ps.RefreshData(); //Empty weight in lbs & kgs double fw_ew_lbs = ps.AircraftWeightLbs - ps.FuelWeightLbs - ps.PayloadWeightLbs; double fw_ew_kgs = ps.AircraftWeightKgs - ps.FuelWeightKgs - ps.PayloadWeightKgs; this.emw1.Text = fw_ew_lbs.ToString("F0") + " (Lbs)" + " / " + fw_ew_kgs.ToString("F0") + " (Kgs)"; //---------------------------------------------------------------------------------// //Zero fuel weight in lbs & kgs double fw_zfw_lbs = ps.AircraftZeroFuelWeightLbs; double fw_zfw_kgs = ps.AircraftZeroFuelWeightKgs; this.zfw1.Text = fw_zfw_lbs.ToString("F0") + " (Lbs)" + " / " + fw_zfw_kgs.ToString("F0") + " (Kgs)"; //---------------------------------------------------------------------------------// //Weight payload in lbs & kgs double fw_pl_lbs = ps.PayloadWeightLbs; double fw_pl_kgs = ps.PayloadWeightKgs; this.payload1.Text = fw_pl_lbs.ToString("F0") + " (Lbs)" + " / " + fw_pl_kgs.ToString("F0") + " (Kgs)"; Paul

I also get 0 or 1 on the default Boeing 737 and 747. But on the default A320 I get more sensible values. There is nothing wrong with your code. These are just the values that FSUIPC/FSX gives us. Try on different aircraft. If you think they are wrong then ask Pete about these values in the main support forum. This file holds the text for the Intellisense. This appears when you are programming inside Visual Studio. It gives information about the method calls and parameters for my DLL. You only need this while coding. You do not need to give this file to users. Paul

Hi Even, The only way to know this is to catch the errors produced when the FSUIPC Process() call fails. If you are using my DLL the sample program that comes with it shows how to do this. Look at the code on the tick event for Timer1. You'll see a try/catch block where it catches the FSUIPCException from the Process() call which means FSX/9 has unloaded or crashed. It then closes the connection, tells the user, and lights a button so the user can try reconnecting. If you're not using my DLL then it will depend on the programming language you are using. You would also be in the wrong sub-forum :-) so I recommend you post again in the main support forum (above this one) and include the language you are using. Paul

Use offset 0BEC. This is for the nose gear. It is possible to get values for all three wheels if you want. Or just use one of them like my example: Declare the offset as follows: private Offset<int> gearPositionNose = new Offset<int>(0x0BEC); Test the value to determine gear up (0), down (16383) or in transit (a value in between). if (gearPositionNose.Value == 0) { this.lblGear.Text = "Gear Up"; } else if (gearPositionNose.Value == 16383) { this.lblGear.Text = "Gear Down"; } else { this.lblGear.Text = "Gear In Transit"; } Below is an example for left wing inboard flaps using offset 30F0. You can do the same for other flaps and slats at offsets 30F0 to 30FE. Not all of these offsets will have values. It depends on the aircraft. Declare the offset as follows: private Offset<short> leftInboardFlap = new Offset<short>(0x30F0); Calculate the flap angle and display: double flapsDegrees = (double)leftInboardFlap.Value / 256d; this.lblFlaps.Text = flapsDegrees.ToString("F0"); For details of the other offsets I have mentioned, please look in the FSUIPC4 Offsets Status.pdf. Paul

The ground speed in offset 02B4 is in metres/second. To convert to knots you need to multiply by 1.943844492: double airpeedKnotsGround = (double)airspeed_gs.Value / (65536d * 1.943844492); this.label18.Text = airpeedKnotsGround.ToString("F0") + " Knots"; You have not shown me the offset declaration. You always need to show it. This offset should be declared as an 'int' like this: Offset<int> airspeed_gs = new Offset<int>(0x02B4); Paul

Your code works well for me. If you are not seeing the Longitude and Latitude updating then make sure you have your events linked properly: On the visual form designer, click on the timer1. In the properties grid, click on the lightning button to see the list of events. There is only one called Tick. Make sure it has 'timer1_Tick' next to it. If it's blank select timer1_Tick from the dropdown box. Do the same for the buttons. Look for an event called 'click' and make sure the correct _Click event is selected from the dropdown box. I notice that you are calculating things like Airpeed, but not displaying them. You need to create a label or textbox in which to display this information. Then you need to assign the calculated values to these labels or textboxes. For example to display the airspeed, create a label on the form designer called lblAirspeed. Then add a line of code after you calculate the airspeed to display the value: double airpeedKnots = ((double)airspeed.Value / 128d); this.lblAirspeed.Text = airpeedKnots.ToString("F0") + " Kts"; The ToString() method converts the numeric value into a string so it can be displayed as text. The F0 rounds the value to 0 decimal places. For 2 decimal places you would use ToString("F2"). These are very very basic C# programming concepts. You should learn C# before you attempt something more complicated like getting data from FSUIPC. I really cannot teach C# here. Paul

I can't see much wrong with the code except that you don't call displayCurrentPosition() anywhere so it's never run. You need to call this from a button press, or a timer if you want regular updates. Paul

I can't see anything wrong there. Please show me: 1. Where you declare playerLongitude and playerLatitude 2. What does appear in the text boxes? You can also try inspecting the value of playerLatitude.Value while the program is running using a breakpoint. Paul

I don't understand Russian so I wouldn't be able to read it. Paul

Welcome George, 1. Download the DLL Package from the sticky thread at the top of this sub forum: http://forum.simflight.com/topic/74848-fsuipc-client-dll-for-net-version-24/ 2. In the Docs folder open "UserGuide.pdf" and read the sections called 'Introduction' and 'Getting Started' 3. Load the Sample C# Project in Visual Studio. Run it and see what it does (It does quite a lot of what you want). Study the code to see how it works. You will need to refer to the document called "FSUIPC4 Offsets Status.pdf" which gives details of all the information that you can get from FSUIPC. This is found under your main FSX folder in a sub folder called "\Modules\FSUIPC Documents". If you have any questions about using the DLL, ask here. If you have questions about FSUIPC in general please ask Pete in the main forum. Unfortunately I cannot teach C# or programming here so if you need to learn to program you'll have to find some other resources for that. Paul