That is the way it is on the real 737NG !!

Well... we know that. That's why I'm saying it LOL . The animations are wrong as well, but it's been noted before. On the NGX they are rotaries, and the BARO knob (QNH) suffers from the same. I let Tabs know like weeks ago, but I'm sure it won't make it for the SP. It didn't for HF4, and I suspect it's way too minor to get fixed anytime soon. Too bad. But the keystroke approach should serve as a workaround for now, I believe.

Here's the code MINS INC

local socket1 = require "socket"    	KNOB_SENSITIVITY   = 50    	KNOB_DECEL_THRESHOLD  = 50    	KNOB_ACCELERATION   = 5    	thisMINinc = socket1.gettime()*1000    	lastMINinc = ipc.get("lastMINinc")    	lastMINincFAST = ipc.get("lastMINincFAST")ipc.set("lastMINinc", thisMINinc) if lastMINinc == nill or ((thisMINinc - lastMINinc) > KNOB_SENSITIVITY and (lastMINincFAST == nill or (thisMINinc - lastMINincFAST) > KNOB_DECEL_THRESHOLD)) then    	ipc.control(69987, -2147483648) else    	for i = 0, KNOB_ACCELERATION, 1 do            	ipc.control(69987, -2147483648)    	end  ipc.set("lastMINincFAST", socket1.gettime()*1000)    	end

MINS DEC

local socket1 = require "socket"    	KNOB_SENSITIVITY   = 50    	KNOB_DECEL_THRESHOLD  = 50    	KNOB_ACCELERATION   = 5    	thisMINdec = socket1.gettime()*1000    	lastMINdec = ipc.get("lastMINdec")    	lastMINdecFAST = ipc.get("lastMINdecFAST")ipc.set("lastMINdec", thisMINdec)if lastMINdec == nill or ((thisMINdec - lastMINdec) > KNOB_SENSITIVITY and (lastMINdecFAST == nill or (thisMINdec - lastMINdecFAST) > KNOB_DECEL_THRESHOLD)) then    	ipc.control(69987, 536870912) else    	for i = 0, KNOB_ACCELERATION, 1 do            	ipc.control(69987, 536870912)    	end  ipc.set("lastMINdecFAST", socket1.gettime()*1000)    	end

It's not quite like that on the real aircraft - the controller essentially has three positions, left, centre and right, spring loaded to centre. Giving it a very quick 'tap' to one or the other will change single digits (ie from 100 -> 101) and giving it a longer twist changes the tens of units (ie from 100 -> 110). Holding the controller to one side will keep changing the tens, but the counting speed will accelerate after a few seconds. We regularly go from as low as 344' (FACT) to a higher value such as 5694' (FAJS), and it's a pain in the real plane too. The absolute best method I've found in FSX is the mousewheel, which is faster and easier than the real plane IMHO.

and it's a pain in the real plane too

Haha thanks, good to know! In you are camera equipped, would you mind shooting a tiny video of the knob operation on one of your next flights, how approximately the acceleration is on the real deal? But only if your time allows.I'd appreciate it very much!

If you load up a fresh flight (from no saved loads) and follow standard cold and dark startup procedure, the mins will start at 50 feet. If you start from a saved flight or some other startup anomaly, the mins startup at 9000+ (in my case), and you might as well forget it. Known issue since day one. I thought they had it on the "fixed" list, but apparently not. Originally, I thought it was some kind of "newbie hazing procedure".