Pete Dowson

Okay. It looks like you did not actually follow the instructions in the Installation section of the User Guide correctly. In order to register correctly under Vista you have to right-click on the FSX icon (or the FSX.EXE) and select Run As Administrator. Please check the documentation again. I think you need to re-register in the correct way. It is a problem on Vista where only "elevated Administrators" can get Registry entries made. Pete

Unfortunately you have shown me a continuation log: so I cannot see the checks made at the start. Can you show me a normal log please? Just load FSX then close it. That will do. I see that you obtained your Keys last Novemberwhat has taken so long to report this problem? Regards Pete

Sorry, there's nothing in FSUIPC or WideFS which will do that. Are you sure you haven't got FSCommander or something trying to control the aircraft, and not checking correctly for when it is paused? If not FSCommander, you have something affecting FS's values. Pete

You need to use the Lat/Lon to find the nearest airport from a file listing all of the airports with ICAO ID and Lat/Lon. There's no facility provided by FS or FSUIPC to tell you "nearest airport is ....". Sorry. My freeware program "MakeRunways", available on the usual download place and above will generate a suitable file -- the most applicable one is probably "airports.fsm" which is a binary file with all the airports in an array of 18 byte structures: struct { char szICAO[4]; float fLat; float fLon; WORD wATIS1; WORD wATIS2; WORD wATIS3; }; The ATIS values are BCD frequencies capable of giving weather information, 0x1234 meaning 112.34. The airports are sorted into alphanumeric order of ICAO id. Regards Pete

Does the FSUIPC4.LOG file show anything useful (show it to me if you like)? You'll find it in the FSX Modules folder. If you enable IPC read and write logging (in the Add-Ons, FSUIPC options, Logging tab) then I would be able to see if anything is reading the traffic data. Regards Pete

Only by using my GFdisplay program, which is freeware provided to program GF unit display capabilities. FSUIPC's support for GoFlight is only as a button/switch input capability. It doesn't know anything at all about displays. It is a simple extension to its EPIC, PFC and general joystick button support. Regards Pete

You'd have to read the Latitude/Longitude and look up a list of airports. You can set the GMT time using the Zulu time offsets -- please see the FSUIPC Programmer's guide. "Zulu" and "GMT" are the same times. Regards Pete

As Announced above, I was on holiday till today! Pete

3.71 is well out of date and unsupported. "Stop sending"? Uh? I think you are misunderstanding something. To enable APP mode, you write a 1 to 0800 or, in fact, 07FC because of how FS works -- but best to stick to 0800). To turn it off you write a 0 to both 07FC and 0800. You should not be writing anything continuously, and "stopping" it doesn't do anything. If sends no commands at all, int interacts with the FS AP internals. Please please read the notes, in the third column of the programming guide. See when in 0800 is says "See the note above, for 07FC". Did you read that? Pete

If you don't have more that one PC, WideFS is of no use to you whatsoever. Only offloading any FSUIPC client programs to relieve the FSX PC, and also providing that much more potential screen space. My own cockpit needs 8 PCs, all running WideFS and used for different applications with their own instrument displays and so on. No, none at all. And FSX supports multiple "players" on a LAN in any case, all on its own -- WideFS is not involved at all, and in fact cannot be used in such a setup. Regards Pete

If they have suitable gauges to do so which work in FSX, yes. It isn't FSUIPC4 which does this, but gauges written to either read the data from FSUIPC4, or obtain it directly from FSX. No.

They are not actually simulated in FS at all, hence no offsets to control them. Regards Pete

No, sorry. That's an area which isn't exposed via any usable interfaces I know of, other than the menus, and it hasn't been hacked. Maybe, if there's a general demand, I can look at it in the future (but for FSX and later, by then), but I've never been asked for it before in the 7+ years of FSUIPC. Regards Pete

That doesn't make sense. There are no bits 50 .... 53. Let me look ... Ahwhere are you reading the above? In the on-line copy of the PM offsets list it clearly says, in bold "(Values, not bits!)" for offset 04F4. No where does it say "04F4 and Bit 2, and state to change the value, not the bit for the function below"! None of those are appropriate as that offset works by sending it a value. You cannot "toggle" anything, as when PM has seen the value it will clear it -- and in any case some other of the many functions may have been used by then. You can do either, but really only by using flags and conditional button programming, editing this in the FSUIPC INI file. Take a look at the Button Programming part of the FSUIPC Advanced Guide. Get back here if you still have questions on that. There is an alternative which might work and which would be a lot easier. The offset 04F2 is used to send commands to different parts of PM using a set of pre-deined codes. I notice this one listed (near the back of the document): TFC K047 (TCAS) So, you could first try programming the button using Offset Word Set, with parameter 47. Regards Pete

