Pete Dowson

[quote name="iflyskyhawks On three separate occasions' date=' FS9 locked up with a black screen and a mouse cursor flashing between hourglass and mouse pointer....Not to place blame or insist that FSUPIC is the cause. In my situation, it was the only variable that had changed.[/quote] Yes, but tthere is nothing FSUIPC is doing or can do about it. Only the video drivers can do such things. Sorry. Regards, Pete

[quote="Les Parson 17820 Trying TCP/IP host "CC1047850-D" ... 17820 Error on client gethostbyname() [Error=11001] Host not found Ah, that's an easy one. Your Windows system running this client does not know of another PC on the same Network and in the same WorkGroup by the name of "CC1047850-D". Use Windows Explorer, find out the name of the Server, the one you can access through Windows Explorer, and change the ServerName in the WideClient.ini file to match. Regards, Pete

The only change between 6.02 and 6.10 is a minor one, in WideServer only, to stop it restarting the services to all clients everytime it detects a "stoppage" in FS (eg a visit to the Menus). You can make it behave just like 6.02 just by adding "NoStoppedRestarts=No" to the WideServer.INI file, in the [Config] section. The fact that you yourself proved that it was not 6.10 ("I then returned to 6.02. The same problem") shows that whatever has changed, it is certainly not the WideFS upgrade which did anything to affect this. I suggest you look for another cause. Something has changed. Maybe your Network card has failed. I'm afraid I can't diagnose your system from here, but I may be able to tell you a little bit more based on the error messages you are getting in the Log files. Regards, Pete

No, sorry. We all wish to be able to do that, but there is no way known to get into the FS ATC system. Perhaps one day Microsoft may release some sort of toolkit, but I doubt it. There isn't even any way to control AI traffic either. I think there's probably a way to delete it, but nothing else. Regards, Pete

I am not involved in the selling loop at all. The professionals at SimMarket deal with all of that. You need to write to Customer Services at http://www.simmarket.com (or use the "Problem" facility they provide for this). Regards, Pete

Thanks. I'll add these notes to the next update for WideFS.doc. Unfortunately it's just missed one update, but I did hint at it there. :) Best regards, Pete

Sounds like it might be something to do with video drivers or your AGP settings. Try going to FS's Options-Settings-Display-Hardware, and setting "render to texture" off. If that fixes it, then it's some sort of AGP problem, an interaction between DX9 and your video drivers or their AGP settings. Regards, Pete

No, but the freeware program does need a key. Since I don't posses all possible freeware programs (and don't want to) I cannot possibly generate them for everyone just like that. I need all the details. For this sort of thing, even if it is freeware, I'd prefer that the Author or someone responsible applied. It may not be the author's wishes that an earlier version of a product is enabled for use on FS2004, for instance, especially if he's preparing a new payware version. You see my point? Please check with the author first, and state that you have done so and that it is okay in your application. Then, check the "sticky" thread up above somewhere listing FreeWare programs and their keys. Either write to me at petedowson@btconnect.com, or add a message to that thread with all the details I need for this freeware program -- program name (.EXE), and, from the Version Information, the Product Name and the Company. If one of those is missing I can make do with the File Description instead. But I need at least two of the three, and I need them EXACTLY, character for character. Remember to say which is which. Regards, Pete

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