Pete Dowson

If you have registered FSUIPC successfully as a User, you do not need to register any applications at all -- they will all work anyway. That is why the Application Registration button disappears -- it has no use for you! Also, when FSUIPC and/or WideFS is user-registered, the button labels change to say so and grey out to indicate that they are disabled and don't need to be pressed. You never need to bother about any of that. Just run your programs. Regards, Pete

Have you downloaded the FSUIPC SDK from http://www.schiratti.com/dowson? Inside there is a programmer's guide which lists everything you need to do whatever you like with NAV1, NAV2, COM1, COM2, ADF1. ADF2 and the Transponder. Regards, Pete

Ahwell, I'm glad things are coming together again. I think we all go through these horrible experiences once in a while. Good flying! Pete

Yes, of course. Several programs use that facility already -- Radar contact and Flight Deck Companion, to name two. FSUIPC's user facilities include both special FSUIPC-implemented HotKeys (on the Hotkeys page), and the facility for FSUIPC to assign keystrokes to a larger list of FS controls than FS's own facility, as well as special controls for Project Magenta and WideFS (on the Keys page), but both of these facilities are end user facilities used via the Options dialogue, not facilities for programs. Please download the FSUIPC SDK which you will find on http://www.schiratti.com/dowson. The programmable hot key facilities are explained in a section entitled HOT KEYs for Applications and involves the setting of parameters into a table at offset 3210. Regards, Pete

64-bit number, you mean, not string. In FS interrogator you get the high part converted and this gives a good approximation. You can do the same in the lower part and add the two together. The only thing to be careful of is the sign -- the lower part is unsigned, so you add it to the high part if the high part is positive, subtract it if negative. Depending on what language and compiler you are using it may support 64-bit integers in any case. They may be called "long long", for example. Check the data types in your language reference. It would be easier for you to show us what you are doing, then someone familiar with the language you are using can help. You haven't even mentioned it. :) Regards, Pete

If you download the FSUIPC SDK from http://www.schiratti.com/dowson you will find a Programmaer's Guide which lists all the information which can be obtained. You could write a program to do something of the sort, via FSUIPC, but I don't know how smooth you could make it. Certainly you'd need some sophisticated code to interpolate values between GPS readouts, which are typically once a second or so. Regards, Pete

Ah, good! One more item to tick off on my long list! Thanks, Pete

If the Network driver doesn't tell the server that the connection has closed (as it really should do, but I have noticed times when it doesn't), then WideServer will only notice after a timeout period -- I think it is set to something like 20 seconds by default. It does no harm, I wouldn't worry about it if I were you. There are other causes of the multiple connection indications too -- these are described in the WideFS documentation. Regards, Pete

No, it does use the program name as well -- there are three elements: program name, and two parts of the Version Info (which are normally Product Name and Company Name). If any of this is changed, the Key won't work. One can of course get around this by registering FSUIPC as a User. Regards, Pete

That looks like a really neat setup! Must be real fun to fly! What do you do about the display of the scenery -- is that projected or do you have a big plasma screen? Regards, Pete

Yes, something has evidently been corrupted, but identifying what can be a very difficult process. When you do re-install, after uninstalling FS, don't forget to delete the stuff it leaves -- all your add-ons, created flights, and so on. It only uninstalls what it installed, but your corrupted data MAY be in one of the files created or added later. Regards, Pete

Well I suppose you can read/write the .PLN file. I think that's what most programs do. What Flight Navigation software? If you mean the Microsoft FS team, then, yes, but only as a Beta tester. If you want to make suggestions for future versions of FS, then now is the time to do it. The feature lists for each new version tend to get frozen a good 18 months before scheduled release. Check the Microsoft FS web site(s), there should be a way of sending messages to them someplace. I looked at a much earlier version, hoping to adapt it to my cockpit requirements, but found it too inflexible at that time. And as a Windows developer I ran into something of a brick wall with Austin, who was determinedly Apple-centric back then. I expect it has all changed considerably now, but I have too much invested in MSFS to change horses now, and not enough time to ride more than one. :wink: Good luck! Regards, Pete

It isn't the panel but the Gauge that needs the key. Please check the FSUIPC.LOG to see which gauge needs it. Most existing freeware TCAS gauges are already listed as far as I know. Regards, Pete

