Pete Dowson

Why would you do that? Although I think it is all-round more efficient to have fixed IP addresses rather than have parts of Windows going out searching for connections now and then, there is no way I'd suggest doing this as a fixed rule. It can make it more complicated setting up routers, for instance (though I think it is worth the trouble, in the end). I don't know what Windows ICS does, but it sounds like you have it confused. Just switch back to the automatic addressing mode for now. Make sure it all works. then read more about ICS configuring before changing it again. Regards, Pete

This most certainly means that your Client PC doesn't recognise the name "FS9MOBIEL". Your client doesn't know your server. There is nothing you can do in any of my software, you need to get your Network working first. Sorry. Pete

One registration per user, any number of PCs. I don't like the one copy one PC systems. ;-) Regards Pete

Neither am I. What "setting up" did you do? If you had the network working already, and both machines are running Win2K or WinXP, then there's nothing much to do -- just put the DLLs into FS's modules folder and run WideClient on the client. Sorry, I wouldn't know what you changed to cause that. You shouldn't have changed anything if your Network was working. Certainly there's nothing WideFS or FSUIPC does to affect any other Network use, they are completely self-contained in that regard. Regards, Pete

Okay. I was a bit restless so I had another look before going to bed. The clue was in my last message. It's all to do with that change from 4 to 6 decimal places in the NMEA data. The fraction was being divided by 10000 to cope with it, but for 4 places it should be divided by 100. The thing I don't understand is why this didn't affect the previous two versions I sent youas I said, I'd not changed anything much that last time. The hundredths of minutes should have been wrong in both 2.602 and 2.603. Perhaps they were and you didn't notice, or forgot to mention? Anyway, this one (2.604) seems okay, and I've made the AV400 output independent of the 4/6 decimal option setting. Regards, Pete GPSout2604.zip

The TCAS data inserted in that way is not seen or understood by anything else in FS at all. It is merely a fabricatiion in FSUIPC data space to make TCAS displays reading such FSUIPC data show the 'target'. It is intended for those programs such as Squawkbox which feed in MP aircraft to FS, which are visible in FS but which aren't detected by FSUIPC because it only gets AI aircraft data. I have no idea whether Active Camera can handle MP aircraft, but certainly the Multiplayer interface is the only way I know of having more than one controllable aircraft in FS. Regards, Pete

Hmmm .... I don't understand that. All I did was do the same rounding as before (exactly the same) except inserting a check for the last two digits being >99 in which case I replace them with 99. I can't see how that can lose all other values except 00 and 01 -- that is totally weird! It should just fix those cases of xx100 to make them xx99. The minutes calculation hasn't been changed at all -- that is still EXACTLY as it was. Only the two hundredths digits are revised, just be that check. The code is several years old. I'll need to leave all this till I have time to work through it properly. I was trying to help in little bits of time here and there, but evidently this is a much bigger problem than I thought. It'll have to wait a week or three. Sorry. Erjust one thought. Do you have "PosTo6Decimal=No" set? It looks like it will go completely wrong if you try to set 6 decimal places -- which is defaulted by the looks of things. That was a recent change for more accuracy on NMEA devices. Even then, that would only affect the hundredths, not the minutes pair! Regards, Pete

Well, yes, but Project Magenta uses an FMS instead of a GPS style control and plan system. Take a look -- http://www.promagenta.com. Regards Pete

I'm actually amazed that it works at all! I've not looked into the GPS side of FS -- the offsets there were provided by someone else. I didn't know you could change them and still have it work! I have no idea, without reloading the flight -- but even that might be cached -- and of course doing that rather resets things. If you are talking about filing a plan for a complete flight, then it is easy. Create the plan file, then tell FSUIPC to load the flight which uses it. Quite honestly, I would not try to use the built-in plan and GPS system at all, but do it in the same way as, for example, Project Magenta does it for FMS guidance. You keep the plan, you display the route, etc, you provide the headings etc, and, if autopilot control is requested, you set them on the A/P. Such a method gives you complete control and lets you do exactly what you like. You don't need it. If I knew how to make FS load a plan into the current flight without going via the menu system to do it, I would probably provide it as a facility in FSUIPC in any case, akin to the current one for loading flights. As I said, if you are happy loading the complete plan for a flight before the flight starts, then that's the way to do it -- use the FSUIPC facility to load a specific flight, after writing that flight's plan. Regards, Pete

