Pete Dowson

Nico mentioned that: 4 bytes = 4 x 8 = 32 bits = DWORD ("double word"). So you would use the Offset Dword controls when assigning. Unfortunately, with their being no (or few) values in the original FSUIPC offsets with DWORD values needing increment and decrement facilities, there are currently no "Offset Dword Inc" or "Offset Dword dec" controls to assign to. With the IAS you should be okay with Offset uword Increment and decrement, because, assuming it is in units of 1knot, you would never be using the high 16 bits. Same goes for Alt. The heading can be manipulated by Offset word cyclic increment and decrement because it can run simply from 0 to 359 in any direction wrapping round at the limits. Again the top 16 bits won't be used. The awkward one could be the VS, which, although can be fitted in to a word of 16 bits, is signed, and -1 in 16 bits is +65535 in 32. Maybe, with luck, Nico's program would treat a negative in the lower 16 bits as a correct 32 bit negative, and in that case you could still use Offset sword increment and decrement. If not let me know and I'll see if I can add sdword and udword inc and dec controls. Regards Pete

Yes, and meanwhile we've lost the subtitles, which I was using to announce FSUIPC and other updates to avoid breaking folks' links by changing the thread titles instead, as I used to. I'll try setting a descriptive tag and see if that works. [LATER] Done. It's better than nothing, but, as you say, easy to miss. Also, though it says I can have up to 10 tags, and I put 6 against the "Updated modules" thread in order to state the latest version number of each important module, it only displays the first two in the thread list. It would be nice to have a tag or subtitle in the subforums titles too, so I can notify there when updated modules are posted. Thanks Pete

The updated Lua package from download Links contains an example called "TileSix.lua". It is listed as such in the Lua introductory document provided too, in the same package. Pete

I realise that. Trouble is a lot of such add-ons are still packaged with an old version which can cause conflicts. If it does turn out to be that you need to look for an updated version. Wow! This is actually starting to look like a problem with your disk or memory. I did mention this as one of the possibilities earlier (intermittent problems reading the KEY file). Software doesn't keep varying in behaviour on its own. Good luck! Regards Pete

Oh, those things looking a bit like buttons pointing left? They don't exactly explain what the OPs problems are though, do they? ;-) Are those instead of the subtitles we used to have? Perhaps I can use them for noting when I post updates in the Download Links subforum, as now there aren't subtitles it isn't obvious when they change. I don't know how to generate those at present. I'll have to have a look. Regards Pete

What if you keep FSUIPC4 and don't run OpenCloud? I'm not sure what you are proving to yourself. No idea about OpenCloud, sorry, but instead of going backwards to 4.60 from 4.70 why not go forward to the current version, 4.745? Pete

Thanks, but ... not very clear? I don't see them at all? I scroll up and down the three message now in this thread and there's nothing like that showing anywhere! Even if i could see them I'm afraid they don't help much to explain what problems he needs help with. Regards Pete

I think you will need at least to say what the "issues related the the above topics" are, because there aren't any mentioned before this in this thread. Are they anything to do with any of the products covered by this forum at all? Pete

Sorry, i don't have enough information. Which version of FS or CFS? Or is this ESP or Prepar3D? Which version of FSUIPC (the actual number please)? What offset(s) are you talking about, and with which aircraft? If not a default aircraft, try a default first -- add-on aircraft may not be using the FS mechanisms. Regards Pete

Are you still using keystroke assignments? If so, don't. That'll never improve. Are you assigning to both press and release? If not it will be half speed in any case. The button repeat only applies when a button is held down, so it doesn't apply. The PollInterval parameter is an optional one for the [buttons] section. Please look in the Advanced Users guide. Use search on 'PollInterval'. However, don't reduce it too much -- the default of 25 mSecs is 40 times per second which should certainly be sufficient. i think FS's is 6 per second. Pete

Aha! You are using Actigate? Can you try with that temporarily removed from the Modules folder, please? it has been known to totally mess things up on some systems. If that sorts it, please see if you can find an update for it. Regards Pete

The log is fine and shows everything is okay. Where are you seeing that you aren't registered? I did ask you before but you didn't answer. There is absolutely no way FSUIPC changes each time you run FS. The only thing that could stop it reading the KEY file which is there would be a disk fault, and in that case it wouldn't show the details in the Log because it wouldn't be able to get them! Pete

Ah, your registry is wrong then. Here's what the installer said: Looking in registry for FS9.1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 Parameter"EXE Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 Parameter"EXE Path" ... NOT found! ... Looking in registry for FS9 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0 Parameter"EXE Path" ... >>> OK! FOUND FS9! <<< ... Only 9.0 is in the Registry. It isn't that so much as under Win7 all folders in 2Program Files" are protected from being written to by anything other than installers and things with elevated admin rights/ FS9 was written long before this was the case, and so doesn't deal with it very well. Worse, any add-ons which need to write to anything there will not be able to unless they are also "run as admini", so it makes everything a real hassle. The easy way out is to never install FS in Program Files. Regards Pete

For assigning buttons or keys in FSUIPC? Yes, of course. The FSUIPC User Guide has chapters on both. Regards Pete

Strange. You shouldn't really need to run FS9 that way. Perhaps you need to right-click on it, select Properties and "Compatibility". You can set it to run as administrator there, but maybe it will work instead with compatibility mode for XP. SP2. If you ever install it again, best to select a folder outside of "Program Files" to avoid all sorts of possible problems with add-ons. I always use something simple like C:\FS9, C:\FSX etc. And don't forget to install the FS9.1 update. Regards Pete

