Caravan Professional

@asnamara Wonderful! I'm glad I could make the improvements you were looking for. I never promise that it's perfect, but with every piece of feedback, hopefully it gets a little better

Hey. Yeah, having the same issue. Can't read the labels in VR during daylight. And I am running a Meganex8K with a 4090, so there are a lot of pixels rendered, but this still isn't enough. Luckily there aren't that many switches, so I just memorized them. But I also have the problem with very bright sunlight making the gauges a bit dim. This seems to be a sim problem. Had that in other planes too. In MSFS 2020 you could mitigate that effect by turning on the gauge lighting, but in MSFS 2024 it doesn't work until it gets darker outside. Made a bug report about that ages ago, but didn't got enough votes to be looked at.

thx for confirming. BTW I am currently in Honduras on my way to Belize

The one on flightsim seems to have been taken down. A2a has one that came with the Aerostar but it doesn't seem to work any more either. I'm guessing Asobo broke it with SU4.

For Axis And Ohs I managed it, changing the Interior.xml a bit. At the component ELECTRICAL_Switch_Alternator_1 I added this code: <OVERRIDE_ANIM_CODE> (L:var_GeneratorSwitch, number) 1 == if{ 0 } (L:var_GeneratorSwitch, number) 0 == if{ 100 } (L:var_GeneratorSwitch, number) 2 == if{ 200 } </OVERRIDE_ANIM_CODE> Afterwards I used the "Layout Generator" from fs.to to recalculate the layout.json. Now I'm able to control the Switch using something like 1 (>L:var_GeneratorSwitch, number). @Black-Square It would be great if you could add this to one of the next updates. This was already missing in the 2020 version and drove me nuts.

Thank you very much for your advice - greatly appreciated.

Agreed and the OAT gauge top left. The deg C does not match. Dunno about F.

Is there any connection to the surface modeling from the simulator? I've found similar behavior with another popular 737 previously that once at a set taxi speed, it never changes. I see this as well with the Caravan. If I am in Beta at 15kts - It will tend to stay at 15kts. If BETA is ZERO thrust from the prop, I'd expect some friction and other forces to begin reducing the taxi speed where I will eventually need to pop out of beta to maintain forward speed.

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

@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.

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

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).

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

It would be great to have a single tablet solution. Perhaps the BlackSquare tablet features could be integrated into the MS tablet, similar to what Sky4Sim has done. The new SWS Kodiak, for example, already includes the MS tablet mounted on the yoke. Since the MS tablet supports Navigraph charts, SimBrief, and other plugins, having everything unified in one device would be extremely convenient. Just sharing my thoughts.