My great uncle flew around the world with Bob Reiss in N9675R, a converted A36 Bonanza with an Allison B17. In the 1994 trip they had an engineering firm plan out and engineer 100 gallon tip tanks (670lbs). After installation it was clear that even though in flight the bending moments margin would be adequate (although reduced), the taxiing was the largest issue with higher accelerations in the Z+ and Z- directions resulting in a limitations that only 55 gallons could be carried. So the stock bonanza can, if begrudgingly, carry 55 gallons on the tips. In his recollections of the time, he stated that it was common in the more remote areas to take off about 50% over MGW when fully loaded with fuel compared to a stock Bonanza. He would say that it flew, it just had to get going much faster to do it.

@AlpraziTech @KAPA-Flyer bickering on the forums won’t get issues fixed any quicker, but may lead to a timeout. Your posts have been deleted as they add nothing helpful to the topic. I’m sure those that deal with such things (not me) will resolve any issues as soon as possible. I know nothing about the MS Marketplace process so can’t help with any finger pointing you may wish to make.

I do believe you've converged on my would-be answer here. I will reduce the severity of the experimental message next time I update Starship. I will probably leave it in place for some scenarios, however. They all have slightly different wording, which would have helped me troubleshoot things, but it seems that the release of this feature went relatively smoothly. Thanks for letting me know how you're using it

@goose-28 Have you read in the manual about using the native 2024 package reorder tool? That should be able to accomplish this by moving Real Taxiway's priority below the handcrafted airports. I configured the package so this should happen by default, but there's a reason the package reorder tool is under the "experimental" options, I guess.

No issues on my end, make sure you have the correct CDI source on the 750?... Very common mistake that I've seen in training irl.

said in KA350 unknown LVars and events collection thread: Hi folks, Did somebody manage to find the variable for the wipers ? I'm using a stream deck plus with pilotsdeck plugin and managed to edit a profil with everything i want, except the wipers. Could be very useful when you break out of the clouds during low ifr approach and don't have the time to switch to the overhead view... Whaaooo. That was quite difficult but i finally found it !! After a deep dive inside the Analogkingair.xml, i found this : <CIRCUIT_ID_WIPERS>54</CIRCUIT_ID_WIPERS> <CIRCUIT_ID_PARK>55</CIRCUIT_ID_PARK> So i tried : (A:CIRCUIT SWITCH ON:54, bool) and it works (but only for slow speed). (A:CIRCUIT SWITCH ON:55, bool) is to set the wipers to park position.

@Moonflower_414 It's a Microsoft side issue, I think. The TBM did the same thing.

Thanks, "SynchFplWithFsATC = 0" did the trick. Just hoped to read this information a few months earlier ...

Hi. It must be a problem with my rudder pedals ("MFG Crosswind V3"). After disconnecting them, the Parking Brake works as intended and can hold my plane even with full power applied. Strange, as I only have assigned both braking axis and the rudder axis to those pedals in MSFS. Adjusting the Deadzones with the Config Tool of the Pedals also brought no help. Does anybody have an idea? regards, Benni

I believe this was discussed here not too long ago, and it was the result of an option within the TDS options interface, but since you said that it's working in one aircraft and not another, I'm not so sure. There should be no difference between the two aircraft in that respect, but it's always possible that one of several thousands configuration settings betrayed me between the aircraft. If it's not a user-side option, if you can figure out what that configuration setting might be from the TDS community, I would be happy to check it in the Baron.

Ah, I forgot about that. Have FSUIPC send >H:MFD_Joystick_Center after all the other events. If it doesn't work, there see if there is a way to add a tiny delay (like 50ms) between the directional event, and the center event.

@dave_pilot I have been flight simming since FS9 too and have avoided trying new experimental AI features for the same reason. Good luck

Hi @meh1951. That worked! I had the event with the "PROP PITCH DECR" actions and it put the prop lever in the feather position, but didn't always feather. This worked right off the bat. Thanks.

Ok, thank you so much for the heads up.

@FlimsyBagel Don't thank me, thank @dejw6! Or Ramasurinen, dev of Albatross on an official MSFS forums. He wrote same tip today.

If it's only happening with the #1 condition lever, then I would further suspect a control binding issue. I know you said you already looked, so I apologize for the emphasis, but it sounds like a control axis overriding your mouse action to me.

@Buzz Very cool, thanks for the find