Pete Dowson

In Vista, all "Program files" folders are protected against user alteration. Because FS9 is not Vista-aware, and does need to write to its own folders, Vista actually puts its files elsewhere and what you see, in Program Files, are mere aliasses, not the real files, and even if you could alter them it wouldn't affect the originals. There are only two ways around this that I know of -- either reinstall FS9 someplace else (C:\FS9 is nice and short), or start Windows Explorer by right-clicking it and selecting "run as administrator", which should give it enough privileges for you to see the real files and edit them. Quite honestly, you'll experience far fewer problems in the future with assorted add-ons if you reinstall FS9 outside the than accursed area. Pete

Well the error messages provided by the compiler are, as far as I know, the same as the ones put into the FSUIPC log (or the Lua program's own log, if you enable Lua logging in FSUIPC options) when FSUIPC's built-in Lua compiler tries to load the programs, so I don't think you achieve anything extra. Do let me know if I'm wrong though, and perhaps i might have to work out a way of providing dummy libraries. Regards Pete

It isn't detecting any DirectInput joysticks, then, or it cannot find a valid joystick number assignment to go with them. Please try using the attached utilities to see what can be detected. The JoyView one uses the Windows "joy" API (same as FSUIPC4 does for buttons) whilst DIView uses DirectInput (used by FSX for everything, but by FSUIPC4 only for axis assignment).. Does FSX see the axes? If not then it could be that your joystick drivers aren't 64-bit compatible. If FSX has no problems then I can only think that the Registry entries, the ones which relate the DirectInput identity of a joystick to its "joystick ID" number, are corrupted. Why did you re-install FSX by the way? It isn't normally advisable -- seems to create more problems than it solves. Or was this a Windows upgrade? If so, then maybe something went wrong with the joystick installs? BTW I'm away from tomorrow (Wednesday 15th) until Friday 24th, so apologies if I disappear before this is resolved. Regards Pete DIView.zip joyview.zip

I doubt that is is in any way related to the library. Do you have any other working FSUIPC applications? It may be the signature. Since 3.7 or so all my modules have been code-signed, for security against virus and other attacks. Right click on the DLL and look at the signature -- see if it says it is valid or ok. You could also check the FSUIPC.LOG file (in the modules folder) -- that would tell you too. If you check the User Guide it explains this and what to do. Otherwise it may be some registration problem. try removing the FSUIPC.KEY file. if it then works, it's either a bad registration or the system date is incorrect. Regards Pete

It cannot be 541A, which is part of this: 5418 4 MCP/FCU Knobs/Selectors S00-31 (Read/Write) Anyway, it's all really pretty much self evident. All offsets are accessible via the Offset controls in the drop-down assignments. There are Offset Byte, Word and Dword controls -- Byte = length 1 (8 bits), Word = length 2 (16 bits), Dword = length 4 (32 bits). If you are only changing one bit then Byte would be sufficient. The operations you can do are Set (to set a value -- changing the whole n bits), Setbits (to set one or more bits), Clrbits (to clear one or more bits) and Togglebits (to toggle one or more bits). There are also Inc and Dec and cyclic variants but you don't need any of those for sure. These are all listed in the dropdowns with meaningful names. You need the bits values -- bit 0 = value 1, bit 1 = value 2etc (just 2 x 2 x 2, n times). Basic arithmetic. Add them together for multiple bits. This becomes the parameter. Whether you want to set, clear or toggle depends on how the PM action works -- you need to refer to their documentation. Pete

All of the Lua libraries supported in FSUIPC -- both the standard ones and the ones I've added -- are built into FSUIPC and preloaded into your Lua process before it is executed. There's no need to refer to them anywhere else/ Pete

Hmm. I see I have to spell every little thing out for you -- how do you think FSUIPC knows what to do if there's no information there other than your button number? Sorry, I cannot go on with this inane exchange. I respectfully suggest you refer to the documentation supplied for further enlightenment. There are many many text editors available -- whoever said they need to have any relationship to Notepad, which just happens to be the freebie editor supplied with Windows? And most certainly Notepad finds the A,2 in your file when I try it here. You are evidently making a mistake. Anyway, I showed you clearly where the parameters were, and you must have edited them before in any case for them to be there (and for the joysticks to be lettered, not numbered, so I'm not sure why you are regressing so much now. Best call an end to this thread. It's going in silly circles. Pete

Are you by any chance doing this whilst it is still in the ZIP file? Even an ordinary text file has more than "General". All my DLLs and EXEs also have "Version", and all DLLs and EXEs have "Summary". I suspect you aren't looking at the right thing, or right place. No, not normally. Two files with the same name cannot coexist in the same folder, so when you put the new one in it replaces the one that is there -- if it doesn't (because of some protection setting in Vista or Windows 7), then, yes, you would need to delete the old one first as the new one might otherwise be called "FSUIPC - Copy.DLL" or similar. Unfortunately FS doesn't care about the name, it loads any DLL that "fits" from the modules folder -- and sometimes from the main FS folder too, though that may have only been FS2002. Regards Pete

You say "tried", but the logs show "succeeded". There are no errors, nothing showing wrong, excepting a very poor frame rate Unfortunately, for the FSUIPC log, you only had FSX running properly for a minute, which is too short to tell what might be goping on -- and programs like ASV6 are very heavy users in that first period. This might explain this awful FSX frame rate: reflected also in the WideServer and WideClient results: But there are no errors, and nothing wrong with the operations as far as WideFS and FSUIPC are concerned. It simply looks as if you are overloading FSX to an extreme. I suspect the symptoms you are seeing are merely the outward appearance of everything slowing down to a near halt. Try taking stuff off, reducing things in FSX. You said "the only thing I did is installing scenery (cloud 9 Xclass and FEX)". Could one or the other of those be bringing FSX to its knees? Maybe one or the other installed some additional activity, other SimConnect clients or modules, which are soaking up processor power? Regards Pete

No. You'd need to look it up using the Lat/Lon. Regards Pete

By "WideFS" here, I assume you mean a copy of WideClient running on a Networked PC? 3) So through FSUIPC on my FSX computer I disable WideFS which causes FSX to hang... Ouchyou have something really wrong if turning off the Server action hangs FSX! Help please? Thanks in advance I would need to see the FSUIPC, WideServer and WideClient logs. But please note that after tomorrow (Tuesday) I am away for a while -- back on the 25th. Pete