Sounds like you've never actually run FS before? Best to get used to FS before worrying about adding things like FSUIPC. The menu bar in FS is just like the Menu bar in 99% of all other Windows programs, but, like in other programs, it isn't accessible until the program is running. The screen you are talking about is an initial selection dialogue and cannot have a menu bar. Pete

In that case FSUIPC has never run in that FS installation. It ALWAYS produces a log file -- the first thing it does is create one, long before adding its Modules menu entry. But just to be sure you ARE looking correctly, run Explorer by right-clicking and selecting "run as .. administrator". This gives you elevated privileges. The folders and files are NOT hidden, but Program Files is protected. BTW how are you determining that FSUIPC isn't registering? Where are you looking? Last time someone reported something like this it turned out they had two installations of FS and were installing into one but running the other! Pete

Why use keypress assignments when there are perfectly good FS controls for such standard functions? You only need to assign to keypresses when driving add-ons which don't recognise FS controls! A list of FS controls is installed for you in the FSUIPC documents folder, and you can use FSUIPC's event logging to determine exactly which control corresponds to which function when you use it. Using keypresses is very inefficient, especially with something which is going to be repetively pressed and released like a rotary. The rotary should be sending a different button one way to the other, so you simply need to assign one to the INCRement control and the other to the DECRement control. Note that with most rotary controls you get "button pressed" and "button released" alternately on each click, so if you want the change to happen on each click you need to assign both press and release to the same control. But please do change to using controls, not keypresses -- the latter will simply choke in Windows' message lists and result in delayed actions in the gauges. You get at least 5 times as many messages going through per click using keys than the one needed for a control. Regards Pete

It looks the same because that is NOT the FSUIPC.LOG but the installer log, again. Please run FS, close it down, and show me the FSUIPC.LOG. BTW I see you are running the original FS9, not the 9.1 update. I would strongly advise you to get your FS9 updated with the 9.1 update as there are lots of things fixed, and many parts of FSUIPC do not work correctly with 9.0. Pete

Sounds good. Actually, all my lists state "Reserved", which does actually mean "reserved" not "free to use" :-) ! Almost all of those marked "reserved" are allocated to one application or another, and, yes, 5300 to 53FF is assigned to Mark Hastings. Well, it isn't usual to share offsets, and it could present a problem for folks using Sim-Avionics as well as your interface -- and why shouldn't they? I know there's a professional or cockpit version of the iFly, but if folks have already spent their money on Sim-Avionics then they should be able to use it with iFly too, don't you think, instead of having to purchase the iFly update. If you used separate offsets there'd at least be a chance of mapping one to the other. I suppose if you used exactly the same offsets for the exact same purpose and units, it might work, but that seems unlikely. Yes, of course. Freeware apps have always had free access to FSUIPC. I just like to be informed/asked, as you have kindly done. Could you please send me an email, to petedowson@btconnect.com, stating the name of the program and your name, and exactly how many offsets you need (a multiple of 16). I use this for the offset registration. If you are still convinced you can share with Sim-Avionics, I can do that, but personally I feel you'd be safer either having your own allocation, or at most sharing with a different aircraft -- the PMDG area, or the Level D 767 areas, for example. At least with different aircraft you know for sure that they won't both be useful at the same time. Regards Pete

You'd need to set bet 5 of offset 310A and keep doing that every few seconds whilst the disconnection is needed. You could assign a key or button to Offset Byte Setbits with offset = x310A and parameter = x20 then remember to press it at least once every 5-10 seconds, or you you'd program the same thing in a Lua plug-in which you can invoke from a button or keypress. To undo it use Offset Byte Clearbits with the same offset and parameters. Regards Pete

Well, there is only one way FSUIPC provides to stop the gear operating, and that is via bit 2 in offset 32F8, but if you were inadvertently setting that, it wouldn't reset just by restarting a flight. Similarly If you were somehow assigning the "G" key as an application hot key (via the offsets for this), again restarting a flight without reloading FS altogether would not reset it. Note that the "G" key is merely sending the FS control "GEAR TOGGLE", so have you checked whether that is working? Really there is nothing whatsoever in FSUIPC (and even more certainly nothing different in 4.70) which could do such a thing but have it undone by restarting a flight. The only things which happen on restarting flights are updates of some offsets relfecting flight changes. It wouldn't even re-run any Lua plugins or reload assignments or calibrations unless the aircraft also changed. Anyway, I think you need to do some more analysis about what is going on. Certainly check whether it is really just the keypress or also the control, then find out why. Also do please recheck with a current version -- 4.745 or later. Maybe something you are doing is somehow corrupting something elsewhere in memory, which affects part of the aircraft system set up when a flight is loaded. But surely not just a keypress? Obviously, you need to delve below that keypress surface symptom.. Regards Pete

Check the date on your computer. If it's wrong, set it correctly. If it is set before the date of your purchase of the registration it will fail. Otherwise please run FS, then close it down, and show me the FSUIPC.LOG file from the Modules folder. Regards Pete

Yes. It seems that both the 4.703 and 4.745 installers work fine now. So what did you change after your earlier reported problem? Regards Pete

No point in that, it's not really relevant. It's probably due to recent changes in Windows security. Please try the current Installer version, 3.998g, as found in the Download Links subforum. Pete