MSFS Products

Hello, I have noticed, that whenever I connect the GPU, but don't switch on the batteries, the cabin entry light illuminates, however does not give any light to the cabin. It looks like this: [image: 5fd9f620-d189-4da5-a950-0194f7c3b171.png] The same goes for other cabin lights, when I switch on the GRD SERVICE switch on the FA panel. [image: d50413d1-9d28-41be-9796-acfe9408ccce.png] The lights work properly only when Battery or GPU power is provided thorugh a cockpit switch. Anyone else is having this problem? Other than that the airplane is wonderful.

Dear Team, When comparing the data in the manual for the normally aspirated and the turbocharged variant you can tell that the turbocharged needs more runway and is a lot heavier than the normally aspirated - Which makes sense for the pressurised one. But the normal Baron with Turbochargers should perform better on takeoff than the normal one - or at least I can't think of any reason why not. Would it then be possible to get seperate data for the P and the TC Baron? Also, would it be possible to get some performance tables for the TC? On the internet I could only find a real world manual for the 58 and 58P, not TC. The MSFS manual lacks data specific to the TC and also doesn't contain and of the performance tables I'd need - like takeoff distance with varying temperature and different weights or cruise performance tables accounting for ISA deviation. Overall I'd be quite happy if there was a way to get my hands on a TC Manual including the performance section - can you help by any chance? Greetings, Jannik S.

Officially, we don't support any of our products on the MSFS Sim Update betas. The Sim Update betas are beta releases, so bugs are expected. It would almost be a full-time job in itself to keep all our products fully compatible with each beta update. Once SU4 fully releases later this year, we'll take stock and provide any necessary changes/fixes to our products to ensure compatibility. Mark - Just Flight

We're not aware of any brake issues in Vulcan, however, if you're using MSFS 2024 there have been some changes to Parking Brake control assignments in SU3 that could be causing a conflict. See: https://forums.flightsimulator.com/t/parking-brake-cant-toggle-on-off/734585 If brake issues exist in multiple aircraft, that typically points to either a control assignment conflict. Mark - Just Flight

Ha, ok, solved it. Apologies

@Woolies You're on social media at the moment

@otreblA said in No traffic at arrival airport: @Derek I'm not crazy or a liar. I didn't say you were. Just that we're not really the sort of business that has 'staff'. From time to time our small teams will work on all sorts of different projects. Sometimes they will impact each other - and I'm guessing this is what you must be referring to - but, most of the time, the team dedicated to one project generally don't work on others at the same time. We also have a number of freelancers. You suggested that your problem with FS Traffic may have been due to a lack of staff and I am just trying to explain that is unlikely to be the case. However, it's certainly true that if we are releasing a big title or a significant update in week 1, another similar thing will need to wait until week 2. To be honest, we wouldn't want to employ enough 'staff' to prevent this - they would spend the rest of the time twiddling their thumbs. With respect to Traffic, the last update was in July, as I mentioned above. The work on it since then has mainly been done as and when, and mostly involves looking into the various updates released for MSFS2024 to see if there is any chance of getting it to work with X-Box S. So far, no good. Getting back to your issue, if you contact Just Flight support with details of the problem they will certainly try and resolve it for you.

@Mark H Hi Mark - thanks for your continued follow-up and support - I have a LOT of controls and when I went through all of my assignments and cleaned everything up to just stick and throttle it works. So I indeed did have something bound which was jamming the throttle. My apologies for not doing a more thorough testing. Spent two hours in the plane already. Again thank you for your help.

100 percent the flaps are inverted. No aircraft goes nose down when the flaps go down. The aircraft in the aim slows down as it should and it feels like it has lift but it is 100 percent not supposed to be pitching nose down to the point you have to fully pull on the yoke to keep it from crashing.

Am I doing something wrong? Maybe I could alter my yoke's settings but compared to other aircraft I've flown in FS2020/24 it seems to me that this Piper Turbo Arrow III might be a bit lacking in 'lift'. Starting at sea level, aircraft weight ~2700 lbs., to lift off the runway at 60-70kts, with flaps 25deg, I use Trim+1 or +2 and STILL have to pull a fair amount on the yoke. Well, that's not a big deal, but I have a devil of a time on Approach. With flaps at 25deg, and then 40deg, I need a LOT of uptrim to hold the plane on descent to the runway. I use a setting of Trim=+10. That is a very different number from other aircraft. Am I missing something? What have others experienced? BTW, I can't edit the aircraft.cfg (does that still exist?), I'm on the Xbox platform. pete G in San Leandro, CA