Dear PMDG,When flying to some airfields with Baro minimum at around 3000ft or even more, it take ages to setup this value with the actual minimum knob.In the real 737 if you hold the knob it start to increase very fast the value but not in your product.I also use the Baro minimum for takeoff to setup the EO Accel Alt which helps when not permorming an VNAV takeoff, wich means that twice per each flight I'm loosing lots of time setting the minimum.Could you please fix this?Thanks.

It's been annoying at times for me as well. My mouse has a "hyper scroll" wheel, which means I can make it spin freely (no stopping at notches). By setting it like that (a button on the mouse toggles it on and off), I can spin that wheel and the baro changes fairly rapidly. It's a work around that might work for you for now.

Dear PMDG,When flying to some airfields with Baro minimum at around 3000ft or even more, it take ages to setup this value with the actual minimum knob.In the real 737 if you hold the knob it start to increase very fast the value but not in your product.I also use the Baro minimum for takeoff to setup the EO Accel Alt which helps when not permorming an VNAV takeoff, wich means that twice per each flight I'm loosing lots of time setting the minimum.Could you please fix this?Thanks.

FWIW : I've found a way around this problem, using a few features of FSUIPC, that works on my PC :In my very modest "home cockpit" I use a rotary switch to adjust minimums. This rotary also has a central pushbutton. Both the rotary and pushbutton generate key commands through a programmable keyboard encoder. I have written a very simple LUA script which1. Toggles one of FSUIPC's user-assignable offsets between 0 and 1 via the central pushbutton.2. If the offset =0, for each ACW "click" of the rotary, the control to decrease minimums is executed once (decrease 1 ft) and for each CW "click" of the rotary, the control to increase minimums is executed once (increase 1 ft).3. If the offset =1, same as step 2. but each control is executed four times in quick succession via a script loop : on my PC, this has the effect of decreasing or increasing the minimums by 10 ft instead of 1 ft. Makes adjusting minimums go a helluva lot quicker !In practice, I toggle between 1 or 10 ft decrements or increments as required, simply with the rotary central pushbutton. Of course you don't need to use a rotary switch : you can simply use the actual key commands via FSUIPC. If it helps, I'd be happy to post the bit of LUA code here and a brief description of how I use it. I've used the same principle for adjusting MCP parameters such as heading, airspeed and altitude.

My quick fix is to assign key-presses to MIN INC and MIN DEC in the CDU Options Page. That way, even thousands of feet work out to one long keypress, followed by a couple of shorter ones to get exact.Hope it helps............

I guess I'm just lazy in that whenever the DH gets to high for my liking i just which to radio altimeter. :(

I guess I'm just lazy in that whenever the DH gets to high for my liking i just which to radio altimeter. :(

That works, but remember that radio minimum are generally only used for CATII/III approaches. Most landings are BARO minimums.

It's been annoying at times for me as well. My mouse has a "hyper scroll" wheel, which means I can make it spin freely (no stopping at notches). By setting it like that (a button on the mouse toggles it on and off), I can spin that wheel and the baro changes fairly rapidly. It's a work around that might work for you for now.

Logitech Performance MX? That's what I have. Gotta love the ''hyper scroll''!

Logitech Performance MX? That's what I have. Gotta love the ''hyper scroll''!

I have the Logitech MX Anywhere mouse (wireless) that I use with my laptop on the road (no for simming), and the Logitech G500 Gaming mouse (wired) for my simming rig. Both have some great features.

Emile -- Please post your LUA code. That is a good idea.* Orest

Emile -- Please post your LUA code. That is a good idea.* Orest