No Version Information? Tut tut! In that case the answer is to purchase a User key for FSUIPC. Then all the application validity checks are bypassed. Regards, Pete

It's okay. I'm just a bit bemused that this is the first problem reported with AV400 since I added it several years ago. It seems strange that the person originally asking for it didnt have problems. Maybe he never actually used it, or didn't use such a fussy unit? Anyway, I've re-written the Lat/Lon rounding algorithm, removed the Q code, and deleted one of the -'s after the T, so this, version 2.603, should be perfect. No? BTW from FSX onwards, GPSout will be bundled into FSUIPC as part of the user facilities, and will need user registration. Part of my plan to both reduce the number of different modules I have to keep track of, and to make paying for FSUIPC more attractive. ;-) Regards Pete GPSout2603.zip

Can you try the attached version 2.602, please, and let me know. I'm not sure I'm adjusting the right things here. Regards, Pete GSPout2602.zip

Hmmm. Strange. I've looked at the code and can't see why that should happen -- it is obviously something to do with the rounding. I'l need to put a check in to guard against that. Regards, Pete

What "RealBasic" module? Sorry, never heard of it. Pete

No, FSUIPC is a tool used by other programs. It has no facilities like that. WidevieW uses FSUIPC in any case and should be sychronising the weather, within reason, on each client -- but I suspect WidevieW is still trying to use only global weather settings, which worked fine on FS2002 and before but not so well on FS2004. Possibly Luciano is working on that -- it can be done with localised weather sent to weather stations around and ahead of the aircraft, as ActiveSky V6 does. If you only mean the cloud graphics, they are more or less generated at random on each copy of FS and cannot be synchronised to "flow" correctly. Pete

It's the file with the name you gave it (or the same as the Flight name if saved with that), but with file type 'PLN'. You'll find all of your FLT and PLN files in the "My Documents\Flight Simulator Files" folder. Regards Pete

It only happens if you specify both the protocol and the Server's IP address. It's just a very unusual combination which slipped my testing. I've fixed it here but there are other things I want to do so it hasn't made release yet. It has never really been a good idea to select the Server by its IP address -- the Name is much more flexible and safe in case your IP addresses change. And if you are using Win2000 or WinXP all round it hasn't been necessary to specify the server at all for several releases. It defaults to being on in any case (and i think the value is 1 for 1 second). You don't have to change it unless you have turned it off before -- but why would you do that? If you are using Win2000 or WinXP all round, your best bet would have been to dump all the Client INIs and not replace them in any case, just let WideClient make new ones. I think the ones in the ZIP are the same default in any case. Well, if you need to select between several servers running FS at the same time, then you need either the Name or the Address. But if, as in most cases, you only have the one FS Server then you haven't needed either for a while. ;-) Regards, Pete