It sounds like something else has got corrupted. Possibly your FS9.CFG file, or a weather-related file. Try, as an experiment, removing the FS9.CFG file (or renaming it), so that FS makes another. Then, in the initial menu do NOT select an existing Flight but make a new one. If that fixes it then one or more of your Flight or Weather files are corrupted, or the FS9.CFG file contains something suspicious, or both. If it makes no difference then it gets more complicated. It could be something in the Scenery files, the Sounds files, or the Aircraft files -- but really selecting a complete new flight and starting with a complete new CFG file should eliminate most of those as possibilities. In the end a re-install of FS may actually be quicker than trying to find the specific cause. Regards, Pete

The IAS there is in 1/128ths of a Knot. In C or C++ you can simply read the 4 bytes into an int then convert it to a double (same as FS's FLOAT64) by dividing by 128.0. e.g. assuming you read it into nIAS, then simply: double dIAS = nIAS / 128.0; In C/C++ experessing the number 128 as 128.0 automatically makes it a double. Pete

No, sorry. All I managed to find is the GPS stuff mapped to offsets 6000 onwards -- you get the previous and next waypoints only there. No, they don't help at all. The data is found by hacking through the code. I use a disassembler (IDA Pro) and a powerful debugger (Soft-Ice) to track things down. It takes many many hours and often leads nowhere. By the way, the "offsets" are mostly not memory offsets into FS at all. Regard them more as tokens for the data. FSUIPC maintains the illusion that these things are all in memory ready to read and write simply to keep faith to the original interface which was actually like that in FS98. Since FS2000 things have been moved all over the place, and often FSUIPC has to call procedures or follow pointer chains to get the data. It tends more and more to be private data in C++ type class objects. This is even more the case when you write -- most writes are really just commands for FSUIPC to do something to something somewhere deep in FS. Regards, Pete

Check that it works using a Shutdown Hotkey in WideServer. For instance, I assign Shift+Ctrl+E there. Pressing this key combination in FS then shuts down all the Clients. All it does is write a special value to an FSUIPC offset, which is exactly what PM's CDU facility should do. I don't value the MCDU, only the Boeing CDU, and that certainly works fine. As far as FSUIPC and WideFS are concerned, you only need the parameter you've mentioned in the WideServer.INI and each WideClient.INI files. This goes into the [user] section -- check that. Then check that it works by assigning a HotKey for it in wideServer's INI. If that's okay but the MCDU still doesn't do it you will need to contact PM support. Regards, Pete

Maybe the sensitivity is turned way down in FS. Try putting it back up to full for that axis. Also try adding stick_sensitivity_mode=0 to the [Controls] section of the FS9.CFG file. It changes the way all axes are handled, to make them linear rather than time-increment based. I find it makes them all far easier to calibrate well. Regards, Pete

Ah, sorry. The facility was only added in 3.202 and the SDK isn't updated yet. Here's the proposed entry for offset 3365: Regards, Pete

Did you not read the Notes for the most recent FSUIPC Release (3.202), viz: "A flag is provided in the byte at offset 3365 which indicates when FS is effectively frozen because of menu access or modal dialogue action. Full details can be provided to those who need to use this before the next SDK update." Regards, Pete

I don't know VB, but it looks like you are setting the variable Master to FALSE when it is FALSE. Why? Where do you change the Caption to "OFF"? Regards, Pete

Oh, drat! Is that typo still there? Sorry. It should be "PGRMZ". The P is for "Proprietary" and "GRM" is for Garmin. There are other PGRM sentences too but the Z one is the only one I've implemented -- I've no information on others and they don't seem to be needed in any case. Regards, Pete

Sorry, I don't know which fuel dump gauge you are using. I have only heard of the TC fuel management gauges -- I believe Tom Corson, the author, has revised these recently -- the FS9 version is either called TC.FuelStatusCG2K4.gau or TC.FuelStatusPR2K4.gau. I'm not sure what the differences are. But he releases them as Freeware and he has got the FSUIPC access Keys for them. Regards, Pete

Not only that, but it would slow things down too -- the WM_PAINT messages would keep repeating very frequently because the painting is not being done. Windows isn't happy until you've told it you've painted the area which it thinks needs it. That's what the Validate does -- tell it you've dealt with the area in question. Regards, Pete

I am certainly only hooking the main (FS98MAIN) window for this. Maybe you weren't validating the Paint request? Try only hooking the main window but validating the WM_PAINT, thus: { RECT rcl; GetClientRect(hwnd, &rcl); ValidateRect(hwnd, &rcl); return 0; } Regards, Pete