I said to look for "A,0" because originally you said it was button 0 on A. It turns out you wanted A,2. The surrounding letters or numbers were not relevant to such a search -- why would you try to look for "A" on its own? It would be meaningless having a line just with "A" on it, or even "A,0". Obviously the parameter lines themselves have to have other information on them, to tell them what to do!!! The "P" means "Press", the stuff after the "A,2" tells FSUIPC what to do. If you want to understand more, just look in the Advanced Users document which details the format in full. Searching for text in a text file can be done with ANY editor, notepad included. Look in the menus. Have you never used any editor before? I'm sure there's Help there too. Er, sorry. What does that mean? We were talking about editing a file. There's no file editor provided in FS! Pete

FSUIPC doesn't "trap" keys as such, it intercepts the keyboard messages arriving in FS -- the main FS Window, class "FS98MAIN", is where all messages (FS controls, keys, everything) are "intercepted". Unless this gauge of yours is a separate process, not part of the FS process, FSUIPC sees all keypresses sent to it. The job of mapping buttons to keypresses, for instance, requires FSUIPC to re-create the exact same conditions in the FS process as would occur if the real keys were used. This actually results in those mapped keypresses being interceptible by FSUIPC! So the facility you appear to want would change K to CTRL+SHIFT+K which would arrive just like the K did. If the gauge is in-process, in FS, then the only other possibility is that the gauge is not using the Windows message system to intercept the keypresses, but the Windows-wide "hot key" system. If it were using this then it would act on the key combination even if FS were minimised and you were using some other program at the time. Is that so? The problem then is that FSUIPC is not creating keypresses from the keyboard, but only the resulting Windows messages arriving in FS -- so it still wouldn't work. Well, you could do it indirectly -- assigning the keypress to toggle a virtual button (FSUIPC offset 3340), then programming that button to send a KeyPress. It would need to be done by INI file editing because the button won't toggle whilst in the FSUIPC options. Even if you did this, I've a strong feeling that it still wouldn't do what you think it would do, for the reasons stated. You actually want a keyboard emulation for the keypress, which needs low level privileged hooks into Windows (i.e. a windows driver or service). Regards Pete

I'm sorry, but I haven't the faintest idea. It realy isn't something I've done myself, as least not directly. And it will all depend on your I/O board and the drivers that came with it. Most kits for this sort of thing come with instructions: didn't yours? You might find more specific help if you are doing everything yourself, maybe even including making the boards, on one of the cockpit builder's forums. There's one near here, but also try the forums at www.mycockpit.org . Regards Pete

WideServer is built into FSUIPC4 so it has no problems talking to it. If you mean WideServer talking to WideClient, there should be no problems if you either turn off the firewall or let ports 8002 and 9002 through for FSX/WideClient. Pete

There's no direct way to do that. It's really a waste of time simply replacing one windows message with another. you might as well send the one you want in the first place. But that would happen still if one key was mapped to another. It wouldn't help at all. Regards Pete

But that compass reads incorrectly when you are turning, or banking. it is only reliable when flying level. For a correct Magnetic Heading you should take the True heading and adjust it using the Magnetic Variation, exactly as documented. You are not reading it correctly then. As documented, it's a 64-bit (i.e. 8-byte) double floating point value. Are you reading into such a variable? Yes, because it's a magnetic disk floating in oil or alcohol and is influenced by G-forces etc. fly straight and level to get a proper reading, as in reality! No, the Longitude value at 0568 is NOT a FLT64, it is a 64-bit integer (__int64, or a long long, depending on your compiler). FSInterrogate cannot handle 64-bit integers, so it shows you the upper 32 bits, dividied out, and separately the adjustment in the other 32 bits. No. You are simply not reading the documentation properly. There's a lot of difference between 64 bit floating point and 64-bit integers, just as there is between 32- Why on Earth are you using some data files concocted for FSInterrogate as documentation when I spend so many hours making sure that the true documentation for the offsets is complete, accurate and up to date! PLEASE USE THE DOCUMENTATION SUPPLIED! Regards Pete

