frazer84

Hi! Is there any way, via FSUIPC for FS9, to detect wherever a client has connected to a multiplayer session or not? I'm making a LUA-script to connect to the Squawkbox multiplayer session, since SB is running on a separate computer and I don't want to use the keyboard on the FS-computer. Then I want to know if the LUA script has succeeded with connecting to the session or not. Thanks!

Didn't try that one, thanks for the suggestion, will try it out!

Hi! I'm having problem setting date and time via FSUIPC. I can set the values ok, and they reflect correctly in the World>Time and Season-dialog in FS9, but the visual time doesn't change. If I enter the Time and Season-dialog, where my set values are seen, and then press ok, the set time and date will be set after a texture reload, but not directly when setting the values via FSUIPC. I'm setting the following values: 0238 1 Hour of local time in FS (0–23) 0239 1 Minute of local time in FS (0–59) 023A 1 Second of time in FS (0–59) 023E 2 Day number in Year in FS (counting from 1) 0240 2 Year in FS Thanks! Regards, Daniel

Hi! I'm having problems with the steering tiller function used through FSUIPC in FS9. Here's how I set it up: On the FSUIPC Axis Assignment tab, I press rescan and move the axis where I want to have the tiller. I can see the movement of the axis in the "IN" and "OUT" datafields, works perfectly this long. I select "Send direct to FSUIPC Calibration" and then tick the first checkbox and select SteeringTiller in the drop-down-box. Then I go to the Joystick Calibration tab, and press the right button until I get to screen number 9 ("Pan axes (etc)"). Here I should be able to see the SteeringTiller move as well, but it doesn't. Sometimes it does, sometimes it doesn't, which makes it very hard to diagnose. It sometimes helps if i check and uncheck any of the checkboxes in the calibration part for the tiller (Filter and Rev). I have also noted that if I takeoff and then land, come to a complete stop, and then start taxing again, it suddenly often work! Is there a bug in the SteeringTiller-function in FSUIPC or have I missed something out? It has never worked from the start, I always has to try all types of tricks to get it going. Sometimes it works, sometimes I will have to fly without the tiller. Any ideas?

After converting the 32-bits integer to a byte-array, I could access the 4 bytes and pick the first two, if that was the length I had requested from FSUIPC. This works fine and I get the correct results every time, with one exception: The vertical speed. In FSinterrogate, I can get negative values, but not when I try to access the same values. I get a small value in the first byte, and a large one in the 2nd byte. Adding these makes a value about 40000-50000 in a descend. The rest two bytes are empty (0). Any idea why I can't get negative values from FSUIPC, when FSinterrogate can?

I have checked with FSInterrogate, which shows the correct values (as well as the logs), so I'm sure that it is a programming-fault, but I don't know what. I have done as you said earlier, to set the integers to 0 before every read, which made it work better, but not every time. I have debugged this application for weeks, as well as rewritten it from scratch. I don't know how familiar you are with C#-programming, but is the declarations I wrote in the previous post the way you told me to do in your first answer in the thread? I'm not a programming-genious, but I'm learning...

Now I have tried most things, with some success. The values gets allright most of the time, but sometimes, for example when FS has been paused for a longer time, the values gets very large like the ones i described in the first post. If i restart my application, the values get all right again. A little more information about my system: I'm using FSUIPC version 3.4.8.0 on MSFS 2004 without the 1.1 patch. The application is developed in C# using Microsoft Visual Studio.net 2003. This is how i declare the variables used in the FSUIPC-calls: int dwOffset = 0; int dwSize = 0; int Token = 0; int dwResult = 0; int Result = 0; This is done before every call to FSUIPC is done. Thank you for your help!

Hi! I have a problem when programming my application to interact with FSUIPC. It works fine on my computer, but when I tried it on anther computer It didn't. After some debugging I found out that the values given by FSUIPC on the other computer isn't the same as the values my FSUIPC is sending out. For example is the ground-flag (Offset 0366) and Engine 1 fireing (Offset 0894). My computer gives the correct values (1 and 1 if the ac is on the ground with engine number 1 running). On the other computer I get the values 262145 instead in the same situation. Any ideas why? It's quite hard to develop applications when they only work on one computer :? Regards, Daniel