Pete Dowson

If you have FS set to run "as administrator" and then run FSUIPC applications as a normal user or ordinary administrator, Wndows (especially Vista) actually prevents FS and the other program exchanging data. If you run one side "as administator" then you must do the same with the others. These are different levels of privilege -- different access capabilities. There is nothing else I'm aware of which could stop a connection completely. However, if the code signature of the FSUIPC.DLL module is failing to check, it will cause incorrect values to be sent to client programs and they may not like that. Find the FSUIPC.LOG file, in the FS Modules folder, and show it to me. Regards Pete

No idea, sorry. I tried to locate this zone, but failed. Must be quite small. A LAt/Lon might help find it? Regards Pete Regards Pete

Maybe the side-by-side library system will be better behaved in Windows 7? Let's hope so. I'll be installing the 64-bit version of "Windows 7 Ultimate" Beta within the next week or so, to see what benefits it might provide for FSX performance -- I've heard only good things so far! But I don't think I want to try uninstalling FSX/SimConnect just to see if it gives me the same pains! I'll leave that till forced to uninstall the Beta because of expiry. Regards Pete

It sounds like the panel for that add-on aircraft has a bug in its coding, then. Have you checked for an update? Or else I think you should report it to the authors. Regards Pete

Sorry for the delay on this, but I only just received the updates on this from GoFlight. I've added support for the GF-SECM unit to the latest FSUIPC updates (see the Updates announcement above), but I've no way of testing the change here. If you are still interested, please try the update and let me know. Regards Pete

Please download FSUIPC 3.865 which I think now works okay for flap axis calibration on the PMDG aircraft. Regards Pete

Not at present there isn't. I'll take a look. If it is easy enough to do, I'll add it as another [buttons] parameter. Okay, please download the latest FSUIPC update from the Updates announcement above. There's an enhanced ButtonRepeat capability, and the default setting should meet your needs in any case. Regards Pete

Okay, version 4.425 is now available with this fix. Please see the Updates announcement above. Regards Pete

I mean that you should NOT try to find "free" offsets yourself, but either use 66C0-66FF which are specifically allocated for personal use, or apply for specific offsets for a program or product you hope to distribute. There are no "free" ones otherwise -- even if they appear to be "unused" from FSInterrogate, they may simply be in use by a program you haven't got (yet). Regards Pete

You do realise that you appear to be replying to a message from over a month ago, don't you? Is this really the same problem? Have you been away for a month? Nothing of mine has anything to do with sound, so won't affect voices. In the above paragraph you seem to contradict yourself. You say "when I open my Flight Deck Companion (FDC)....I get all the voices fine", then later "I don't get the voices". I don't understand? What is it in FDC which starts and stops these "voices". I'm afraid I don't have the FDC package and know nothing about it, so you do certainly need help from Dave March if you have any problems with it. FSUIPC is not a "publisher". If you told Windows to always trust "Peter L. Dowson" then that name will be in Internet Explorer's "trusted publishers" list, not FSUIPC. By " a few files" you mean only the DLL.XML file? That's all you showed, and that's no help. Why did you think it might be? Where's the FSUIPC4.LOG file? If you suspect an FSUIPC4 problem, that is the file you need to look at. Is there an FSUIPC entry in the FSX Modules folder? You need to check! There should be NO simconnect files anywhere you should be looking at. The only SimConnect files are in the Windows side-by-side library folder and they are binary libraries, not "gibberish". Please try to be more explicit -- name what you are looking at precisely.. No! Most certainly not! Whatever gave you that idea? Why would you expect Microsoft to know anything about third party add-ons like FDC? Regards Pete

FSInterrogate will say whatever the particular FSI data file used with it tells it to say. The data file I supply with FSInterrogate only covers offsets being populated or assigned in FSUIPC itself. The two places you mention are part of a region which is assigned to third-party addons. You should be referring to the FSUIPC offset tables in the SDK in any case, as it contains more information, and in particular shows that those offsets are reserved for applications. Sorry, I don't know what all that means. What's BCD4T? I know BCD, but what does adding 4T to it mean? If you want offsets for private use, use the ones allocated for this -- 66C0 - 66FF, as listed for general use in the FSUIPC offset table. If you need offsets assigning for use in a program which others will also use, you should apply for an allocation. It is important for different programs to use separate offsets so that users and authors don't get some nasty shocks when two conflicting programs are run together. Regards Pete

