Hi Jordi,

Make sure to restart XP11 after activating an aircraft, and reload the aircraft if you've changed the screen resolution or window size. You might also need to change the UI size to 100%.

Thanks
Martyn

Just to clarify, the lack of feedback is due to this not being a support forum so no guarantee of us reading every post.

Apart from submitting a support ticket, the best place to go for discussion of our XP11 aircraft is - https://forums.x-plane.org/index.php?/forums/forum/473-c152/

That forum is very active so the development team are usually lurking around and will answer questions where possible.

Our entire XP11 fleet received significant updates in early September to bring them up to the latest XP11.50 standards, including flight dynamics, as well as fixing a variety of bugs that had cropped up since the previous updates.

https://support.justflight.com/en/support/solutions/articles/17000085809-c152-xp-changelog

As Andy has posted, you can adjust the transparency of the menu arrow using your mouse-wheel.

We'll investigate the sounds and add any that are currently missing. There will be some differences in functionality and aircraft behaviour due to the differences in the two simulators.

@Mike-Cameron I have the same question, disappointed that this was never addressed. I took lessons in an old 150 and would like the old-school avionics.

Frankie, try this:
https://community.justflight.com/topic/533/figured-out-panel-selector-not-displaying-issue

@Voice-of-Reason Yup thank you!

@lesnyborsuk The update was sent out to all third party vendors last week so you''ll need to check directly with SimMarket. They definitely have the latest build from us. I'll also get someone here to chase our contacts up at Sim Market for you.

Just to confirm, the 3D pilot being visible in the cockpit is an indication that the SASL activation process isn't complete. It usually requires just a restart of XP11.

@stephane130281 If you haven't already done so, submit or update a ticket and we will investigate further, as this isn't an issue that we or our testers can reproduce at the moment.