Pete Dowson

At present you have to read the byte or word or whatever, then use the Logic library facilities or And, Or, Xor to clear, set or toggle the bit(s), and write the changed value back. So, for example: x = ipc.readUB(0x1234) -- read byte to change x = logic.And(x, 254) -- clear bit 0 (worth 1, 255-1 = 254) ipc.writeUB(0x1234, x) or, the same more efficiently (and safer, avoiding possible other changes to the same offset by others between the read and write): ipc.writeUB(0x1234, logic.And( ipc.readUB(0x1234), 254)) These sorts of operations can become quite frequent, though, and I am considering adding "SetBits", "ClearBits" and "ToggleBits" functions to the ipc library. Maybe soon ... Regards Pete

Re-installing FSX seems to be able to create SimConnect problems 90% of the time. In this case, although it appears as if you've installed FSX SP2 or Acceleration, that version of SimConnect is not correctly installed. The version number returned by FS is 61242, which is the SP1 version, so if I were you I'd try re-installing SP2 or Acceleration, or possibly just running the SP2 "Simconnect.msi" which you will find in the FSX SDK if you have it installed and updated. FSUIPC4 does try desperately to recover by then trying to link to the older versions, but when things are screwed up like this those attempts too always seem to fail with that error "80004005" which is an "access denied" error. I think this is because one part of SimConnect can't talk to the other. You could also try updating to the current interim version of FSUIPC4, 4.651, which you can obtain from the Download Links subforum above. I changed the method of linking to SimConnect to make it a little more resilient, though it still can't cope with a total SimConnect mess. Regards Pete

No, it cannot possibly change by itself. I believe you must not have confirmed the change by pressing OK. If you just ESCape from the dialogues everything reverts to its state as it was before you entered the options. Regards Pete

Yes. You'd need to write a Lua program to read and write the two ports -- FSUIPC will only do this automatically for VRI devices. And the Lua program could filter off the commands you wish to deal with yourself and send the appropriate commands to FSUIPC. If by "like a normal joustick" you mean to send button presses, then you'd need to use the Virtual Button facilities at offset 3340 and following. Regards Pete

That set of FS9 folders will be the REAL ones FS9 is actually running from. When you install into "Program Files", Vista (and win7) protect the real folders for being written to (even by the program itself), and the ones it presents to you are just aliasses. An easier way to see and edit the real folders is to run Explorer "as administrator" (a right-click option), as this gives it Elevated Administrative privileges. This is what I explained in the other thread I referenced for you. The best solution, however, is simply never to install anything in "Program Files" if you can help it! Regards Pete

"Holes" in firewalls can be made for specific ports AND/OR specific programs. WideServer runs inside FS, so the program to be known to the firewall would be different between FS9.EXE and FSX.EXE. Regards Pete

Sounds suspiciously like you've got port 8002 in use by something else, maybe SimConnect? Check the SimConnect.xml file on the FS PC and the SimConnect.cfg on your client. Regards Pete

Since all of Your user settings are stored in the INI file and no where else at all, you couldn't have deleted the file in use. Neither of those are placed by FSUIPC nor will they be read by FSUIPC. Are you running FS with the compatibility mode set to XP, or is it off or set to Vista? If it isn't set to XP mode it is possible that the INI, LOG and KEY files are kept in the Flight Simulator Files folder, in your Documents folder. This is a Vista thing. However, I would have thought you would have found them there using search. So: Alternatively, assuming you let FS install in its default location, in Program Files, then please see the explanation in a thread near here -- one explanation which unfortunately seems to have confused that user completely, as he appears not to be running Explorer "as administrator" in order to see and access the real folders as I suggested. The link is http://forum.simflig...installing-fs9/ Regards Pete

Do you mean FSUIPC3 or FSUIPC4? If you mean FSUIPC3 (for FS9 and before), it's on the Miscellaneous tab, and documented in the user guide. It is mysteriously called "stop cockpit sizing and moving". You wouldn't have found it by searching on "lock" though. It doesn't exist in FSUIPC4 because it didn't work there. Pete

Sorry, what exactly are you right-clicking, and where in what manual are you reading this? I am suggesting that in order to view the REAL folders, not the aliassed ones, you need to run Windows Explorer in elevated administrator mode. There's nothing in any manuals I've had anything to do with which gives instructions for Windows Explorer! I think you are not reading what I am telling you. Please read a little more carefully! You can install FS wherever you like. It's one of the options during installation. It hasn't changed just because you have a new computer. Regards Pete