Really? Are you saying that the radios are actively using the new frequencies, yet the (default?) FS gauges aren't updating to show them? If so that really sounds like a problem in the panel or the FS installation. The radio gauge most certainly gets its values from the same place as the part which detects reception. In older versions of FS, after changing the frequencies, you had to write values to one of the offsets 0388, 0389 or 038A -- but that was to make it re-scan the database to locate the radio transmitters, not to update the gauges. The latter are supposed to get updates automatically, at the frame rate or better. No. How are you actually determining that the new frequencies are actually being used? It sounds to me that you are not actually sending the Swap commands. Can you log the IPC writes to check what you are doing? I've just tried all 4 standby radio offsets here, and swapped them all both individually AND together via 3123. I am using FSInterrogate2, and the default FS9 737, with the radio stack showing. Even writing all 5 offsets together, setting and swapping en bulk works fine. Please also ALWAYS state the version number of FSUIPC when asking questions about it. If you are not using at least 3.85, please update. You may want to also check the version I am using, available in the Updates announcement above. Regards Pete

I'd need to see the logging. Set IPC read and write logging and also Weather logging. Do one test which doesn't work, and show me, or send me (petedowson@btconnect.com) the ZIPPED log. First, with the logging enabled, try reading a specific ICAO of your choice using WeatherSet2. That uses the NWI. (WeatherSet, the original, uses the older AWI). Sorry, before I look at anything at all, please update your FSUIPC to a supported version. 4.40 is the minimum I will deal with -- that's been available since the middle of November 2008. However, just a quickie: your read request for EGLL seems to have been recognised. but fails to get any response from SimConnect: 24315766 Weather Read request (At Station) to area 3: ICAO="EGLL", Req=0 24319453 WX Error: timed out, WX request type 3, ICAO=EGLL Not seen one of those errors for a long time -- FSX Simconnect since SP2/Acceleration has been pretty responsive. Pete

I've been poring through the part of FS which processes the mouse clicking, and I think I've discovered a way which may well solve your problem with mouse macros and the APU switch. I'm working on it now and should have an update for you to try this weekend, probably tomorrow (Sunday). Please look out for it, then try it out. Try programming the APU switch (yet again). I'd like to see the resulting Macro file entries whether it works or not, please. [LATER] Okay, the latest FSUIPC updates, in the Updates Announcement, may enable you to get that APU switch working with mouse macros. Please let me know. Regards Pete

A few months ago? Maybe it was for an older version? You should at least be on version 4.40 (FSX) or 3.85 (FS9). There are later versions above, as I said, with newer facilities which may suit your needs better. Pete

Ah, sorry. I hadn't realised that PMDG had used something different there as well. Ok, good. Another way possible usually with PMDG panels is to program a mouse macro in FSUIPC for that function, and then assign that. This works for virtually all ops on the overhead -- I do know that -- so I assume it should work for other parts of the cockpit. Regards Pete

The answer is in the documentation supplied with FSUIPC. Yes. Please refer to the documentation. In particular check the Appendix to the Advanced User's guide entitled "About the Aircraft specific option ....". You might find it better in the long run to use the new Profile system, developed recently. This enables you to establish a profile of settings, with a name assigned by yourself, and assign aircraft to it as you need. To use this facility, please download the latest update from the "Updates" announcement above and read the short document about it included. Regards Pete

