Pete Dowson

Is this your line: ?If so it is wrong. Comments are started by -- not ==. If you only just added the == comment for posting here, then can you explain what goes wrong when you use sleep? That's all wrong. The sound is identified by a reference, the one called 'ref' in the documentation, returned specifically for later references in the query and stop commands. Did you not notice the "ref = ..." parts in the play commands, to give you the reference to use? It does actually say: The "ref" value returned is a number which can be used subsequently in the stop, adjust and query functions. Regards Pete

Oh, in the "simFlight Forums" banner? Phew. Never looked there! That's way outside my little Support Forum. I have no idea what goes in there. I'm talking about here, in this Forum, where my updates have ALWAYS been provided, for years. It's just that the owners have started using different Forum software, since some weeks ago, and what used to be "stickies" and "Announcements" are now in "subforums". But they are easily accessible - at the top of this Forum, and in fact just above this thread when it's the latest to be written in. The idea of the subforums is to provide ongoing useful reference data, downloads, help, as well as news. Different from the support threads themselves which eventually scroll out of sight and get lost among the thousands of others. Pete

Is there a link saying "downloads"? where? I can't see one! The subforums here are at the top of this Forum, before the topics themselves. There are four of them: Announcements FAQ ("Frequently Answered Questions") Download Links User Contributions Between them there's a lot of useful stuff. I really recommend you don't miss them. The reason they are placed at the top is so you CAN'T miss them!!! Pete

Yes. At present 4.43 is only available here in the Download Links sub-forum, with all the other updated programs. Pete

You control the autopilot by assigning a switch or button to the appropriate control. You only need the Lua code to drive the LED indication. The example you are looking to base it on does not control anything in FS, it only operates the LED. It's virtually identical to the example you quoted already. you only have to add identical lines but changing the offset to the autopilot master offset (0x07BC) and some values and names to match. i.e. whereas for the brake you have: function set_brake(offset, value) if value == 32767 then gfd.SetLight(GFRP48, 0, 6) else gfd.ClearLight(GFRP48, 0, 6) end end event.offset(0x0BC8, "SW", "set_brake") Note the bits in RED. Those we shall change in the lines we add . function set_ap(offset, value) if value ~= 0 then gfd.SetLight(GFRP48, 0, 5) else gfd.ClearLight(GFRP48, 0, 5) end end event.offset(0x07BC, "UD", "set_ap") So, the name of the function is changed, because it is a different function. The test (value == 32767) has changed because the A/P is on if the offset is non-zero (~= 0), off otherwise, the offset is 07BC not 0BC8, and the type is "UD" because it's an unsigned Dword (4 bytes) not a Signed Word (2 bytes) -- though really that doesn't matter much because only one byte is ever used. It's just that it is best to stick to the correct type and length because in some cases it certainly would matter. I've changed the LED to number 5, but of course you need to select that yourself. If it's on a second RP48 you'd change the unit number (the 0 before it) too. I assume you've equipped yourself with the offsets list from the FSUIPC SDK, and of course the FSUIPC Lua library reference? You need both. Regards Pete

Seems it must be a version you are using which precedes that addition. If you are using any recent version (4.43 is the latest) then there is no way it cannot produce such a file. It has exactly the same level of importance as all the others. Regards Pete