U is "Up" or release, P is "Press", as documented. You say "nothing with either an A or a 1", so what is this? 23=PA,1,C65567,0 <<<<<<<<<<<<<<<<< A,1 Both A and 2 !!! Why didn't you simply search for A,2 if that's the one you wanted -- I did suggest that, but you ignored my suggestion? There are TWO entries for Pressing A,2, both of which you seem to not be able to see for some reason? This is presumably the one you wanted to change? It looks like you have the button set to press "Z" twice, for some reason? 62=PA,2,K90,8 98=PA,2,K90,8 Please do try looking a little more carefully next time. It would save us both a lot of time! Regards Pete

Hmm. I'm using two overclocked BFG 9800 GTX+ cards in separate PCs, both running Vista 64 and Windows 7 Ultimate 64 (dual booting), and have no problems since version 181.xx of the nVidia drivers. But versions between 179.xx and 180.xx most certainly had frequent problems with black screens -- only ever in full screen mode though. I found the frame rate was just as good in maximised windowed mode, and the graphics sharper-looking, in any case, so I tend to prefer that mode. But certainly full screen mode has been okay with the latest version 181.xx (.22 I think? Not sure at present). Regards Pete

Sounds like the Elite stack, possibly made by PFC (?), but using Elite protocol -- which is proprietary to the Elite simulator. FSUIPC? What on do you mean by that? FSUIPC3 works with all versions of FS from FS98 onwards. Only FSUIPC4 is new, for FSX. It has nothing to do with hardware -- it is NOT a hardware driver! You are getting a bit mixed up, perhaps? None of my software will be useful with the Elite simulator. I do FS drivers for PFC hardware, but FSUIPC is not a driver at all. You need to look elsewhere -- please do not buy anything of mine thinking it will drive your Elite hardware. You need a driver from Elite. If they do one for FS, they will tell you whether you also need FSUIPC or not. Regards Pete

An INI file, known to Windows as "Configuration settings", is a file with ".INI" as its filetype. If you want to be able to identify files properly you really ought to go into Windows Explorer folder options and de-select the option telling Windows to hide the filetypes from you! This means that at some timer you HAVE edited the INI file and assigned two actions to the same button! Once you start doing this for a button, you always need to do it for the button, because there's no way to edit multiple assignments for one button in the options. (I don't think it is worth making the options over-complicated for the few users needing to do such things). The fact that your joystick is being assigned a letter ("A") is positive proof that you HAVE edited the INI file before! By default all joysticks are known by their Windows ID number (0 - 15). You evidently selected the option at some time to assign letters instead! First find the [buttons] section. The should be line [buttons] or, if you are using Profiles or Aircraft-Specific assignments, one or more [buttons.] sections. In those the number to the left of the = is merely a sequence number. The button A 0 will be seen as "A,0" on the right-hand side. Do a search. There must be a LOG file too -- that can also be opened in notepad, and is known to Windows as a "text file". If you can see the DLL you should also see the KEY, INI and LOG files. All three are always there if you've ever run FSUIPC. Information about the INI file is given, and in great details for Buttons, in the Advanced Users document. Pete

You must be entering something incorrectly. There's no other possibility if that's the response. I've done a search. Both sets of keys, were in this name and address: Bill McCracken wmccracken221622@comcast.net Are you entering these details EXACTLY like this? And the Keys MUST be exact too. It is easy to mix up 0's and O's, 1's and l's, 2's and Z's, 5's and S's, depending on the font you are using. Best always to cut and paste all the details. In the six years I've been using this same Registration system there's been no other reason, ever, for the keys to be rejected outright like this except for the few known banned keys (those published by users and distributed by pirates) -- excepting in the very first release of FSUIPC3 which would not handle accented characters correctly, fixed within a week of release. If you really do believe you are entering all three fields correctly, please ZIP up the FSUIPC4.KEY file along with the Install LOG file (both from the FSX Modules folder) and send to me at petedowson@btconnect.com. I'm away for 8 days from Wednesday. Regards Pete

Looks good! Pete

Well your registration looks okay, so the only thing that could be wrong is the settings in FSUIPC for the throttle assignments or calibrations. Remove your FSUIPC.INI file before loading FS so that it all defaults -- then FSUIPC will not be touching anything at all. The only difference between unregistered and properly registered is the action of the user options. Regards Pete

I didn't say "updated" drivers -- what you want is drivers which work. That isn't always the more recent versions! Regards Pete