Pete Dowson

I'm glad you sorted it out, but by "full version number" I mean something like 4.xxx. FSUIPC4 is the generic name for the FSX version which has been available for over four years now (since FSX first Beta). Regards Pete

You don't buy a specific version, only FSUIPC3 or FSUIPC4. What is the full version number? Either your copy of FSUIPC is well out of date, preceding the implementation of the EFIS module, or you haven't got the GoFlight software installed correctly. FSUIPC needs GFDev.DLL to be installed in the GFConfig folder (or, for FSX only, it can go into the FSX Modules folder). Please check the user guide. >> The FS Control tickbox is unavailable << What do you mean by "unavailable"? Is the keypress tick box also "unavailable"? Is there a joystick and button number showing top centre? If not you can't do anything. You cannot assign until a button or switch is recognised. Please see the user documentation. And please always state actual version numbers. Regards Pete

Which simulator simulates that? Pete

I did explain. did you not see? ("after pasting, select the data and click the "<>" button above the message entry area"). Can't you see that button? In the line showing B I U S etc (for Bold, Italic, Underline, Strikethrough). The <> button is one from the end. Pete

You just need to take the actual parameter lines, make sure their numbering doesn't clash with any you have already, and paste them into the [buttons.xxxxx] section applicable to whatever Profile you wish to use them in. Or if you want them applicable to all, paste them into your [buttons] section If that's not the same joystick number used in the stuff you want to include you'll need to edit those too. Regards Pete

On my system with two screens I'm using a GTX 280 with even older drivers I think -- 190.56. I'll try again when I get time, or I might update my drivers. It's my development and testing PC. My real flying PC only drives a projector and a 10 foot wide screen. ;-). That uses a GTX 480 and very very recent drivers. Regards Pete

So far i can't make it do that. I suspect it may be to do with video drivers, maybe the video cards themselves. What drivers and card(s) are you using? Note that a lot of the messages I've read in assorted forums also seem to suggest that using 2nd screens in full screen mode doesn't work with FSX -- though it did, and quite well, with FS9. I suspect you've just hit on some combination which does work. Regards Pete

Hmmm ... that means it is not only bypassing the usual WM_COMMAND route via the FS98MAIN window, but also the SimConnect control monitoring facility. I think you've uncovered another bag of worms inside FSX. I'm really very unlikely to be able to resolve that, not unless I can repro it here which so far I cannot. Same here except only two screens and no TH2G. There's something about TH2G that is changing things there, then. I do have a TH2G on an XP machine, but a full screen FSX on that occupies all screens -- I don't understand how you have a screen free if it is all one continuous desktop. The full screen FS should occupy all of them, surely? That's what it means to be "full screen". Regards Pete

So it is a DLL.XML problem. You posted that before. Two copies don't help more than one! ;-) Your DLL.XML is in error somewhere, but as I said before: I'm afraid I can't tell from the posted copy whether it is okay or not. This new forum software seems to remove all of the control lines. Could you try putting files into "code" brackets? (after pasting, select the data and click the "<>" button above the message entry area). Pete

No. If it occurred on all of the menu tabs I would have said the only possible cause would be some keypress being sent to the Windows dialogue routines. FSUIPC itself doesn't control which tabbed section is showing -- that's all part of the Windows software presenting the dialogue. However, you'd think the same would apply in any of the tabs. The only keypresses I've found which change tabbed sections are the "Left" and "Right" cursor keys, but they only do so when the tab title is shown selected (i.e. with the rectangle around the name). If you can try enabling FSUIPC's keypress logging and see if you are receiving spurious keypresses all the time. Regards Pete