The user manual is saved by the Installer into a folder called "FSUIPC Documents", inside the FS Modules folder. It contains full descriptions of everything you get access to when you register your copy. Those are the FSUIPC user facilities. Without registration FSUIPC is merely what FS6IPC used to be (it's predecessor program) -- an interface to FS for add-on programs and aircraft. If your copy was installed by some add-on then it may not have the documentation included. In this case you can obtain it from the Download Links subforum, or merely by running the more recent versions of the Installer. Regards Pete

Thanks for confirming this. I don't know what is going on, and I've no idea how to go about finding out, so I'm going to just document it as it is. Maybe I'll find out exactly what is happening one day, but I'll not lose sleep over it! ;-) Regards Pete

Well, the only time it rejects one and makes the error sound is when min <= both centres <= max would not stay true if the number was to be accepted. That's the only test it performs, the only check it makes. What are the numbers showing before you try to 'set' new ones (MIN - CEN + CEN - MAX)? And what is showing in the "IN" when you press which 'SET' button? Sorry, what do you mean by "a second number"? You seem to have covered all 4 possible numbers in your list of what you can set! No. It is a simple arithmetic check it is performing. And it is totally independent of both Windows and FS9. And it has been like this now for 12 years and I've never heard from anyone before that it doesn't work as I describe. Regards Pete

I assume you mean the auto-throttle, used by the autopilot for vertical and speed modes? FS and most add-on autothrottles should already be doing that automatically -- though I think, to be more accurate, they should automatically disable the autothrottle if the thrittles are manually moved very much. FSUIPC does offer the option to disable the throttle connection to FS, though, via offset 310A. There are bits for each throttle separately as well as one for the 'generic' single-throttle-for-all. You'd have to program it appropriately of course. Programs like Project Magenta use this facility. You could actually program it with a few lines in a Lua plug-in too. Regards Pete

If that Saitek software lets unprogrammed switches through as joystick buttons, then of course. But I don't know the software. If FSX can see them as assignable buttons, so can FSUIPC. Pete

Why do you want to read the axis? I'm now confused. If you aren't already reading the axis why should you want to to implement these changes? Pete

That is a video driver bug which prevents the standard Windows dialogue being drawn on top in full screen mode.. Either update your video drivers (the default ones installed by Win7 itself are not very good -- go to www.guru3d.com and get the current ones for your card), or switch FS to Windowed mode to use Windows dialogues. I expect you have Windows Explorer set to hide filetypes from you. They are in your FS Modules folder -- from what you say they must be. Windows probably says they are text files. Nothing to do with FSUIPC needs special administrator rights. Regards Pete

No, it is a fault in the video driver you are using, one that causes it to be unable to display standard Windows dialogues in Full Screen mode. It happens very rarely, but it isn't anything to do with FSUIPC -- the dialogue is made by Windows. If you cannot fix it by updating your video drivers the only work-around known is to switch to FS Windowed mode to access the dialogues. Note that if you just upgraded to Windows 7, it installs its own video drivers to get you started, but they are quite poor compared to the correct latest ones for your specific video card (i.e. from nVidia or ATI/AMD). Pete

Congratulations. What has that got to do with buying a PMDG aircraft? No! Surprise, surprise, if you want to use all the user facilities of FSUIPC you have to actually BUY the key from SimMarket. Please do read the instructions! Pete

That happens (only) when the numbers are not in ascending order, left to right. It sounds like you are trying to set the maximum to a lower number than the minimum, or centre, etc. The order of the two centre values is irrelevant, but both must be between minimum and maximum, and the minimum must be less than the maximum. Note that negative numbers are arithmetically LESS than positive numbers. Maybe you are thinking that the sign doesn't matter? It does. Pete

Hmm. Strange. I'll check it here. It might be another symptom of one of the fixes made since 3.98 -- there was an error in an internal array size which corrupted at least one thing we knew about. Thanks. I'll check it out with the current Interim version (3.989q). [LATER] Okay -- I cannot make it happen in the current interim version, so I'm pretty sure what I surmised above is correct. If you look at the list of changes since 3.98, it was part of the same bug which is listed as 21. An error in the FSUIPC options interface is fixed which would have caused a number of odd problems, including the resetting of the "white messages" option on the Miscellaneous page. so I'll add this problem to that item. It was fixed in version 3.989d, in September. Please visit the Download Links subforum, and update to 3.989q (or whatever interim version you find when you look) and confirm that you agree it is fixed -- then I'll update the wording to include it. Thanks again, Pete

I can only think of two ways to do this: 1. You could, in the Lua plugin, have an ipc.sleep for 100 mSecs, then, before doing the action, check one of the Lua flags for that plugin. If it is set, don't perform the action. In FSUIPC assignments program the exit from the zone to set that flag. or 2.Just as above, but program the exit from the zone to Kill the Lua plug in. The second isn't a "nice" way though, so try the first. Regards Pete

No, you can use it on any computer. It is registered to YOU, not a specific computer. You can use it on several computers at the same time if you like, providing they are all being used by you. Yes. Regards Pete

You do not "purchase" a particular version, and you purchase from simMarket. The Schiratti site is the download site only, and the version which has been there now since early March is 3.98. If you downloaded an old one it was either cached by your ISP (very unlikely) or you downloaded it long ago, not in the last eight months. Please do read the red text on the Schiratti Dowson site just below the entry for 3.98. The only other possibility is that some other add-on you've installed has overwritten the correct version with an old one. There are some bad installers which do not check! In this case simply re-run the current FSUIPC Installer. If you still have such a problem, show me the Install log which you will find in the FS Modules folder. Pete

At what stage do you get this "total black"? Immediately you double click the FS shortcut, or does something happen first? A bit more information might help, please. incidently I moved your post out of the FAQ subforum -- FAQ means "Frequently Asked Questions" and this certainly isn't one! ;-) If you are asking if FSUIPC is compatible with Win7 then, yes, of course it is. I use Win7 on three of my PCs. No problem. It's a very nice operating system -- easily the best yet from MS, and there are many happy users. If there's an FSUIPC.LOG file in the FS Modules folder, show it to me please-- you can past it here. There will also be an Install log. Show me that too. If there is no FSUIPC LOG then FS is crashing before it even loads FSUIPC. Regards Pete

FSUIPC is NOT "going dead". It is just not seeing your devices. That is NOT "dead! I already told you this! And I've just noticed you are using FSUIPC 3.96, which is old and unsupported!! (I think that version had rather stringent timeouts to eliminate badly behaved joysticks (ones with slow responses) and it was discovered late on that Saitek models seem rather slow to respond and easily cause timeouts). Please update to a supported version. Sorry I should have checked this point before answering the first time! I do not and cannot support old versions. The earliest supported version for FS9 is 3.98. Pete

I may have found a work-around. If I do sub-class the Device Window, it doesn't receive any messages when you first switch to full screen mode. but if you then switch back to Windowed mode THEN again to full screen mode, it looks like the interception works! At least that's what it looks like. i need to do a few more tests on that. I've no idea what's going on -- this is just an experimental result. If you think it might be useful to do it this way let me know and I'll build an updated version for you to try. [LATER] I've done some more testing, and at least with Vista on my particular system this action is 100% consistent. So I've released it as FSUIPC 4.641, in the Download Links subforum. Please let me know how you get on. Regards Pete

The buttons only do anything when an axis has been detected and is shown in the joystick/axis ID in the top centre. Theres no function those buttons can do when no axis is being seen. Sorry, I've no idea. It uses standard DirectInput. So something is wrong with the unit or the USB connection to it. Is is "dead". just because buttons are greyed doesn't mean it isn't scanning. The buttons are only active when they have a role to play. Regards Pete

Mostly it's a case of experimentation. some definitely work, like putting an AI aircraft into slew mode and taking it out again (used by several applications). I don't personally know which ones work and which don't. Regards Pete