The FSUIPC programming interface, Which wideFS supports (indeed, that's its prime purpose) provides facilities to request flight loading (or saving). Please see offsets 3F00 and 3F04 in the offsets tables in the FSUIPC SDK. Regards Pete

That is exactly the purpose of the ipc.set and ipc.get functions. Such globals persist for the whole FS session. Regards Pete

Those are FSUIPC.INI, FSUIPC.KEY, FSUIPC.LOG and FSUIPC.1.LOG respectively, as EXplorer would tell you if you changed that stupid option which hides filetypes from you! The FSUIPC.1.LOG file is only produced when you click "New Log" in the Logging tab. The old logs are saved with .n inserted, in order. FSUIPC always makes those files and cannot run without doing so, so they are certainly on your system, and in the right place too. If you are not seeing the same on the Windows 7 PC it is because you are looking at the Aliassed folder, not the real one. Windows 7, like Vista, protects all files in "Program Files" from user change -- this is why most folks are advised to install FS elsewhere, not in the default install location. FS9 is not aware of these things and wants to write to its own folders. Windows 7 recognises this and creates special folders which FS9 can see but you cannot, at least without bering an "elevated administrator". Try running Explorer by right-clicking on the icon or the EXE and selecting "run as administrator". You should be able to see them then. They are there. It is simply the way Windows is protecting its system against you, the "untrustworthy" user. It's a right Royal pain. I always turn all User Account Control (UAC) off and always install FS in its own folders, like C:\FS9 -- or better, on a drive of its own. It performs better that way too. Regards Pete

Yes, as I said, didn't I? Both READY and DELAY. Looking at the code it should work still. What FSUIPC4 version are you using (the number?). Show me the [Programs] section from your INI file please. Pete

It sounds like you are using the separate Thriottles pages to calibrate your throttles and are forgetting to check the "No Reverse Zone" (NRZ) option. The throttles calibration is specifically designed to allow calibration of throttles with both forward and reverse zones on the axis. Please do read the documentation. The section on calibration does point these things out. The fact that you've got the idle point ("centre") about half way along the axis also indicates that you've not really yet bothered to even try calibrating correctly, as that is the default position. It you were calibrating with mostly forward thrust you'd have placed the idle point, via the two centre "Set" values, way back near the idle stop. If you follow the numbered calibration steps in the documentation you'll have better results even without the "NRZ" option. That's why documentation is provided, to help in matters such as these. Regards Pete

What Windows version are you using? If it is Vista and you've not set FS9 to run in "XP compatibility mode", then the FSUIPC data files may be going to your Flight Simulator Files folder in your Documents folder, the same place as FS stores its data such as Plans and Flights. This would affect the FSUIPC LOG, INI and KEY files, which is why I'm a bit confused by your statement "The only files in the modules folder are either DLL, text or key files.". You don't have to do this every time you run FS? If you mean after changing PCs, this will be because Windows registers your devices with different numbers. If you unplugged them and plugged them in differently it would happen again. The best way out of this is to allow FSUIPC to keep track of them by using Letters for the devices, not numbers. Look up the Joy Letter facilities in the User Guide, and apply that. [LATER] It's occurred to me, perhaps rather late, that by "text" files you may actually be referring to the FSUIPC LOG file, which is a text file. By the same token the INI file is either a text or a configuration settings file -- according to Windows default classification. If this is how you are seeing things, by Windows types not by the full filenames, it is because you have Explorer set to hide filetypes from you! Just stop it doing that annoying thing -- it's an option someplace in Folder Options. Regards Pete

FSUIPC only provides default FS controls, plus a few additions of its own. That sounds like something added specifically by Carenado. Does their documentation provide any information about ways of switching it other than the mouse? If it will accept a keypress you can program that in FSUIPC. Otherwise you might need to investigate the use of L:Vars (Local Panel Variables). If you check some of the User Contributions about other aircraft, in the sub-forum of that name, you will see all sorts of suggestions for this. Unfortunately no one has contributed anything for that aircraft yet, though, so you may need to research it yourself. Regards Pete

Sorry, no. It works fine here. simMarket is run by the same folks who provide these Forums. This link should take you direct to their main page: http://secure.simmar...default-en.html If not I can only suggest you either check with your ISP or check your own PC for some sort of virus or trojan infection. Regards Pete

"Unzipped" FSUIPC? You should (must) run the Installer. FSUIPC isn't supplied on its own, except as an interim update. There never is initially -- it generates the default settings. I'm not surprised. I doubt if any of the joystick numbers are the same on a different computer! This is because you are looking at an Aliassed folder, not the real one. You need to run the FSUIPC installer. Install FSUIPC using the supplied installer. You must be using 3.98 or later in any case, or I cannot support you. 3.98 is only supplied in an installer. Please post to the Support Forum next time, not the FAQ subforum, where I found your post. Regards Pete

That's probably because you've got FSUIPC calling FS's window display routine as fast as it possibly can, and that doesn't leave time for anything else. To avoid re-entry to non-re-entrant functions, most of the FS routines used by FSUIPC, and therefore Lua, are called from within the main FS thread -- and if that does nothnig esle, nothing else looks like being done! The same effect would occur with many other Lua facilities which invoke, directly or otherwise, FS functions. Yes, I can understand that. As I said, the timer is a low priority facility. Regards Pete

Interesting, but I think it must be just a coincidence. I wouldn't really expect things to lock up. The timer system operates at a lowish priority. It would only mean that your Lua time function would be re-entered as soon as it exited, within the frame of Lua interpretation, bearing in mind that there's an interpreter-imposed delay (a hand-off to other threads) between each line to ensure full time-slicing cooperation. I would just think that any timer setting of less than about 20 mSecs would actually give an unpredictable rate, but it may well coincide with all the other demands which have a regular rhythm, like the visual frame rate. Sorry, can you clarify that? What blocked who and how? The sleep function actually does call the Windows Sleep API, and "Sleep(0)" merely tells Windows "if anyone else is ready to run, give him this time slice, but if not let me continue". Assuming you mean "event.timer(0,"F-Name",)", then, no, because you've no knowledge of what that achieves. If you really want to re-execute the function immediate, just loop. Having a Timer do it seems superfluous. FSUIPC uses them, but they are not synchronised -- SimConnect interaction is too loose, too asynchronous. FSUIPC's interface with FS9 and before was rather different. Regards Pete

Ah, that makes rather more sense! ;-) No, no! The axis assignment facilities were added MUCH later, mainly to satisfy the demand to be able to assign different devices for different aircraft, or multiple devices for dual controls etc. After I'd added the facilities I realised there was scope there for adding extra "axes" not supported by FS in themselves, like the reversers. But they are an extra and separate option. Well, quoting it out of context like that is bound to be ambiguous and confusing. But you need to read things in the ontext in which they occur. The paragraph it is part of actually says: which (I though obviously?) simply tells you that if you don't set or select an axis here, in one of the joystick pages, then FSUIPC does nothing to it. It is simply telling you that you have to SET it to CALIBRATE it. See the "SET" button? I really cannot see how you can relate any of this to ASSIGNING an axis, which is a completely separate subject and a completely separate chapter, and actually uses completely different words -- not "setting" but "assigning". Assigning is a very specific action and has a specific meaning. But "set" or "setting" is a rather general English word which can be applied to something as simple as pressing a button, as here, one labelled, oddly "Set". Regards Pete

