Pete Dowson

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

You would need to set "Log=Debug" in the FStarRC.INI file [settings] section, then run a session. The FStarRC.Log file it produces will be quite big, but it should help me work out what to change -- you'd then have to test any changes for me. but not now, when I come back! ;-) No, that must be something else entirely. Are you using MixW to create two virtual serial ports? Flitemap should not be able to tell any difference between a real COM port and a virtual one -- that's the point. Can you not select the port? Maybe they've restricted it now to COM1 and COM2, though that would make no sense. I did read something someone reported that Jeppesen were dropping the moving map feature from FliteStar/Map in some version. Regards Pete

Yes. Jeppesen, in their wisdom, keep messing about with the print formatting. FStarRC relies on recognising bits of the print output stream so it can extract the data it needs. It cannot do this directly as it is encrypted. I have a world-wide corporate FliteMap, currently at version 9.0. To update to that from the last cost me hundreds of Euros, and the price gets steeper, so I am not willing to update it continuously I'm afraid. Maybe the changes needed to FStarRC are minor, but it is hard to tell and harder to test without the software. There are some detailed logs I could probably use to decide, and I can try to work out how to get them so you can help -- but unfortunately I am on holiday after tomorrow for nearly two weeks. Please write again after September 12th and I'll see what can be done. Regards Pete

I don't have any web pages. If you mean the Schiratti one, that's a page where Enrico Schiratti, of Project Magenta fame, assembles my various FS efforts. I actually distribute the programs to many website managers but they don't all post them. Version 4.156 has been available above (i.e. in the FSX downloads announcement) for over two weeks-- I've just replaced it by 4.16. Haven't you ever noticed the Announcements? They should always be your first port of call, especially if you are a developer. There's more up-to-date developer SDK bits for FSX there too. How do you gert to posting these thread messages without ever seeing the Announcements which occur right at the top? Regards Pete

4.151? That's pretty old. the current formal release is 4.152, since a month ago, and there's a much-improved 4.156 available above which was available since two weeks ago. Actually I've just finished testing this (in 4.156) and I cannot find any problem with it at all. Of the problems I mentioned in my previous message, the true status, having gone into them in some detail, is as follows: This was a result of a bug in the "ApplyHeloTrim" facility, which I've fixed now. If you haven't enabled this then the elevator control via 0BB2 works fine. This turned out to be a bug only in the automatic clearing of the 310A inhibits after 10 seconds or so, unless replenished. Writing 0 to 310A did restore the throttle link from 089A to 088C. There is and was no other problem with 089A -- it basically simply operates 088C unless inhibited. I've fixed the 10 second (approx) clearing of the inhibits now. This wasn't quite correct the way I stated it. In fact, if the axes are assigned directly in FSUIPC to FSUIPC calibration, the inhibits worked fine. The only problem was for unregistered users or those who were neither assigning axes direct in FSUIPC or calibrating axes in FSUIPC. I've dealt with this by automatically intercepting the relevant axes once the inhibits are set in 310A. These three fixes are tested and working here in version 4.16 which will be released before the end of the day. Please keep an eye on the FSX downloads announcements above. I'm afraid I won't be able to do much more, if anything is needed, till I return in mid-September. I am here tomorrow and will answer questions, but there will be no more changes till then. Always ZIP attachments. In any case, judging by the fragment you included with your message you are not logging IPC writes, so I cannot tell what you are trying to do. You have evidently only set the IPC read logging option. Please refer back to the details of the logging I suggested, which also included Monitoring so that the SimConnect exchanges would be seen. Finally, please do not report problems without first using the very latest version of FSUIPC available. I have no idea why you are still using 4.151 which was an interim Beta replaced very quickly by the formal release of 4.152 over a month ago. Version 4.156 has been available in the Downloads above for two weeks. Now you may as well wait for 4.16. Regards Pete

Okay, I've been doing some testing and this is what I've found: WORKING: 1. Writing to offsets 088C (Throttle1), 0BB6 (Aileron control) and 0BBA (rudder control) works fine. I can't make that go wrong at all. 2. Offsets 3328 - 3330, which are read-only (something you appear to have misunderstood?) correctly give the input values for the relevant control axes. 3. The inhibition of axis inputs via 310A works correctly ONLY IF the axes are calibrated in FSUIPC4, and assigned to FS controls (not the "direct to FSUIPC" method in FSUIPC's axis assignment option). NOT WORKING: 4. For some reason, writing to 0BB2 (elevator control) isn't working 100%. I am looking at this now. It may be my joystick control jittering and overriding my inputs, as there really is no internal differences in the treatment of the three main surface controls. 5. Writing to 089A to control the throttle works just like writing to 088C -- until you have inhibited it via 310A. After that, even if it is allowed again via 310A, it doesn't do anything. I'm checking this too. 6. The 310A inhibits don't work when the axes are not being intercepted. To be sure they are intercepted, the axes have to be assigned to FS controls, either normally via FSX, or specifically in FSUIPC4, then calibrated in FSUIPC4. This is an oversight on my part, a result of recent changes in this area. Hopefully all three of these problems should be easy enough to fix, and I am working on that today. If I succeed these fixes will be in FSUIPC 4.16 today or tomorrow, but otherwise they won't be fixed till mid-September (i.e. in about two weeks or so). Please confirm that the problems you are observing coincide with the ones I have identified. I am still starved of any useful information from you, so if I as missing the point I'm afraid your problems will not be fixed for some time. Regards Pete

No, because FSUIPC doesn't use any redistributables, at least nothing not already used by FS itself. Ahnothing to do with any redistributables. Please see viewtopic.php?f=54&t=64092 I cannot solve it unless someone can find facilities in Windows to do sidebyside probing without generating errors (which are no such thing). I will continue to press for such things from my side, but you do your bit too if you don't like it -- complain to Microsoft's Windows developers. Pete