[image: cf01951b-5fe0-4b55-8a65-2577915ea8e5.jpg]

Brilliant, thanks Mark!

Just adding feedback for the 'buzzing' prop while in cruise in latest update. This seems to be a regression from V1.0 as you would not hear this in the actual aircraft. Glad to see it will be corrected! I also notice this issue in the TP Bonanza along with other default MSFS aircraft (TBM comes to mind) You do not hear these prop sounds in-flight, it is only something you would hear on the ground or externally...

@Mark Thanks. I will test it again over easter and see if the problem still exists. I‘ve read that there are some people reporting similar issues with other products and even default aircraft here: https://forums.flightsimulator.com/t/unable-to-click-some-items-with-the-mouse-in-vr/758216/32 Seems to be VR related and probably something for Microsoft/Asobo to solve, not you…

@Black-Square the su5 beta also affected the Baron in VR in a similar way, click spots become very small and the tablet was unreachable. The releases notes did mention they were adjusting the interactions in VR so it wasn't a surprise to me. However it seemed to be fixed in the last update they pushed (within the last two weeks) - for me at least.

thanks. I finally solved it by using the same as I use for the FSR500. Button 24 on Bravo. Button Pressed Send THROTTLE1_DECR - event Delay execution for 200 ms (repeat 5 times) Button released Send THROTTLE1_cut - EVENT Works great in the Van !

I understand there may be higher-priority updates, but I think this particular feature deserves attention. The shader-based prop animation introduced in msfs24 is, in my view, a significant step forward. It removes that harsh and unrealistic transition between a static propeller and a spinning one, which has always been visually jarring. Beyond just looking smoother, it adds a real sense of volume to the prop disc—both from external views and from inside the cockpit. The way it interacts with lighting is also a big improvement. Reflections from the sun and other light sources feel much more natural, which enhances overall immersion.

So now I had time to check - sorry it was my bad. Too stupid question. In the failures tab there was activated "1x Realtime" and so I had a failure with this compressor. I did not expect this. But now I know that I should check this each time I fly. I love the study level details of your aircrafts....was just too stupid to realize this.

@fosl yup, same, that's why it's weird

Oh OK - that's what Chat GPT said I should look for in the config file and adjust :).

No I didn't know that, thanks for bringing it to my attention.

@SBS That's right. Also, if you bought the "Analog Caravan" before, there is a discount code found somewhere in your JustFlight account area for 10% off the bundle, or 20% off the individual packages (buying the individual packs will still be more expensive with the discount).

Gets us a free climb and descent.

Those SDK changes seem promising to my untrained eye, hopefully they're a step towards fixing things in the sim like how you can't reduce RPM in the TBM and compensate with torque; you'll just bleed off airspeed anyway. Of course, I'm sure they're subject to change without notice (or documentation) until SU5 drops

@Rich Hi Rich! I think I have noticed a bug with new installers you're using for the Caravan Pro. On initial install, you can select a custom directory, which I did for v1.0. However, after downloading the updated v1.1 installer from the website just now, here is what happened. Normally, the installers can handle updates themselves without having to uninstall the old version. However, this time, even though it said in the installers UI that is was updating from v1 to v1.1 - it did not respect my original custom directory. It deleted the old v1.0 files, and then installed the new v1.1 into the MSFS 2024 community folder like the legacy installers would. Could it be rectified so that when updating an existing addon with InstallShield, it respects your custom install directory of the existing installed addon? Thank you

The essential MSFS 2024 settings for FS Traffic can be found on page 9 of the FS Traffic Operations Manual: https://downloads.justflight.com/products/JFF003616/FSTraffic_MSFS_manual.pdf Looking at the screenshots you have provided, we would recommend setting Traffic Type to OFF in the first screenshot (this is a requirement for FS Traffic to prevent the simulator from generating its own default traffic in addition to FS Traffic). In the second screenshot, we would recommend that every setting from Character Quality down to Fauna Density be set to OFF or LOW. Most of these aren't a requirement (apart from Parked Aircraft Quantity, which generates default aircraft at gates), but we recommend setting these to their lowest settings for the best performance, as well as to reduce the likelihood of MSFS reaching a hard-coded limit on how many objects can be loaded in the simulator at any one time. Hope that helps. Mark - Just Flight

Hi there, I've since discovered that the effect can be modified by changing the entry in the aircraft.cfg file: effect.0 =Exhaust_1#(A:GENERAL ENG COMBUSTION:1, boolean)#FX_ASOBO_M_REACTORHEAT_CAP10 effect.1 =Exhaust_2#(A:GENERAL ENG COMBUSTION:1, boolean)#FX_ASOBO_M_REACTORHEAT_CAP10 For example you can change it into: effect.0 =Exhaust_1#(A:GENERAL ENG COMBUSTION:1, boolean)#FX_ASOBO_HEAT_BIG effect.1 =Exhaust_2#(A:GENERAL ENG COMBUSTION:1, boolean)#FX_ASOBO_HEAT_BIG While the intensity is now almost perfect for me, the exhaust stream is too far away from the exhaust pipe... Is there any way to move the stream closer to the pipe? Thanks in advance! Best regards

@BorisAudio Thank you! I dont like complaining about your work because I know you put alot of time and effort in to your sounds, but i felt like I had to say something

I haven’t come across any videos showcasing the v1.1 update just yet, but from your description, it sounds like exactly what I’ve been hoping for with the beta sounds. I’ll definitely keep an eye out for some footage and give it a listen when I can. Out of curiosity, do you have any kind of timeline (even a rough one) for rolling these sound updates out across your other aircraft, given your schedule?