146 Professional

I just discovered that increasing the gauge refresh rate to maximum greatly improves the ratio of good screen to bad screen. Now it only flickers to the bad screen in my image about every 6 or 7 seconds, and then just briefly.

Just for the record in case somebody else has this issue: I had my throttles bound to: THROTTLE1_SET THROTTLE2_SET etc I changed this to: THROTTLE1_AXIS_SET_EX1 THROTTLE2_AXIS_SET_EX1 etc And now it seems to work fine! Back in the air!!!!

@taipan303 said in BAE146 RUNWAY PERFORMANCE SPREADSHEET: @derek haha I think I'll leave the combat to DCS and IL2. Microsoft have given me plenty of bugs in Windows, so I should probably buy more software so they have the money to fix them hey ;) That's the idea. Not sure MS are alone in producing software with bugs.

@fragron just did the mod, works beautifully :) Don't get any indication on the FMC about the address, but I just type in my IP and the port from the readme and it works

There is a simple method which works reasonably well and as a simple soul even I can work these out in my head. DESCENT POINT - DIVIDE FLIGHT LEVEL BY 3 So FL300 divided by 3 is 100. So you need to start your descent 100 miles from destination. Keep checking during the descent, so passing 10,000 ft, 100/3 = 33 miles from touchdown. RATE OF DESCENT TO MAINTAIN A 3 DEGREE APPROACH- MULTIPLY GROUNDSPEED BY TEN AND HALVE THE RESULT Groundspeed is 400 KTS. 400*10=4000. 4000/2 = 2000FT per minute Rate of Descent You need to recalculate as the aircraft slows down in the descent. So on final approach GS around 120 KTS. 1200/2 gives you a rate of descent rate of 600 FPM. Hope that helps

@martyn Thank you very much Martyn! I really like the way you explained it. I like the planes but also the feedback from the staff on the forums. Kind regards, Davy Wittebols WITTEBOLS PRODUCTIONS

@rob-lockett Thanks, I wasn't aware of that. Learn something new every day

@sbanks75 Yes, that's correct. Hopefully our support team will be able to resolve your issue with IAS hold as I've never encountered that.

@martyn Ok, alright. That explains it. Thank you Martyn.

@melon yeah - I remembered that from early days with the good old CJ4 from WT :-)

@tommchowat As long as it works for you and you are happy, who cares?:winking_face: I am happy to hear that it is working for you. Nice flights!

@flusi2004 I missed anything in the changelog for 1.7 about fuel - only saw the simconnect adjustment. I suppose if you were happy with the prior version you could try reverting to that? Or maybe disconnect the Bravo and just see if APU behaviour changed. At least you have the 737 to keep you occupied - I'm waiting for the -800 to drop and then I'll grab that for sure.

@mags885 LOL! Well if the panel works OK with a default a/c like the 172 or G58 then your Logitech plug-in is loading in fine and should work as-is with the 146 assuming all your avionics and radios are switched on in-sim. If you haven’t got it working with stock a/c go here: https://support.logi.com/hc/en-au/articles/360024698434--Downloads-Flight-Radio-Panel and select your O/S and download and install the plug-in. If you’re lucky, the plug-in will start with MSFS automatically and you’re all set. If worse comes to worst you’ll just need to launch the plug-in manually before setting up a flight in MSFS. Get it running with a default a/c and it’ll run in the 146 with nothing extra to do. Good luck!

@09tir98 Yes, the UNS-1 is in development