@jmarkows Oh. Very much sorry! I just copied without seeing what i got ! That was the PL REV! I sincerely hope i did not mess things up for anyone.. [image: 62c96042-c204-43fe-9d71-6c82006a6d27.png]

said in ND Data and Alt hold small bugs: @awde Looks like the standard reply should have been sent out which is basically "we will log these issues and pass them to the dev team". This was done but someone probably forgot to reply. Apologies for that. Meanwhile, the dev team is aware and will be looking at what's possible to resolve in a future update(s). Thanks for passing it on.

@Outermarker and @hangar_101 Thanks chaps for your wisdom regarding the Asobo tablet - I wasn't aware it could was integrated as a 3D device. Having it and the Black Square tablet combined in the cockpit is sounding like a great idea

Taxi and takeoff were uneventful (but the takeoff roll was SHORT - 400 feet MAYBE). Engine startup was easy lol - mags on mixture rich.

I’m not sure just how accurate the simbrief figures are. What I’d probably recommend is trying to determine your fuel requirements by using the figures in the manual (pages 167-8 for turboprop variant) which shows estimated fuel to climb and cruise PPH. You can use SimBrief for the routing, winds, ISA, and estimated time/groundspeed (if they have the right airspeed figures) and plug those numbers into the charts from the manual to predict fuel requirements. For example if climbing to 9000ft at ISA you’d need just under 5 gallons and then about 33 gallons per hour after that. If simbrief shows a 2.5 hour flight then you’d want about 90 gallons (about 600lb rounded up) before adding your reserve. The turboprop variant consumes a HUGE amount of fuel compared to the piston variant so it’s very easy to run out early. Sorry, I can’t say I’ve tried simbrief for the B36 yet so I’m not sure how close or far off the figures are.

Glad to hear it! Let me know if you have any more questions

What a wonderful note. Thank you so much. I hope moments like that can bring you joy in your virtual flying! Next time it happens, you can try using your real world procedure to burn off the deposits instead of pressing the "cheat" button. Have fun, and let me know if there's ever anything else I can do for you!

I apologize if I came across as impatient, I'm just excited to fly this plane with as much physical interaction as possible. Thank you again for a great add-on. I also got the Baron last month and put some hours in each variant. Wonderfully done as well. So, after a sleepless night and some consulting with ChatGPT (as I have 0 knowledge or experience with coding), I managed to get it displaying right. For anyone coming across this topic with similar issues, if you're using an ultrawide monitor you will need to play with the crop settings in index.html and the position in config.js until it aligns properly. [image: de765096-e84f-4bdc-81f1-d5b22980d0b7.jpg]

Nick? Anyone? I feel silly even asking but I would think there would be some indications of a fire.

I have a good amount of time in 172's (N-S models), the Baron BE55A, the Debonairs, and F model Bonanzas. The 172s won't quit at the min ground idle as long as you don't lean it out too much for taxi. The Beechcraft birds will and even at full rich at ground idle when cold. Almost all post-start checklists have you set the power to at least 1000 RPM. The Bonanzas and especially the Baron are relatively slow to decelerate on approach, especially if you don't have the flaps or gear out. I would guess that the low idle stop for the Beech birds are set lower than a typical training aircraft like a 172. I also suspect that some schools might ask their mechanics to bring the low idle up just a hair, so that new PPL students won't decelerate too fast in the flair when they are learning how to land. Edit, as Nick said. 750 rpm is way too high for low idle.

There is a work around, for the BS Dukes and Starship at least that’s what I had to do to get it. I’m on Xbox msfs2024, though I got the dukes in 2020 before I migrated to 2024 full time. They work 99.9% (wether radar not drawing correctly long standing Xbox issue. And the registration blacked out). Still show in library. so 2 weeks ago, I got sick of waiting. Reinstalled just the basic 2020 client. Got BS beechcraft 2000 starship in the Xbox marketplace. Deleted 2020. Had to give 24hr’s and it showed up in 2024 library. And works perfectly ( above weather radar issue aside. And if it don’t show, raise a support ticket, and they’ll manually replicate it through. I did it when there where Azure issues.

@lilycrose Same here, also on SU4 Beta. I really hope this can get resolved soon. I've been putting quite a few hours on the Bonanza and the Baron, it's a shame not to see the Hobbs meter go up...

Here is Rob's mod.. it seems to refer to the G36 model, so confused at to how that would conflict.. https://www.dropbox.com/scl/fo/vz8qm9ya1c9nr6raz0a5m/AKsFJ1WfeOLuotNtPYdckhM?rlkey=2kjgy1vms12p1i4f63bsysq97&st=g8y645p9&dl=0

I also experience a problem during initial climb with the airplane not accelerating from V2+10 to 210 kts. I'll test this further before creating a support ticket because I think there are some variables which might play a role (BeyondATC, takeoff procedure (normal, NADP), on TRK/HDK or following a LNAV SID, inappropriate engine derate), but this is what experienced last flight: The aicraft stayed at the same pitch after selecting a higher speed, activating LVL CHG didn't help either. Had to accelerate using VS before selecting flaps up. MSFS 2020 and BeyondATC. Just posting this here to indicate this might not be a MSFS 24 issue only.

@Bishop I'd be very surprised if it weren't an analog. I mean when has Black Square ever not done steam gauges? Ok, Starship, but that doesn't count that 80s glass cockpit is rad.

Upon further testing, other addons (like the SWS PC-12, FlightFX P180 and PMDG B737) still seems to work as intended, with ITT increasing as altitude rises and the engine power becoming ITT limited.

It's not currently possible to change the pilot voices in any of our aircraft; however, we do have it logged as feature requests that will be considered ahead of future updates to each product. Mark - Just Flight

There have been various improvements to this over the course of FS Traffic's updates; however, it's sadly not something that can be removed entirely without affecting the traffic generation at the destination airport. The small freeze is caused when the FS Traffic module detects that the player is within a certain radius of the destination airport, and starts to read the schedule files that are stored locally on your PC. Once it reads those schedule files, it'll start to generate the relevant traffic. The more schedules that exist at the destination airport, the longer it'll take for the FS Traffic module to read those; therefore, the size of the freeze is directly related to how busy the destination airport is. For example, if you approach a small to medium-sized airport like Manchester (EGCC), you may only notice a small stutter, but if you approach Chicago O'Hare (KORD) at rush hour, you will get a larger stutter. Mark - Just Flight

Thanks for the feedback. This is something we have on our internal feature request tracker as something we'd like to improve in the future. Mark - Just Flight