Saying "latest version" isn't helpful I'm afraid. It only means the latest you've seen and I don't know where you looked. Please always state version NUMBERS. They aren't hard to find, after all. My FSMeteo Version 7.0 quit downloading (froze during TAF portion of download) after I installed FSUIPC update ... What is best way to correct this problem Pete? No idea, sorry. There's nothing in any of the facilities FSMeteo uses that have changed in years. If you are using FSMeteo from a WideFS client for the first time, then possibly your Network isn't working as well as you'd hoped? Check the WideServer and WideClient Logs for errors. If you are using FSUIPC4 (for FSX -- you don't even mention what version of FS you are using!) then possibly you have SimConnect problems. Look in the FSUIPC4 log file too. Pete

Missing numbers don't matter much in these files, so you can just omit the line. There is a maximum number (999 I think in Macro files), that's all. The only restrictions on missing numbers so far are in the new [Profile. ...] sections of the INI. This is because all of those are scanned every time a flight or aircraft is loaded so scanning to a maximum number would affect performance more noticeably. The other stuff tends to be loaded either only once, or when requested in the Options, or only singly rather than all at once. Regards Pete

Possibly an easier way would be to take the ZFW (offset 3BFC) from the total weight (offset 1334), then also take off the payload weights (using the count at 13FC and the sequence following). All I know about that is what it says in the documentation -- "units unknown but dividing by 625 seems about right". Pete

Yes, add up the fuel in each tank and use the fuel weight conversion factor in offset 0AF4. There's a count of the tanks for each engine, but I think those are the ones switched through. I think you just add up all the fuel in al the tanks that have any. Regards Pete

Sorry, I don't understand you. Your original message merely indicated that you'd somehow got a copy of FSUIPC and wanted to install it into FSX. I pointed out that you cannot do that yourself, you need to use the Installer. Have you run the installer? If so you will now have a Modules folder in FSX and FSUIPC should be getting loaded when you run FSX. What "key" are you trying to "check" with SimMarket? Do you mean you can happily install FSUIPC4, and it is working okay, and you now want to purchase it? Regards Pete

Okay, I have reproduced this in the current interim update as well. So there is not need for you to send me any logging, after all, at least for this problem. But I believe it is only affecting the calibration screen, not the RAW axis scanning or its operation. So if you do have some other problem, like that elevator centering, you'd need to try using the logging to isolate that. It does sound more likely to be either an odd incorrect value coming from the EPIC, or, more likely perhaps, an alternative elevator assignment interfering with its values. I will work on fixing the way the RAW input are affecting the calibration IN values, though I must admit, as I said earlier, it was never really intended for RAW values to be "calibrated". In fact in may be an oversight arising from that fact.*** I would advise you to try using the normal inputs for analogue values (as opposed to software-generated specific values). *** LATER: For information, I've identified the cause of the wrong calibration "IN" values. It does only apply to the calibration, and to FSUIPC4 only. It is actually a function of FSX. In order to continue scanning FSX-assigned axes whilst in FSX's "dialog mode" (which has to be used for FSUIPC to present its options), FSUIPC has to make a call to FSX to make it happen (after all, for such axes FSUIPC is dependent upon FSX supplying the values, and this doesn't normally happen when it is "stopped", as in dialog mode). The call it does to achieve this is a facility of SimConnect. It seems that, even if no axes (no joysticks in fact) are enabled in FSX itself, this call does a scan of attached joysticks and puts the calibration mode back to normal, thereby disabling "raw" mode. In turn this creates entirely the wrong range of values in FSUIPC4. I've fixed it, ready for the next FSUIPC4 update, by restoring RAW mode on entry to and exit from the options dialogues. However, unless there are really good reasons for staying in "RAW" mode, I repeat my advice, to try always using the normal inputs for analogue values (as opposed to software-generated specific values). I'm sure it would be less problematic. Regards Pete

The latter is better. Both will work provided the numbers don't change before you next load FS. Sorry, I now see it isn't clear in my update notes. I will have to expand upon that when it gets into the documentation. Maybe I'll edit it now. The numerical "assignment" lines are provided to show you the current setup in Windows. That might change if you unplug things and move them around, and they disappear if you load FS with one of the entries unplugged. The letter assignments do not disappear, however, and you would simply get a warning appended at the end of the unplugged line saying there was no joystick. Next time you loaded FS with it plugged in, the numeric line would reappear and the warning cleared. This works even if the number is then different. No, you don't need to do that. It will be done for you automatically using the numeric assigns to translate. That's why you don't realy want to delete them. Regards Pete

It sounds like you are only looking at the drop-down list for "direct to FSUIPC calibration" assignments. "Pan view" is an FS control, and doesn't (can't be) calibrated in any case so it won't appear in that context. Regards Pete