John Dowson

Great! No more information needed, thanks. I will release this version later today. Cheers, John

Hi Ray, Hmm..I'm really not sure if this would be useful these days, or if this is easily possible (or why it was removed) but I can look into it. There are so many other specific (freeware and non-intrusive) tools for memory monitoring these days that would do a better job - why not just use one of those? I can add it to my list to look into, but it will be a while before I can get around to this. John

Looks interesting...thanks! John

@Adri1 Could you try the attached version please, v7.3.1a: FSUIPC7.exe John

Actually, with offset conditions, you could make your key presses conditional on the state of the bits in a button flag offset. You would need to determine what offset/bit held the state for the button and use that. Logging the offsets (in hex) would help.

You want to check the status of a button flag when you press a key. As you can't do this, you can use an offset instead. So you would set an offset when the button is pressed, cleat it when released, and on the key assignment you can then check if that offset is set or not, and have your assignments accordingly. Not sure why you can't get a lua script running... No problem. Should have figured out what you were trying to do wasn't possible much earlier... John

Actually no, sorry - no compound conditions on key presses - the documentation says that offset conditions apply, not compound conditions. But why don't you assign and use an offset (or two) to determine what your key presses send? Otherwise then it looks like you will have to use lua.

The same as for buttons. As the documentation for the format of key conditions (at least in FSUIPC4 and later): John

Yes, you can do it that way. But 1070 is just an additional control that sends key presses, such as via offset 0x3110, for use by external programs, for example. You can apply conditionally formatted commands to key presses. As well as setting/clearing/checking the virtual (button) flags. So what is the problem?

Needed to send a key press on a button press - is useful to assign buttons to the default keys assigned in the FS. You cannot activate a button press from a key. You can change a button flag on a key press, using controls 1003, 1004 and 1005. But why do you need to do this? If you want to trigger a button action on a key press, just assign that key press to the button action (rather than triggering the button). If you also want to toggle a button flag on that key press, overload your assignments and also assign to change the button flag. I am sure you don't need to use lua for this... John

No -JsBk is jut an alternative way to define the key - J<shift code>B<keycode>. That’s what the ‘s’ and ‘k’ represent. It is not JjBb! The J and B construction was a form already interpreted for controls 1003, 1004, 1005. Sorry if that is confusing. It is controls 1003, 1004 and 1005 you need to use to set/clear/toggle button flags from keys, not 1070 which is for sending key presses only. Thats why you are seeing all of those key presses in the logs - the assignments to those keys are triggering further key presses... John

Are you installing on a client PC? If so, why are you confused? Did you follow the instructions? I cannot help if you do not tell me what the problem is. If you are installing on the same machine aa MSFS, why are you posting in this topic? What is confusing about the installation process? You just run the installer... See the included Installing and Registering FSUIPC7 document. John

Can you attach your ini file again please so that I can understand hoe log extracts? I always need to see the ini that produces a log file. Also strange that there are no button presses registered in these log extracts, or did you omit them? Best to include them... But there is no link between keys and virtual buttons, unless you are using one if the button flag controls (1003, 1004, 1005). The last time I looked at your log, you seemed to be sending further key presses on your key assignments, using control 1070, which seemed strange to me (why send key presses on key presses....!). Anyway, this should be easy to check. But I need to see your ini.

If you mean the transponder state, this is held in offset 0x0B46, where 0 = Off, 1 = Standby, 2 = Test, 3 = On, 4 = Alt, 5 = Ground. So you can assign to write to that offset with one of the Offset Byte controls, depending on what you want to do. Alternatively, try searching the MobiFlight HubHob preset list to see if there is a preset for this for the aircraft you are using and assign to that. John

This topic is nearly 8 years old, and FSUIPC support is not a sales site. Topic closed. John

I didn't expect that to change anything, it just confuses things, as i said (you don't know which section is being used). Do the logging as I suggested. This will tell you what is going on. Joihn

Btw, you also have two [Keys] sections in your FSUIPC7.ini. This will confuse things... Did you create one of these sections manually? You should remove one of those sections - they contain the same assignments except for the Axis Elevator Set assignment to your comma (',') key, which are slightly different (one is sending the control on press and release, the other is ignoring repeats). John

As I said: Also activate logging for buttons & keys. You can then verify if the control is being sent when you push your button, and if any other elevator axis controls are being sent. I really don't want/need to see this log - you should be looking at it to work out what is happening, but you can post/attach it here if you need further help. John

As I have commented, the issue is confirmed - assignments to button numbers 64-95 are not being triggered, both in FSUIPC6 and FSUIPC7. John

I know what an .ODS file is, and use OpenOffice myself. But the file you posted is junk - it contains the following: Of what use is that? And it is NOT a .ods file. It is a .ods# file, and the name starts with '.lock'.... so, as I said, useless.

What do you mean? And what does that mean? Any elevator value coming from the joystick axis will also change the elevator position. if you want to know what is happening, activating logging for axis values, open the logging console and look at the elevator axi controls logged - this should tell you what is happening. John

What lua file? You haven't mentioned lua before, and I have not seen any lua files from you. Can we please stick to one problem at a time. I am not going to look at those, as I have no idea what you are doing with lua... That looks ok (except it should be 'Lua' not 'lua', but that shouldn't matter, but change just in case). I presume you didn't insert the [LuaFiles] entry, and this was created by FSUIPC, no? If so, then I don't know why your lua isn't running - there are no lua scripts being started according to your log. As for your 'keyboard keys' log, what exactly am I looking for? Why have you attached such a large log? Have you looked at this yourself to try and work out what is happening? I am certainly not going to go through a log file containing over 4000 lines with no indication from you what the problem is (i.e. what key press do you think is not performing as expected?) You can see the key presses registered, and the actions taken on that key press. What is incorrect? Why don't you try keeping the log open and see what messages are logged when you press your buttons or keys. This should tell you what is happening, and if it is not as expected, then show me (i.e. a concrete example of an individual key press that is not behaving as you expect).

You can try assigning to the Axis Elevator Set or the Elevator Set control with a parameter of 0 (both of these controls use the range (-16383 - +16383). John

Not sure what that file you attached is - looks to be an editor lock file, completely useless.... What are you assigning to? If it is the inc and dec controls, they do not accept any parameters. First, activate logging for events and axis controls, open the logging console (Log -> Open Console) and see what events are logged when you move the flaps lever in the UI. This should indicate what controls you can use. You can also try assigning to the flaps offset at 0x0BDC. First, monitor this offset (using FSUIPC's offset monitoring facilities) and check the values logged when you move the flaps lever in the UI. If they are changing as expected, you can assign your buttons to the Offset UDword Increment/Decrement controls. Doing this will use the Flaps Set control when you press one of the assignment buttons to inc/dec the value in that control. Alternatively, you can check what lvars are available for the aircraft (Add-ons -> WASM -> List Lvars). Maybe there is an lvar that you can use? If you see one that looks like it might control the flaps, you can try changing its value (using the provided facilities) to see if updating it has any affect. If so, you can add that lvar to and FSUIPC offset and control by assigning your buttons to change the value in that offset. As I don't have this add-on aircraft, I cannot really advise any further. You need to investigate and try the various options. John

Yes to all. You can also add comments to your myevents.txt with the control number to be used for offset 0x3110. Yes, this file will be installed and overwrite the existing file each time you update, which is why its better to use the myevents.txt file. You can also uncheck the option to install that file (in the installer). Yes, you can also do that.