146 Professional

@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

@highlander_821 couldn't agree more. Very nice job JF! I really like flying the BAe 146 in MSFS

Hi @Martyn and the JF team. Congratulations on the continued success of the 146, it's still absolutely a favourite of mine and I'd say you've taken it to the next level in MSFS. I'd also like to commend you guys on your excellent approach to user communication and change logs etc. Best in the business.

Sorry for resurrecting this old thread, but just wanted to loop back regarding the sounds.

One thing I've noticed, as per my original post, is that the engine buzzsaw sounds do not seem to fade at cruise altitudes (22/24/26k ft). From my experience as a pax sitting in the first few rows of the 146, the engines usually fade to just a low frequency hum, being completely masked by wind noise.

Is this something you're able to improve?

@hains

Thank you very much. The answer already helps me. The TGT cruise mode is a little illogical to me. The mode and the speedlimitations are not coordinated at all. But if the aircraft was designed that way, then that's the way it is. Now I know that you have to lower the TGT temperature so much. Thank you.

@voice-of-reason gotcha, any ideas on time frame?

Hi Martyn,

Thanks for the response!

That's unfortunate if you are constrained to only being able to read that title. Seems like a silly limitation :(

It's less of a repainter issue and more of an end-user issue. Are you aware of Flightsim Economy (FSE)? It's a cross-sim multiplayer persistence layer (kind of like a sandboxy career mode).

FSE has a database of recognized livery names called "aliases" and it's really common to have to rename a downloaded livery that isn't in FSE's database to one that is so the client will accept your flight. That works fine, but it's also common to rename a livery to identify as a different but similar model of plane.

For example, if you own a Cessna 172 in FSE but you want to fly your Piper PA28 Arrow, you could buy an Arrow in FSE but that's expensive. You could also just rename one of your PA28 liveries to identify itself as a C172 and because the two are very similar capabilities-wise (four-seater piston props) the FSE client will accept that and let you fly the PA28 in place of the C172.

In FSE a 146 is one of the most expensive planes to buy, so I wanted to just alias it onto something my group already owns, and then I discovered that it crashed the game :P

Anyway, in case you were curious how I discovered it now you know.

@Lairyliam
Select "Wide Angle" as the default cockpit view in MSFS Options. That will give you the familiar out-of-the-window view.
Not sure why the devs chose the instruments only view as default, it seemed a little odd to me too.

Well, the Bae is going to be perfect. But unfortunately not the lights. The lights should illuminate the hull more. See the difference between the 300 and 100/200 version. In 300 version the lights illuminate the front of the hull. a little, but not at the other versions. The lights are very important for the realism. and the lights make a model much more attractive. See also my first statement to this subject. Anyway, this plane is absolutely great.

I think Grue is probably correct. I have the Honeycomb Alpha and Bravo and had the same problems that you are experiencing. I made separate profiles in MSFS for the Alpha and Bravo for the BAe146 and made sure all the lights/APU etc weren't assigned to any buttons and switches. Once they were all deleted every switch worked perfectly.

Bruce R

@melon said in Fuel Flow/Burn:

@johan217 Oh that is really interesting, where does one acquire these sorts SOPs?

Some of these are floating around the interweb. I got this one from scribd (requires subscription, so I don't think I can share the full pdf here, sorry).

@b3lt3r Yep. Oh, it still had the synchronised doors/chocks/etc too, so hopefully that can get changed at some point.

G'night.

@slinger There is no way to retract the gear after manual extension, just like the real aircraft, but following the v1.6 update you need to click on both the emergency gear release door and handle to extend it, so inadvertent selection should now be very unlikely.