Pete Dowson

So, I don't understand then why you asked " Is there a way to export to FSNavigator?", which was where we started on this loop? Anyway, I've no idea what format PMDG uses. Surely they can read FS .PLN format? It's a bit short-sighted of them not to support the format folks can have universally. Regards Pete

Doesn't FSNav read FS PLNs? I've never been asked to support anything for FSNav before. How were you using FStarRC before? Pete

From what? FStarRC? It produces FS format PLN files as well as RC's APL and Squawkbox & PM's SBP form. If you mean FSBuild, sorry I don't know it. Pete

So the change is from 9.4.7 to 9.5.2.1? That's odd -- such a seemingly minor step ... ... yet it looks as if they'd completely re-compiled it all with some newer versions of the standard Microsoft libraries. MFC42 and MFC71 contain the routines I hook into to trap the printing output so I can get the plan data. I'm afraid it is going to have to wait till I can update my copy. I've taken the plunge -- the cost is nearly 500 Euros! (Groan! :-( ). Pete

FStarRC would save a log file too. You are using the latest FStarRC (2.10) aren't you? And using it to start FliteStar as per instructions? What was the previous version of FliteStar which it worked okay with? Looks pretty much unchanged, although mine doesn't have 2 decimal places for fuel and distance values -- is that new or an option you've set? -- nor seconds in the timing, only hours and minutes. How does the printed Report compare with the last version you had FStarRC working with? You could setting "Log=Debug" in the FStarRC.ini file, then rerunning and printing a typical report. That'd produce a huge log. ZIP it and send to petedowson@btconnect.com. Can't promise anything though. I might have to wait to see if I can update my copy without too much expense. It'll be much more than that -- mine is a Worldwide Corporate FliteMap version (takes GPS inputs and operates as a moving map too). Last time I updated (Jan 2008) it cost a few hundred Euros I think. Regards Pete

I'm using 9.3 on Windows 7 (64-bit) with no problems in FStarRC. Jeppesen keep changing things to mess me up, but not usually on minor increments. What exactly happens? Can you show me an example of the Report output format? FStarRC is dependent upon scanning the printer output so that's relevant. I'm making inquiries now about updating my copy -- if it isn't too expensive I might get it. That might be the fastest way to sort it out. Pete

Show me the Install log, and the FSUIPC log files -- you'll find both in the FS Modules folder. And check to see if there's an FSUIPC.KEY file there. If so, look inside it and check the details (don't post it here). Reinstalling FS or FSUIPC won't help. Regards Pete

I've seen that mentioned before. These threads might help: http://www.simforums.com/Forums/topic34526.html http://www.simforums.com/forums/error-1402-installing-sp1-for-fsx_topic33125.html Regards Pete

There is only one cause of that -- an invalid, possibly pirated, registration key. Check your computer's system date. If it is wrong and pre-dates your registration it will make it look illegal. Also if you registered this year but are using an old version, it will look illegal. Check that it really is 3.98 or later. Regards Pete

Sorry, that is too old. Please update to at least 3.98. Mouse macros are not usable on hardly any parts of any of the default aircraft as MS did not use their SDK when writing the code. Regards Pete

Okay. The reason for the problem is clear. You are using an original, buggy, un-updated install of FSX: That's the original FSX release of September 2005. However, at some stage you or one of your add-ons has installed the SP1 version of SimConnect: FSUIPC4 likes to use the latest it can find (they work whereas the original doesn't, at least not well), so selects SP1. Unfortunately that version of SimConnect is not compatible with the origiinal version of FSX: FSUIPC tries then to revert to the older, buggy, version, but FSX is now rather bitter and twisted by it all: The answer is to install the SP1 update for FSX. I'd also recommend that you go further and install the SP2 update too -- it is far better. But run FSX at least once after installing SP1, then re-boot before installing SP2. Regards Pete

Correct. In fact with some add-on aircraft there's no way to even dig out the information you'd need to save, and certainly no way to put it back in on re-load. Regards Pete

In the FSX Modules folder there will be an Install log file, and possibly an FSUIPC4 log file. They show exactly what is going on. Please show me them. Also please always state version numbers -- make sure you are installing 4.60 or later. Nothing earlier is supported in FSX. Regards Pete

Really? RC has all its frequencies in its data files. MakeRunways generates these from your scenery, but I'm not sure offhand whether RC version 4 uses the frequency files it generates or not -- I know the future RC version 5 does, but I think RCV4 pre-dates that facility in MakeRunways. Probably it's frequency data is simply a little out of date. How do you define the "wrong frequency" in any case? When you look at the charts for airports there are so many alternatives for many of the ATC facilities that it could choose one which isn't included in the FS scenery data. It shouldn't matter provided you tune the one in you are told to, as in real life. These days aircraft are equipped for closer spacing with their radios, and many control areas are using these new frequencies, but FS does not support the new spacing. The three digits in the true frequency for the old spacing are always abbreviated to two digits for FS as it's radios only accommodate such. So .x25 becomes .x2 and .x75 becomes .x7. Both RC's files and those generated by MakeRunways are in plain text (actually comma-separated-variable (CSV) format, so displayable in tabular form by Excel), so you can always check them yourself and edit where you wish. Regards Pete

The option is "Make NAV freq increment = 50 kHz", and it is in the miscellaneous tab of FSUIPC3. It is only applicable to FS9 and before, as the default behaviour in FSX and ESP has the radio increments set correctly in any case. In fact it might have been so in FS9 too (I don't recall) -- it was introduced for FS2002 originally. Before that it wasn't possible. Regards Pete

If you just want it logged then quite a short Lua plug-in will suffice. here: function logvs(off, val) if val ~= 0 then -- if on ground flag just set, get VS, convert it and log it vs = ipc.readSD(0x030C) vs = vs * 60 * 3.28084 / 256 ipc.log("Vertical speed at touchdown = " .. vs) end end -- set to call above routine whenever "on ground" flag changes event.offset(0x0366, "UW", "logvs") I've not had a chance to test this -- ask me later if it doesn't work. Just save it as "ipcReady.lua" to your FS Modules folder. and run FS. (Your FSUIPC must be registered). The log entries will go to the FSUIPC log file. If you want them separate, check the Lua logging option in the FSUIPC Logging tab. The file will then be "ipcReady.log". Regards Pete

Autosave is merely calling the same Flight saving routine in FS that you can manually by using ; or the Flight Save menu. That is because in complex add-ons the add-on code is simulating some of the subsystems, not FS, so FS does not know about it. Most decently programmed addons like those from PMDG trap the FS save action and save their own files at the same time. Where these are known to AutoSave (and some are -- see its documentation), AutoSave will handle the cycling of N past copies as it does for the FLT and WX files. Of course re-loading the flights is then more complex. As well as reloading the FS flight you may have to go to the add-ons menu to reload its settings too, though I think this too could be automated to some extent. One way is for the add-on to supply a utility menu to load its flights including its own data. I think some may do that. Yes, the programmers of the aircraft concerned can do that. Choose those add-ons whose makers take care of such details. Regards Pete

Does FSUIPC have anything whatsoever ot do with your use of GoFlight hardware or the Ariane aircraft? If it isn't used it won't have anything to do with it. Also, it has no idea of any differences in cockpit modes, they are completely irrelevant to it. Maybe you programmed something for 2D mode which doesn't work with the 3D gauges because they are different code in the aircraft? Are you using FSUIPC for anything? Did you lose you settings by dleeting or not reinstalling the FSUIPC4.INI file? Unless you quote actual version numbers -- your "old" one and the "latest" one -- I couldn't even guess as to what might have changed. Saying "latest" unfortunately does not help. Folks have said that and been found to have been using a pretty old one. They meant "the latest we've seen" not "the latest there is" (currently 4.628 at time of writing). All of my products have version numbers and they aren't too hard to find. Regards Pete

Oh, right. I've got no idea what a broadcast address is. I assume it acts a bit like a mask, working with the subnet mask to select the destinations? Regards Pete

Oh. How strange. I've never seen anything other than 255.,255.255.0 or some similar arrangement of 255's. A mask of, for example, 192 would match 0, 64, 128 and 192. A mask of 168 would match 0, 8, 32, 40, 128, 136, 160 and 168. Why choose such an odd mask? I can understand the 15 and 255 parts. Regards Pete

Yes please. Could you post it in a message about it in the "Download links" sub-forum, please, with a sutiable subject title. Thanks & Regards, Pete

There's no simple way like switching on a log in FSUIPC. Those logging options aren't utility things like that, but aids to debugging problems with applications, and assistance for those developing applications. There are hundreds of variables available through the application interface to FS which FSUIPC provides, and there's no way FSUIPC, as the interface, will provide individual user needs for logging any specific one in a friendly form. You can certainly ask FSUIPC to monitor specific offset values (up to four at a time), and those can go to the log, but the "vertical speed at touchdown" offset is a variable which is the same as the vertical speed whilst you are in the air, and which merely freezes when you are on the ground. So if you monitored that you'd get thousands of lines logged and a huge file until you landed, when you could look it up. Additionally it is in units of 256ths of a metre per second, not the normal feet per minute you'd be wanting, so you'd need to convert it. There are two answers. You can either write a small Lua plug-in to do the job. It would only be a few lines of code. One of the examples provided in the FSUIPC install is a program which records many flight variables to a CSV (comma separated variable) file. You could strip that do to its basics and add the test for "on ground". so you only make entries then. The other answer is to use an existing application, such as FS FlightKeeper (there are probably others) which makes records like that. Regards Pete

It's so quick it doesn't arrive! ;-) Yes. But FS wouldn't re-assign automatically unless you unplugged the device and reconnected it, so it looked like a new connection. Or possibly you have left Windows' USB power management enabled, and the device is being turned off to "save power", only waking up when you move the pedals. Try disabling power management on all USB hubs in the Windows device manager. You need to calibrate is with the minimum setting (brakes off) set with your brakes pressed down a little. You always want a dead zone -- the step-by-step instructions for calibrating in FSUIPC does cover this. You need to follow them and be a little more generous with the movement allowed before braking occurs. Yes. assuming you are pressing evenly with both feet (and that is not necessarily the case -- most folks have one leg/foot stronger than the other), then maybe you've not calibrated them well enough. In any case, all you need to do to compensate for a tendency to veer to one side is press a little lighter that side and heavier the other. Like steering a car, differential toe braking isn't an exact setting of the feet but a process of feedback from what you see and feel. What is there to understand? In the matters you mention it is only calibrating, following the simple numbered steps, to achieve your personal desired operation. Regards Pete

There are two other causes of there appearing to be more than one version installed: 1. A copy of FSUIPC.DLL in the main FS folder as well as in the Modules folder. 2. FS still running in the background, hung, with no window showing. I suspect the latter. FS may have crashed, but it didn't terminate. Press CTRL_ALT_DEL and select the Task manager. Go to the Processes tab and scroll to FS9.EXE. Select it and tell the task manager to delete it. Note for future reference that there is alwayts an earliest version of FSUIPC for which support will be provided. 3.85 is extremely old and has not been supported for a long long time. Nothing earlier than 3.98 is currently supported (and there's a much later version available in the Downloads subforum above). Pete

What messages are you expecting? If ASv6 messages are appearing, FSUIPC is obviously not stopping any of them. I'm pretty sure you can delete your own posted messages, but I'll do it anyway. Regards Pete