It seems fixed in the new SP1c. I was also annoyed by the slowly-changing value, but now, the value is incremented by 10ft steps when you keep turning the mousewheel, as for the altimeter setting.

Don't believe anything was changed with this in SP1c. I will ask for SP2.Here's one idea though - I have a Logitech G500 mouse and the wheel on it has a "free scroll" mode with low friction. You can basically roll it, take your finger off it and it has momentum and keeps rolling. I use it all the time to quickly roll sim knobs up or down.

Don't believe anything was changed with this in SP1c. I will ask for SP2. Here's one idea though - I have a Logitech G500 mouse and the wheel on it has a "free scroll" mode with low friction. You can basically roll it, take your finger off it and it has momentum and keeps rolling. I use it all the time to quickly roll sim knobs up or down.

Indeed this mouse feature you are talking about is very very useful, and a little picture for you guys. By the way, it may be an expensive product but really worth it. Never had the trouble you guys talk about since release date. And the button Ryan talks about is on top (on mine)

Don't believe anything was changed with this in SP1c. I will ask for SP2.

Oh? Maybe I wanted it so much that I dreamed of it... ;-)Thanks,Thomas

Hi,I'm not sure what's going on there. The Ctrl+End combination was only an example. Perhaps this command is already used by another add-on on your PC, in which case you should use a different one.You need to assign ALL THREE flags used in the Lua script to hitherto unused key commands or to buttons (as long as FSUIPC recognises them). Key commands or buttons assigned to toggle the flags 1 and 2 will result in the minimums value decreasing or increasing. By default, the FSUIPC user offset 66C0 equals 0, meaning that the minimums value increases or decreases by 1 ft via the Lua script. If you change this offset to 1 with the key command or button that toggles the flag 0 (Ctrl+End in my example), minimums value increases or decreases by 10 ft - IF you change it with the Lua function executed by toggling flag 1 or flag 2 (i.e. not with the mouse). Toggle the offset 66C0 again, it will go back to 0 and increase or decrease will once again be by 1 ft, etc etc.The above has no effect on what the mouse does. There should be no click sound that I am aware of - you should not need to use the mouse, that's the whole point of it !I understand now from Thomas L. that mouse acceleration has been introduced with SP1C. That may address the issue for you. But if you still want to pursue the above, can you describe EXACTLY what you have done ?

Hi Emile!I think I start to get it now. So, I don´t need the mouse but 3 keys right? Maybe that's the problem because I just did 1. I assigned the ctrl+end (and is not used by any other stuff) to the LuaToggleMinimums with condition 0. I just don't know what to do about de 1 and 2 that you said. Also the flags I didn't get it.Maybe if you help me setting the other 2 keys it can work.Many thanks.

Hi Emile!I think I start to get it now. So, I don´t need the mouse but 3 keys right? Maybe that's the problem because I just did 1. I assigned the ctrl+end (and is not used by any other stuff) to the LuaToggleMinimums with condition 0. I just don't know what to do about de 1 and 2 that you said. Also the flags I didn't get it.Maybe if you help me setting the other 2 keys it can work.Many thanks.

Correct, you need three different key commands that are not used by any other add-on or by FSX itself. No, you don't need the mouse for this. The mouse will continue to do exactly as the PMDG programmers set it to do.Don't worry about "flags" if the term is unfamiliar to you. Think of a train approaching a switch : the position of the switch determines which track the train will continue on. That's what flags are commonly used for in software : their value ("position") determines which part of the code gets executed next if there's more than one option.You have already assigned one key command Cltr+End to flag 0 (your "switch"). Now you need to do exactly the same procedure (see the picture of the FSUIPC dialog box as an example) twice more :The second key command you decided upon, must be "confirmed" with the value 1 in the parameter box as shown.The third key command you decided upon, must be "confirmed" with the value 2 in the parameter box as shown.Now when you press your second key command it should decrease the minimums value. You can select whether it decreases by 1 or 10 ft using your first key command (Ctrl+End).When you press your third key command it should increase the minimums value. You can select whether it increases by 1 or 10 ft using your first key command (Ctrl+End).And don't forget that firstly the file Minimums.txt must be saved in your FSX Modules folder as Minimums.lua.I really can't explain it any clearer than this. Good luck & let me know how you got on.

Indeed this mouse feature you are talking about is very very useful, and a little picture for you guys. By the way, it may be an expensive product but really worth it. Never had the trouble you guys talk about since release date. And the button Ryan talks about is on top (on mine)

I have that. It's the best mouse I've ever used. It also works on transparent glass.

ipc.control(69987, 8192) -- decreases minimums by 1 ft

Great instructions, Emile.Just wondering if you could kindly explain the relevance of the values of the two parameters, 69987 and 8192 passed into ipc.cotrol() ?Many thanksGary

Great instructions, Emile.Just wondering if you could kindly explain the relevance of the values of the two parameters, 69987 and 8192 passed into ipc.cotrol() ?Many thanksGary

Hi Gary,Thanks, and sorry for the belated reply - I've been away all week for work.Please note that I'm no more than an interested amateur. What follows below, is my understanding which may be only partially correct and would probably not be the way in which a programmer would explain things.The ipc.control function "writes" a "control" to FSX (a bit like sending FSX a command). When and how that control is written to FSX ("issuing the command"), is determined by the user, in this case through a Lua script that can be assigned to buttons or to key commands. FSX contains a whole host of default controls, which are listed in Peter Dowson's PDF document "List of FSX controls" and can be assigned directly to buttons or to key commands with FSUIPC or LINDA. Many of those (though not all of them, I think) can also be assigned via FSX's own Controls menu.Add-ons such as the PMDG NGX implement additional controls to manipulate aircraft features that are not available in default FSX. The ones I've used in my simple Lua script, are non-default controls so you won't find them in Peter's list. Perhaps there will be a list of them in the SDK documentation.The first parameter (69987) is the control that tells FSX to make a change to the Minimums value on the PFD. The second parameter (8192 or 16384) specifies whether this minimums value change is to be an decrease or an increase. I have no idea why PMDG chose the number 69987 for the control. Nor do I know why the parameters to indicate a request to decrease or increase the minimums value are 8192 and 16384 (although as it happens, these values are equal to 2¹³ and 2¹⁴ respectively so there's probably a programming-technical reason).Hope this helps.

Don't believe anything was changed with this in SP1c. I will ask for SP2.

Please do, Ryan. This topic is brought up here at least once every 1-2 weeks. It seems that some people have a way around it, and some people don't. I think some sort rotary acceleration would be great, or maybe even a key command to increase the altitude in 1000 ft increments. Also, I think it would be a good idea to be able to have the CAs and F/Os minimums synced, just like the altimeter function that is already there.