Pete Dowson

Ah. sorry. No I don't know how to get that -- wish I could. Pete

No, I cannot intercept the conversation between ATC and AI aircraft. However, yes, of course you can get the current state of AI traffic through the TCAS tables facilities in FSUIPC, at least since FS2004 (not before). Try running my own TrafficLook demo program supplied with FSUIPC -- it shows that state. Documentation for the FSUIPC programmable facilities is found in the FSUIPC SDK. Regards, Pete

Not really. The graphics parts of FS are those which I've never learned anything about nor delved into. That sounds to me like a job for an application, not FSUIPC which is intended as a mere portal. I expect that's because it is treated like the scenery, for which you also need to shut down FS and reload to change. I'm not sure why you think it is actually possible, but even to find out one weay or the other it is going to take some expert in FS graphics (and that's not me) many hours of hacking to get into the appropriate FS modules. If you do this and work out a way to do it, let me know and I'll try to make an interface for it in FSUIPC -- but I think you should be looking forward to FSX now, not backwards to a three year old product. Regards, Pete

Not at present. I am open to suggestions. For instance, if it cannot find FSX (because it is not installed correctly and therefore the Registry is wrong) it would ask the user to locate "FSX.EXE". If it cannot find or create the Modules folder or write the modules there, possibly because something is write protected, it would say so and request the user to rectify matters. The same goes for the DLL.XML file which needs to go into the same folder as the FSX.CFG file -- if it cannot edit or create that the user would need to do it, so there's a reference to documentation on how to do that. Finally, if all goes well, it confirms that FSUIPC version X has been installed and asks the user to check the Read Me file. Confirming the actual version installed may be important as other dependent programs may need that information. Normally, all being well, only the last part is seen. I can suppress any or all of these and instead resturn some sort of error (via what, a little result file?), but you'd need to be able to deal with these things yourself. If it is only success or otherwise you need to know and I suppress the last message, then maybe it would be okay for the others still to be handled by my part? You tell me. I don't know wat you need to do. Note that I cannot rely on other folks' installers doing any of this correctly. They don't even do the simplest things most of the time -- I have always asked for installers to NEVER overwrite a later version, but most inevitably do, and it has created a lot more support work for me over the years. :-( Pete

Please don't get upset. I wouldn't have been particularly upset even if you had been referring to FSUIPC in any case. Folks are entitled to their point of view. In any case, a lot of the adverse initial reaction when I "went payware" was based on a complete misunderstanding. As far as the interfafe to FS was concerned it was and still is free for Freeware, and negotiated for Payware -- just as Adam Szofran's original FS6IPC module was, in fact. The only thing I've been charging for, so that I could afford to carry on developing (and it IS a full time job) are the additional user facilities which user registration provides. Despite this being explained very carefully right at the start, many folks did decide to keep their blinkers on and only see that money was involved, now, whereas, as they thought, it wasn't before. Regards, Pete

You are most certainly getting one of the three parts of the entry wrong. I am constantly surprised at how many ways folks have of mis-spelling their own names, even! ;-) The name, email address (or whatever you used there), and Key must ALL be exactly as notified to you originally when you first got the registration details. If you backed-up your FSUIPC.KEY file, as advised in the documentation, then you could read the details from there to save you having to remember them. The KEY file is a simple text file which you can view with notepad, for instance. Pete

Okay, I didn't need your INI file after all. It was actually a trivial problem, coding-wise, fixed easily (I hope! :-) ). I broke the saving when mending the loading. Sorry. Please download 3.707 now available above. Regards, Pete

Validate the area to be painted. i.e. something like RECT rcl; ... GetClientRect(hwnd, &rcl); ValidateRect(hwnd, &rcl); Pete

Well, possible I suppose, but not so easy -- aileron and rudder trim in FS are very much set-and-forget settings unlike elevator trim which is used all the time and reasonably responsive. I have far less in the way of control to play with. Sorry, I really know nothing about helos so I can't comment. It is really the worst time to ask me for new facilities when I need to concentate on getting the existing ones all working on FSX. Maybe you could do some research yourself -- find a forum where helo experts hang out and chat with them -- and come back in, say, November to ask again if it looks to be a good idea still? Regards, Pete

That is very odd, because this was almost exactly the problem reported in 3.7 which is supposed to be fixed in the updates. Well, not quite. I think the problem in 3.7 is to do with the LOADING of separate calibration settings -- no matter what you saved, next time you load FS it only ever loaded the default settings --- UNLESS the "ShortAircraftNameOk" parameter is specifically set to "Yes" or "Substring". I'll check this tomorrow (a bit tied up today), but meanwhile could you send me a ZIPPED copy of your FSUIPC.INI file, please? petedowson@btconnect.com. Thanks, Pete

The offsets haven't changed. The message area is 3380 with a control word at 32FA. Please refer to the Programmer's Guide, part of the FSUIPC_SDK. Regards Pete

Didnt understood what I need to write into that offset. Any help please? Thanks. Only a Window title, if you don't want the Window called FSUIPC Window, or whatever my default is. Isn't "title" clear enough? Sorry if not. A title is the text in the title bar of a window. This is the (usually blue) bar at the top of a Window containing the program name or something similar. Pete