Saitek use their own driver and own system, and they use FSUIPC without permission and without license, so I will not support them. You need to refer to their support. Sorry. If they ever resolve this violation (and I've been trying for many months) I shall look at such problems more sympathetically. They are the only hardware company to ever refuse to correctly license their use of FSUIPC. Regards Pete

Hmm. I cannot explain that. FSUIPC subclasses the "FS98MAIN" window -- the windows message processing WndProc in FS -- and traps WM_KEYDOWN and WM_KEYUP messages to determine if they are user assigned. The log should show those. If not then they are being taken out by something else subclassing ahead (i.e. subclass added after) FSUIPC's. But to do that you'd think that whatever it is had a use for those keypresses, so it would still make no sense if they did nothing. I can only think that there must be some sort of focus change and an alternative WndProc activated to handle the messages. I find that difficult to believe, as it would be so weird. The FS98MAIN WndProc is the control centre for everything in FS. All parts of FS send controls (as WM_COMMAND messages) through that routine -- that's how FSUIPC monitors Events too. (Does the FSUIPC event logging show the control sent by 'z'?) How? Where does it get them from? Is it only the GPS? What about other child windows (undocked FS windows)? They are all treated in the same way as far as I know. No one has reported this problem before in the four years of FSX. In fact as far as I know most folks can't get undocked windows on a separate screen in FS full screen mode. I have two different multi-screen installations and I certainly cannot do it -- as soon as I switch to full screen mode any undocked windows disappear -- screens unused by FS go blank. Regards Pete

Edit the FSUIPC INI file which you will find in the FS Modules folder. Delete the sections which have the aircraft name appended within the [ ] parentheses. Regards Pete

In that case, so must FSUIPC -- unless the specific keypresses you are using have been intercepted by some other add-on. You can enable button and keypress logging in FSUIPC's options to see what is going on. Custom controls? What are they? Perhaps you could be more specific. Regards Pete

Neither ASE nor Squawkbox4 use either FSUIPC or WideFS. You have to install SimConnect on the client PC and configure SimConnect on bother Server and client. I cannot really undertake to support SimConnect and those programs as well as my own -- you should find their instructions perfectly clear. If not please do try their support forums. Note that a separately installable client version of SimConnect is only supplied with FSX Deluxe. Regards Pete

Why? There's no need to delete anything. Pete

Yes. Offsets 66C0 - 66FF are reserved for general user needs. They are listed as such in the tables. Regards Pete

Sounds like FS then no longer has the focus. FS won't see any keypresses either -- if FS sees them, so does FSUIPC, as that's how it gets them, through FS. For normal keypresses to reach a Windows program it must have the keyboard focus. Aha! Certainly nothing outside the "full screen" owned by FS is going to provide keyboard focus for FS. It might be using raw keyboard mode or Windows hotkeys. Neither of those methods needs the focus. Regards Pete

It sounds like the Maddog installer program destroyed your correctly working copy of the DLL.XML file and merely put itself there. There are still a few poorly written installers like that. No, just re-run the FSUIPC installer. It will correct the DLL.XML file for you. Then please report this bad behaviour to the Maddog support people. Regards Pete

There are a lot of working examples in the "plugins" Zip installed in the FSUIPC Socuments folder (inside your FS modules folder), and there are more in the User Contributions subforum here. You want a little Lua which waits (via an 2event" call) for an offset to change, then executes a function to determine what to do. you could, in that, write a 0 or 1 to a user offset and program your LED to operate from that. A recent example of using the offset event was part of a reply here in thread Please have a look at these things and by all means come back if you need further help. Regards Pete

Okay. And does that interface program allow you to make programming conditions to determine when to light and LED or extinguish it? Where are you actually wanting to program these things? Er, by "programmed" do you really mean "assigned"? If not what programming are you doing, and where? In a Lua plug-in? But "for FSUIPC" in what way? Sorry, I still don't seem to get the picture. If this "InterfaceIT" program can deal with the conditions you are talking about, then what is the problem? If it cannot, how were you proposing to do sophisticated conditional programming? If you could tell me what you've done, how you are currently "programming" these offsets you are talking about, maybe I can advise further. If you want to set bits on a user-assigned offset based on events in other offsets, and you cannot do this in "InterfaceIT", then perhaps you are thinking of a Lua plug-in, using the Event library? (event.offset to take action when an offset changes)? Regards Pete

All FSUIPC can do for keypresses is trap them when they arrive in the main FS Windows message processing routine. It sounds like the GPS is capturing them first. However, it should certainly pass on any it doesn't use. Alternatively maybe the GPS is acting like a separate process and uses its own Windows processing when it has the focus. This is likely for GPS's and FMC's where they need to capture all of the alphanumeric keys for waypoint and airport identity entry. I don't see any reason why it is dependent on where you put things on multiple screens, however. Regards Pete

Those two must be the only ones listed in your Scenery.CFG file then. Neither FS nor MakeRunways looks at folders which are not listed in the CFG file. Both will be ignoring all other subfolders. If MakeRunways doesn't list any details for that BGL then it isn't an Airport Facilities data BGL. You can't go just by the name. It cannot skip over any folders which are listed VALIDLY in the SCENERY.CFG file. The folders will be listed, with their layer number, in the Scenery.txt file to prove it. Just check. If you really cannot figure it out, ZIP up these files: Scenery.cfg Runways.txt ... plus the BGLs you think are AFD's being ignored. and send them to me at petedowson@btconnect.com, and I'll look at it for you. But first, please do make sure you've tried the very latest version of MakeRunways (4.43 is available in the Downloads sub-forum). Regards Pete

You must be using FSX or ESP as those offsets were not available in earlier versions. Sorry, what is "InterfaceIT"? How are you programming things? Help in writing a program, or what? You'll need to be a little more specific in explaining what you are doing, I'm afraid. The programming logic seems easy enough -- you've explained it in words so it only needs converting to code. So I assume your real question is something still unsaid? Regards Pete

If the folder is included in the Scenery.CFG file then all of its BGL's will be searched for AFD contents. They certainly are here. There's no distinction made for any specifically named folders. MakeRunways simply uses the folder names provided by the Scenery.CFG file, it has no favourites or selectivity. It cannot distinguish them. To see exactly what the program is doing, check the Runways.txt file. Regards Pete