All updates are free, and in fact you are encouraged to keep up to date as old versions cannot be supported. The latest full edition, 4.60a, is available in the usual places -- mainly the www.schiratti/dowson page maintained by Enrico Schiratti. That will be replaced by 4.70 within the next few weeks. That place is documented in the User Guide, and pointed to by the SimMarket purchase site. You can always check versions and see if there are later ones by visiting the Download Links subforum, here. At present there is a new Installation package there for version 4.638, and an updated module (only), 4.651, which adds a lot more, as listed there in "Updated Modules". Regards Pete

Just delete it! Please refer to the section entitled "Deinstalling" in the user guide where it tells you this! However, if what you really mean is that you want to restore it to defaults, to delete all your settings, that's not the same thing. In fact deleting the program and putting it back again would accomplish nothing. To delete your settings simply delete the FSUIPC4.INI file, which is the configuration settings file which contains ALL of your assignments and options choices. Delete it from the FSX Modules folder before running FS and all FSUIPC's actions will revert to default -- i.e. no actions at all. Please always also make sure you are using a current supported version. 4.60 is the earliest for FSX, soon to be replaced by 4.70. Regards Pete

Sorry, I didn't write FsXpand, and I cannot therefore re-program it to stop it stealing the focus. I suggest you write to the author. That's what the READY option does, as you've seen. What good would that do is FSXpand still steals the Focus? Hide works fine, but only if the first top window produced by the program is the one which is going to be used, because all it can do is send a Windows message to tell it to minimise as soon as it detects it's top-level Window. Programs which have a splash screen or intro screen which then disappears in favour of the main screen are just not amenable. Black screens when changing FSX screen modes are quite a common problem which are only usually resolved with video driver changes or settings. Try the FSX Forum here on in AVSIM. Have you asked the FsXpand folks? It shouldn't be hard for them to provide a non-intrusive or even auto-minimising mode? It surely cannot be an uncommon need? I went bald long ago. :-( There is an unpublished DELAY facility in the [Programs] options. I implemented it thinking it might solve something like your Focus problems, but it didn't, so I was going to remove it -- but didn't. It operates like this: Add a parameter "Delay=n" to the [Programs] section, where n is the number of seconds. Then for any Run or RunIf parameter with a READY setting which you want delyed n secs after "ready" add the extra keyword "DELAY" (with a comma seaprator as usual. I can't promise it still works, but let me know if it helps. As I said, I can't really see how it can. You might want to make sure you are using the latest version (4.651 from the Download Links subforum) as I'm not sure when it wnt in. Regards Pete