Hi Orest,OK, here goes :=====================================================================================function DH_toggle() ipc.writeUB("66C0", 1 - ipc.readUB("66C0")) -- toggles FSUIPC user offset 66C0 between 0 and 1endevent.flag(0, "DH_toggle")function Min_Decrease() if ipc.readUB("66C0") == 0 then ipc.control(69987, 8192) -- decreases minimums by 1 ft elseif ipc.readUB("66C0") == 1 then local i for i = 1, 4 do -- decreases minimums by 10 ft ipc.control(69987, 8192) end endendevent.flag(1, "Min_Decrease")function Min_Increase() if ipc.readUB("66C0") == 0 then ipc.control(69987, 16384) -- increases minimums by 1 ft elseif ipc.readUB("66C0") == 1 then local i for i = 1, 4 do -- increases minimums by 10 ft ipc.control(69987, 16384) end endendevent.flag(2, "Min_Increase")=====================================================================================Sorry, I had added paragraph indents for clarity but they don't show up in the above.The above block of text, between the double lines, should be saved as a text file but with the extension ".lua", in the FSX Modules folder. I saved it as "Minimums.lua". For convenience I also attach a text file that contains the above script (the forum wouldn't let me attach a file with a .lua extension). You can just save this file in the FSX Modules folder and change its extension from ".txt" into ".lua".The above Lua script contains three functions :The first one toggles the FSUIPC user offset 66C0 between 0 and 1 (I chose the first available offset but there is a range of them : see the document "FSUIPC for Advanced Users").The second and third functions decrease and increase minimums respectively, by 1 or 10 ft increments as determined by the value of 66C0.These functions are executed whenever an event occcurs, in this script : a change in the status of one of the flags assigned to the Lua plug-in "Minimums.lua". The task of toggling the flags' status is assigned with FSUIPC to key presses or buttons. Here is a screen capture of the FSUIPC Key Presses dialog box :Arrows indicate user selections or entries. The control "LuaToggle Minimums" in the drop-down list is created by FSUIPC for the Lua script "Minimums.lua" and toggles a flag. In the Parameter field, the value representing the specific flag to be toggled by this control (as assigned in the Lua script) is entered :0 for toggling 66C01 for decreasing the minimums value2 for increasing the minimums valueIn this example I assigned the key combination "Ctrl+End" to toggling flag 0 i.e. toggling the value of 66C0 between 0 and 1.Tick the "No Repeats!" box and don't forget to press the "Confirm" button.Note : on my PC, executing the appropriate ipc control four times in quick succession (four iterations of the "do" loop) results in a 10-fold increase or decrease of the minimums value. I do not know if this may be different on other PCs. If so, you may need to establish the correct number of iterations by trial and error.Oh and BTW : I am NOT a Lua expert ! I only learned those bits that I need for my own setup, through reading Peter Dowson's extensive documentation and looking at the many examples of Lua script provided, as well as from the great work of Artem and Günter of LINDA fame. IOW if the above does not work for you, there's a limit to how much help I can give you.

Hi Emil!Thank you for your help.I don't know so much about FSUIPC programming but I tried anyway. I did everything like you said and assigned ctrl+end as well, but after confirming when I press ctrl+end and then click on the minimums knob a few times nothing happen. I tried several times and nothing. Then I changed the parameter to 1 and when I press ctrl+end I hear a click sound but still nothing happens. I changed again the parameter back to 0 and the click sound disapear but I can't get it working.Anyway, thanks for the help.

Thanks Emile, very straightforward, will try that out. I have been getting into LUA programming.* Orest

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.Thomas

Hi Emil!Thank you for your help.I don't know so much about FSUIPC programming but I tried anyway. I did everything like you said and assigned ctrl+end as well, but after confirming when I press ctrl+end and then click on the minimums knob a few times nothing happen. I tried several times and nothing. Then I changed the parameter to 1 and when I press ctrl+end I hear a click sound but still nothing happens. I changed again the parameter back to 0 and the click sound disapear but I can't get it working.Anyway, thanks for the help.

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 ?

Thanks Emile, very straightforward, will try that out. I have been getting into LUA programming.* Orest

Hi Orest,You're welcome, glad it's of use to someone. I actually didn't start looking into Lua programming until after the release of this marvellous PMDG NGX. That's when I found out that FSUIPC's mouse macro functionality wouldn't work with its panels so that I needed to find another way to access the functions that I wanted to set up on my modest home cockpit (Pete Dowson has since fixed that bug in FSUIPC). But the more I looked at example Lua scripts and the sophisticated things one could achieve with them, the more interested I started to become. It took a fair bit of reading up documentation followed by much trial & error (especially the latter :( ) but it's been well worth the effort.