Pete Dowson

It never arrived! One copy came to the "private" part of this Forum, but as I said there, I don't like using that at all. No. I did hear of someone making a stab at a Linux version of WideClient (or it may have been an Apple O/S version -- it was a long time ago), but I never heard of it coming to anything. There are no specifications of documentation I'm afraid, you'd have to derive it all my monitoring the packets. Quite honestly you may be better devising your own methods. Sorry, no. There's only the current version. Use that with FS98 too if you like, though you won't get many facilities -- FSUIPC was designed originally for FS2000. It wll run on Win98 though (try to make sure it is Second Edition). Avoid Windows NT. I don't really think your project is terribly viable in any case with FS98 unelss you do some deep digging into FS98's innards. Use Adam Szofran's FS6IPC.dll, not FSUIPC, that saves you paying and gives you almost as much -- for FS98 FSUIPC offers only a few extras like Logging. It certainly allows you to receive data from FS. I don't know if you get any control the other way. I only had a brief look at it a year or two ago and didn't really think it was a lot of use. But don't take my word for it, take a look yourself. Regards, Pete

Have you got the Technical page option set to "fix" panel windows? If not, then FSUIPC doesn't really have anything to do with this, and it doesn't even know you are doing it. Just because it occurs with FSUIPC installed and not otherwise doesn't necessarily mean it is the culprit. Pete

You need to make your joystick work without FSUIPC first. FSUIPC is not a joystick driver, it is only useful for more precise centering and null zone setting. You need to calibrate your joystick first in Windows, then make sure it is assigned correctly in FS. If you've already tried to set it up in FSUIPC, go to the FSUIPC Joysticks page and reset it, so that FSUIPC has nothing at all to do with it. Now make sure that it works well in FS. When you have a properly working joystick, only then consider using FSUIPC for making the final settings for a good center zone and balanced left/right movements. Regards, Pete

Well if emulating keyboard actions was easy you might be right, but in the end I think you'd find it more problematic, a lot more programming, and still quite unsatisfactory when you've done it. The direct FS controls route is far preferable. Regards, Pete

This is correct for the Sqawkbox version 2.3, which is named "Squawkbox.exe" and has a Product Name (in the Version Information) of "Squawkbox 2.3" and a Company Name of "None" in the same display. At least, I think these were the details I was given. Any other version would need a different Key. Regards, Pete

Ah, you mean rather than program the keys to give specific FS controls in your own program, perhaps via an INI or CFG file, you are going to generate FIXED keypresses instead and send them to FSUIPC? Really this is the same as sending keypresses to FS. The FSUIPC Keys programming facility intercepts keys going to FS's window. The facility to send FS key presses, at 3200, would do this. But it just seems a bit, well, circuitous. But by all means try it and see. Really I think you'd be better associating an FS control (with parameter where needed) with each of your buttons, and sending that by the facility at 3110. You only need a list of button=control numbers in your CFG file or whatever. Messing with keypresses can get a bit fraught, since you have to deal with KEYDOWN, KEYUP, and combinations of keys can get horrible. Timing problem can arise, interactions with the real keyboard, and shift states can get stuck. Regards, Pete

As stated in the Announcement, right since before FSUIPC 3 was released, you apply to me for details on petedowson@btconnect.com. Regards, Pete