A picture of FS ready to fly? Duh! :-( Have you never even flown in FS yet? Please BEFORE trying to use anything I've written, go for a flight. Follow Microsoft directions for installing and running FS and getting your aircraft in the air. If you are able to do that, then AT ANY TIME during your flight you can access the FS Menu. Just press ALT. A row of words appears at the top. That's called the 'menu'. If you want a picture of what FS looks like when you are flying, look almost anywhere, even on the box I suspect. Windowblinds was mentioned in the manual as being something which can cause problems!!! It was a warning! Pete

I only have fields A B C D Q T (but blanked ------) listed as relevant to what GPSout can do. I you want to see the output from GPSout, grab Portmn from http://www.systeminternals.com and monitor the data as is goes out. I wouldn't know how it does that. GPSout knows nothing about any flight plans. No, GPSout has no idea what your plan is and makes absolutely no attempt to send any waypoint data. Sorry. Regards, Pete

First, he should update -- that version is pretty old now. Current is 3.65. "Normal flight mode" is what I mean by the setting FS ready for a flight, i.e. as if you are just about to fly! NOT in the initial settings menu which FS provides for you to select options for flying. Other programs can't get into that! Once you are ready to fly there's a standard type of Windows menu available in a bar across the top of the screen. If you don't see it, just press the ALT key. The left most entry is "Flights". Towards the right, probably the last, one of the entries will be "Modules". Select that, FSUIPC is in there. Why do you want Windowblinds? That can cause all sorts of problems with FS -- I'd uninstall it if I were you! Pete

Okay. There are three values: WATER LEFT RUDDER EXTENDED WATER RIGHT RUDDER EXTENDED WATER RUDDLE HANDLE POSITION and one Control: KEY_TOGGLE_WATER_RUDDER The first three may be mapped in FSUIPC at 2A78 (double), 2A80 (doublke) and 2aA0 (possibly a 32-bit value). I'm not sure. I don't know if writing to them has any effect. Most likely you have to use the control "Toggle water Rudder", which is presumably assigned to your Ctrl-W. As far as I can see these should be readable in gauges too -- there are token variables for them. I'm rather confused by you saying "... will open and close according to the percentage it got from .." though. As far as I know position type values normally would reflect where the rudder / nozzle has got to, rather than apply a target angle as you seem to think. Of course I could well be wrong. Try monitoring those offsets in FSUIPC (use the Monitor option on the Logging page), see what they do. Then try writing to them from FSInterrogate. Regards, Pete

Good. Thanks. Sorry, I'm not sure what this means nor what you intend to do. I think you may be misinterpreting me? Disabling the joystick in FS is a menu item -- look in the Options-Settings. That's the first thing to check, test and report. If you still have a problem, let me see the relevant parts of the FSUIPC.INI file (the sections entitled [Axes ...] and [Joystick ...]. The FSUIPC.INI file is in the FS Module folder. Good nightI'll pick up any more tomorrow. Regards, Pete

I have no Website. Could you please check the Version numbere and report that instead. So many people say "latest version ..." and it has often meant different things. You'd be amazed at how much time this wastes. Look at the first page of the options, or right-click on the DLL itself and find Properties-Version, or just look at the first line in the most recent Log file. There's no sensitivity settings in FSUIPC, only response curves. Did you make these aircraft-specific? Erwhat did you expect the mixture levers to do in the Lear? If your only axis assignments are through FSUIPC, with the joystick disabled in FS, then when you switched aircraft all FSUIPC assigned axes would stop working, of course. That sounds very much like you still have the mixture levers programmed in FS --- FSUIPC defaults to using FS's mixture levers for reversers as soon as you calibrate them in FSUIPC. You can set those default assignments to 0 in the INI file. But your main confusion sounds like it is arising because you havn't got the axes disabled in FS -- check that the Options menu shows "Enable Joystick" not "Disable Joystick" -- if it shows the latter you will have both FS and FSUIPC using the same levers. You need to either stick to FS axis controls, or FSUIPC ones. If you mix them you will end up confusing yourself. FS doesn't help by often setting zero sensitivity for the CH levers, especially on mixtures it seems. If you want any more help (it would have to be tomorrow now, it is late here), let me see the Axes and Calibrations sections of the INI file. And do re-check the FS joystick settings -- that sounds the most likely root of your problems. Regards, Pete

Questions: 1. What version of FSUIPC, please? If not the latest (3.65) please try that first. 2. In FSUIPC axis assignments are you assigning to FS controls or using the direct assignments to FSUIPC? If the former, then it sounds like your FS sensitivity settings are set to full left for those FA axis controls. Pete

This question was posted as a private message, but it is a normal Tech Support question so I am answering it here: This is because, as clearly documented, the value at 0E8C is only 2 bytes long, whilst you are reading 4 bytes -- the two high bytes are being filled in with the value from offset 0E8E. Only read the sizes as documented. Set your 4-byte Int or Long values to zero BEFORE reading so that the top bytes are known to be zero. Either that, or read them into a short (16-bit) integer, if your language supports such a thing. Same problem. These are also the same, only worse, because these values are only 1 byte long. PLEASE take proper note of the lengths of each value. They are all documented for a good reason! Regards, Pete