One or other of your FSUIPC or WideFS keys for FS9 is invalid. If you want me to check them, Zip up the FSUIPC.KEY file and send it to me at petedowson@btconnect.com. Sorry, I've no idea about that one. Do they have an update for FSX? Best check with Elite support. Regards Pete

This isn't really a WideFS problem, as WideFS doesn't use such access methods -- FS Commander is presumably looking to scan the FS scenery files. With Vista I don't think you can share the system drive as such. I think you have to enable the actual FSX folder to be shared. You would give it a short share name as well, like "FSX" so it would be referred to by \\Ksfash-83\FSX on the client. Regards Pete

Rev button? What's that, please? Assuming you have a prop loaded (the mixture wouldn't be used in a jet, not as such anyway), then you should be able to calibrate any lever as Mixture, assuming it is so assigned, either in FS or FSUIPC. All FSUIPC's calibration does it set the extremes (full lean to full rich) to the values you tell it to when you click the "Set" buttons over the appropriate columns. It then spreads the intervening values appropriates between. It really is that simple. If the incoming values a jumping about then it is either a broken pot or you have some other driver in there which is doing this. Take a look at Windows' own Game Controllers calibration. Regards Pete

Sounds like quite an old bug which hasn't been seen for a year or two. Are both your Radar Contact and FSUIPC installations completely up to date? If not, update them. Regards Pete

Yeah, I hate Vista because of its way of preventing you to do anything it thinks is "wrong". There must be a way, and I hope someone else can tell you how, but I have a feeling you may have to treat it like a broken driver, and roll back Vista using restore to a point before you installed FSX, then install it again. Otherwise I think you may need to contact Microsoft support. Regards Pete

Strange, as all it does if regurgitate the keys it saw pressed. I'll check that here. Glad you solved it anyway. Regards Pete

ZIP them first in any case. Send to petedowson@btconnect.com as an email attachment. Looks like you didn't put the FStarRC.exe and FStarRC.dll into the correct folder, the same one as Flitestar.exe and MFC42.dll? There are no changes in Version 2 which affect the initial hooking of those routines, none at all. Regards Pete

The 4-throttles page only works if you either assign your throttle levers to the separate Engine throttle controls, or, with one throttle lever, check the "Map to 4 throttles" option on the main throttle page. Obviously if your throttle is working on the first page you've not done that! This is all clearly explained in the User Guide, so it may help if you reviewed that. Regards Pete

FSUIPC 3.65 is a long time out of date and unsupported. Please use 3.75. I cannot undertake to support old versions. Yes, sorry, but this tells me nothing useful. I don't need to know about the actual hardware, I need to know how you are trying to control the radio frequencies. How are you doing that using axes? I've never heard of that being done before and I have no idea what you are doing!? After all, the radio frequencies are discrete values, but analogue axes are continuously variable. Maybe the reason you can't get to 50kHz increments is that your pots don't have fine enough resolution? Regards Pete

Can you tune them correctly in FS using mouse or keyboard? If so, then it's the same through FSUIPC. Unfortunately I can't really help further as I have no idea how you are connecting these pots (what are they doing, what do they look like to FSUIPC? Buttons, keys, axes, hats or what? How are you programming them? Have you written a program to measure their resistance and then write to FSUIPC offsets, or what? Please tell me a little more and maybe I can help. Also, please always state basis things such as FSUIPC version and FS version (FS98, FSX, ...?). Regards Pete

Oh, it does occur to me that I do have a later, unreleased (as yet) version of FStarRc -- version 2.00. It has a load of extra undocumented facilities to do with Radar Contact 4 and 5. The reason it is unreleased is that I've simply not got round to documenting these additions, and no one has pressed me for anything. however, there is a remote possibility that it may work better with FliteMap 9.3. Give it a go anyway, and let me know. Regards Pete FStarRC_200.zip