It checks the version of FSX. It checks that the installed update to SimConnect will actually load one or other of the Versions of FSUIPC4 the Installer contains (yes, there can be more than one). For this it uses Manifest Probing. It then makes sure that SimConnect's XML file which tells it what to load, where to load if from, is correct for this version of FSUIPC. It creates an FSX Modules folder if there's not already one, and it puts the current version of FSUIPC4 in there, but only if there isn't already a later one. It may also install ancillary files, like read Me documents and so on. All your installer would need to do is run my installer. Pete

What, intercepting WM_PAINT messages? Subclass the Window, process the messages. I wouldn't know any other way of getting into Windows other than using the API. What other ways are there? Pete

Like the new one in FSUIPC enabled on the front screen? It operates only for multiline messages. Regards Pete

Good question. It was okay in FS2002 and before. If you find the aswer let me know. I could only do it by intercepting the main FS window WM_PAINT calls and dealing with them myself to stop FS painting over my Window which then redrew (hence the flicker). The easiest way, of course, is to only run in Windowed mode. If you ever find a good way, please let me know. Pete

Is this BEEP an FS sound -- if you choose another program on that PC does the BEEP stop? If it is an FS sound, then the usual BEEP comes from having the gear lever up when the Gear is down. Pete

They just will. Please don't worry. I hope you don't need to tweak them particularly either. ;-) Pete

Really? I suppose, then, it's a good job I don't browse other sites! :wink: (I don't like getting upset). Regards, Pete

Now that isn't quite true. You misunderstand I'm afraid. A rather large amount of code in WideServer.DLL (and *only* in WideServer.DLL, not the Wideclient.EXE part of WideFS) was effectively unnecessary IF the DLL could be integrated into FSUIPC.DLL. So that is what I did. The way FSX works means, in any case, that simply placing a DLL into it (where?) will not get it loaded. It actually needs some rather complicated (for ordinary users) XML file updates as well in order to persuade FSX to load them and integrate them. This is exactly why, for the first time in its 7 year history, FSUIPC comes in an Installer. That installer also creates the FSX Modules folder, which serves no other purpose than accommodating FSUIPC4 and any other Modules which FSUIPC4 is designed to load (PFCFSX.DLL being one such). Just think of WideServer.DLL already being installed (but inactive) once you install FSUIPC4. Apart from that everything else is as it was in FS2004 and before. The same applies to AutoSave.DLL and GPSout.DLL, though these now of course need an FSUIPC4 registration. They won't be needed. But on the other hand I'm afraid I cannot see how this question relates at all to WideFS. Care to clarify? Regards, Pete

There is an "XUIPC" but I've no idea what it does. There's an application interface called "SimConnect".. the new FSUIPC4 for FSX uses it. It has saved me a lot of work, I can tell you! If it hadn't been for this the FSX version of FSUIPC would not have been ready till next year sometime! Hmmm... Where on Earth did you try to install it? There's no way the Demo supports any add-on applications. Please see the announcement at the top of this Forum. I supplied a version of FSUIPC4 and some information about all this here last Monday. I will be releasing an updated version of FSUIPC4 tomorrow (Saturday). All this is for the BETA, not for the DEMO. You cannot do much with the Demo, sorry. Regards, Pete

I'm sorry. I put all the help I can into the User documentation. Did you read that? I'm sorry it is only in English. Maybe someone can help you if you don't understand it? I can answer specific questions, but I don't really see the point of reproducing the documentation here -- there are even pictures there, to help. Have you tried assigning things in FS first? I'm not sure why you are going to FSUIPC especially if you don't understand it? Regards, Pete

Okay. FSUIPC can supply all that. Erbut it outputs to a Serial Port in NMEA format. Surely you would be better off reading the data you need from FSUIPC? GPSout is intended to feed data to existing map programs which are designed to work with real GPS devices. It "emulates" a GPS, using FS as the "aerial". Haven't you read even the small amount of documentation supplied with it? You mean the data sent out by GPSout -- you could use PortMon, a freeware serial port monitor from http://www.systeminternals.com, but if you want to understand standard NMEA sentences I suggest you use Google to search for the definitions. There's a lot of information on the NET and even some decoders. No way at all, the module, like FSUIPC, is ad add-in for FS, not a library for you. If you are writing a program and not using a moving map designed to read data from GPS units, you would most certainly be better off interfacing to FSUIPC for all the information you want. GPSout is only supplying positional and speed data, as a GPS would. All the help you could possibly need is provided in the FSUIPC SDK. What is confusing you there? There are also some packages downloadable from this Support forum -- see above. Just bear in mind that YOU do NOT use any of my DLL's directly. They all run in the FS process only. You interface to them using the interface code provided, including, for FSUIPC, via WideFS over a Network. Pete

Sounds like you have calibrated yout throttle wrongly. Just delete your FSUIPC.INI file and start again, or re-calibrate. In any case version 3.53 has not been supported for a long time -- there have been many versions since then. Please delete it and download the current version if you wish to keep using it. Regards, Pete

Hmmm .... I'm certainly not going that way ... Thanks for the info. Pete