[quote name="in_04 I don't know if this feature is free for unregistered FSUIPC users? So if I release my program as freeware with FSUIPC key' date=' can the user set the values or must he have a full version?[/quote] All the facilities in the weather tabs, along with those in the technical, joystick, buttons, keys and hotkeys tabs, are USER facilities and accessible when the user registers FSUIPC. Please see the details in the announcements and documentation. Or download a copy of FSUIPC 3 and try it, both unregistered and registered, and you will see the difference. But I thought my documentation was clear enough on this? You can control the FS visibility in FS2004 via the FS98 interface, or the AWI, or the NWI (new for FS2004). FSUIPC provides MORE facilities for weather control in version 3, not less. But none of this has anything whatsoever to do with the facilities offered to the user in the Tabs of the registered version. Regards, Pete

Sorry, I'm not sure I understand. What is it you want to do in your program -- i.e. what is the purpose? If I provided anything along such lines it would interfere horribly with the manipulations FSUIPC is making. Pete

By "keypress routine", do you mean the facilities to program those to send FS controls? If so, why not simply send the controls instead (offset 3110). Alternatively if you want to send keystrokes to FS, use offset 3200. If these are then re-programmed in FSUIPC they will be intercepted on arrival again, but this seems an odd circuitous route. Pete

FSUIPC does not move your aircraft. There is no code in it to do any such thing. It sounds like you are using some application program which is moving the aircraft. What programs are you using? You say "nobody from my airport see me ( pilots or ATC )". Does this mean you are flying on-line, perhaps using SquawkBox? You don't say! If so, maybe you have not Registered FSUIPC and are not using an access key for Squawkbox, so the program cannot get any information from FSUIPC at all? Regards, Pete

The nearest thing to this already implemented would probably be Project Magenta's advanced Autopilot, built into it's MCP. It has two modes, one using the FS autopilot for some things, and another where it tries to do the whole thing itself. Of course the inter-machine transmissions are performed by WideFS in this case -- the MCP can be run on the same PC as FS, or on another. WideFS provides the remote interface to FSUIPC. I think all this is perfectly feasible for control of aircraft where a small time lag (latency) is not detrimental to the flight. You would find this probably a bit too slow for jet fighter operations, or even probably Extra aerobatics. But for airliners and some GA aircraft you can do it. If you are not operating as an Autopilot, but more "fly-by-wire" there are even facilities in FSUIPC for disconnecting the user's flight controls, reading his values and acting upon those. Regards, Pete

Could you give some more practical, technical, details of how someone can (a) check this, and (b) turn it off? Even if the details are very specific to the one mobo, it may still serve as an example which I can add to the WideFS.doc. I am looking to release a minor update next week in any case, as I have changed the timings to stop WideServer detecting "stoppages" in FS so readily -- it appears these can happen much more easily in FS2004 and they currently make WideServer restart the service too often. Thanks, Pete

Offset 060C had it in FS98 and FS2000, but I've not had that one mapped since then. I don't know if I would be able to find it or not. Pete

There's no cure. Just don't move it around. It is either this, or having the dialogue flashing all the time. FSUIPC stops the flashing otherwise caused by FS's use of DX9 by preventing it repainting its screen whilst you are in the dialogue. There's no other way I ever found. Why keep moving it around in any case? :o Pete

It only does this if you have any of the weather filter options set. This is because most of them do operate on the "global" weather setting in FS -- the one used at any WX station without specific weather -- even though you won't normally see the effect. I'm changing this so that it won't touch native FS weather unless you select an option for it to do so. This will be in version 3.05, which I hope to release by the weekend. Meanwhile, you can avoid the problem by selecting "minimum weather defaults" in the first FSUIPC options page. Actually "normal defaults" may also do it. But either way, please note that these reset other options as well, like some of those on the Technical page which you may wish to re-select afterwards, and the Hot Keys too. Regards, Pete

Nothing. PFC.DLL has been doing that since version 1.50, as I pointed out. I have no other possible solution I can pursue. If it isn't working it looks as if you have no choice but to enable it manually, or try to resolve it with PSS. If there is a programmable way to do it which I can add to a future version of PFC, I will consider it, but PSS aren't notable to date for making their panels programmable. Perhaps you should ask them about it? Let me know if they suggest a decent solution. Regards, Pete

Sounds like you need an update from Richard, as you are correct, it has been issued with an access key. Have you gone to the source with this query? This isn't really the correct Support Forum for application programs. I have so much to do supporting my own programs already! :) If there is any problem I would expect to resolve it with the author. He and I are on good terms. Regards, Pete

FSUIPC is the interface module for Flight Simulator which programs like your EFIS uses. It needs installing first. You can get it from http://www.schiratti.com/dowson. Please look at the User Guide inside the ZIP> FSUIPC is most certainly compatible with XP Pro, and also XP Home, Win2000, and Win98 (and, yes, even the ill-fated WinMe). It is not compatible with Windows NT, that's all. EFIS is an application program which should be completely operating system independent as far as I can see. I really doubt whether it uses any techniques liable to render it sensitive to O/S changes, but since it is several years old there's no guarantees I'm afraid. Regards, Pete

Why such an old version? Before FSUIPC 3 was released the only supported version for about 5 months was 2.975. 1. Users who register their copy of FSUIPC 3 can use your program in any version of FS. If they don't register then your program won't work without an access Key. Please see the announcements at the head of this Forum. 2. I have tried very hard to make sure that the interface provided for FS2004 is a superset of that provided for FS2002, just as I did for FS2002 before and FS2000 before that. However, I cannot test everything and there could be some differences depending on what your program uses. If there are differences I try to eradicate them as soon as I know, but I am dependent upon people like you telling me. There are just too many variables, many of which I don't even necessarily understand, for me to undertake full testing of every possibility myself. Therefore it is you who must test your program and tell me if you find anything amiss. Regards, Pete

There is no support for APL-encoded adventures in FS2004. Microsoft started this withdrawal in FS2000, continued it in FS2002 -- but FSUIPC "patched" up the tables in the interpreter to keep some FS98 compatibility. However, there is not even an interpreter in FS2004. This at least accounts for "Real ATC". I don't know "BSATC" but presumably that also is based on APL adventures? Regards, Pete

This was reported some time ago. It's something very odd about the way PSS programmed the reverse. I think I got around it in the in the PFC driver by actually sending the same control as F2 when reverse is engaged. This was done back in version 1.50, as noted in the History part of the PFC documentation: The current PFC.DLL version is 1.55. Try that. If you are using that but it still doesn't work then I'm afraid it's over to PSS. Sorry. Regards, Pete

Version 3.04 is the only current and supported version of FSUIPC for FS2000, FS2002 and FS2004 -- even FS98, CFS1 and CFS2, if anyone uses it in those for anything. It is enough work maintaining one version without several separate parallel versions! I'm releasing Version 3.05 soon. Then it will be the only version :lol: Regards, Pete

This is basically Chris Brett's EFIS98 program, as released for FS98 originally, with some updated data I think. It is probably compatible with FS98 through FS6IPC and FS2000 through FS6IPC as well. In order to make it run with FS2000, FS2002 or FS2004 through FSUIPC you have to install it as if it it running on FS98. I don't remember the details now, sorry -- I haven't actually used it for about three or four years. Interestingly it was the program which got me to write WideFS, so I could place its ND screen on a separate PC. Chris sometimes looks in here and should be able to help, although I think the version you purchased may have been one on which he was in dispute with the publishers. Other erstwhile users may be able to chip in too, but I don't think you'll get any guarantees. It was several years old when Papa Tango re-packaged it. Regards, Pete

Yes, and no, in that order. Originally I planned to release FSUIPC 3 on the 25th July, and the SDK one week later. Of course, incomplete, only containing what I knew about FS2004 up till then. Events have thwarted me. I've not even started on it yet. I've been, if anything, busier since releasing FSUIPC 3 than in the desparate few weeks between getting FS2004 gold and making things more or less work. So, sorry, no date. Everytime I quoted a date I've missed it. If there's anything not obvious is the current SDK, ask me. Regards, Pete