MSFS Products

Hi everyone, I bought the RJ about a month ago so I'm still relatively new and still learning the full procedures but I've done a couple of full flights already and absolutely loved it. But on my last 3 flights in a row (and a test flight) I've ran into the exact same issue on approach - the plane wobbles from left to right constantly, up to the touchdown when using autoland. I've got no clue what the cause could be. I've been following the exact same checklist the whole time and it just suddenly started to appear a couple of days ago. In this clip I wasn't touching the controls and let autopilot do the whole approach and landing. I had about 5kts of crosswind but I don't think that's relevant (it happened on approaches with no wind as well) and even then it wouldn't make the plane sway the way it does. Can someone tell what the cause of this could be? Or is that normal and there's nothing wrong with it? It's kinda getting on my nerves already...

I tried this too, doing a quick RNAV flight from KPAE to KBLI. On approach into KBLI runway 16, I'm able to capture the localizer using RNV/APR on the KNS-81, approach mode on the autopilot, and RNAV selected on the GPS-NAV control selector. But while the HSI displays glideslope indicators, the autopilot doesn't capture the GS. My assumption is that I'm doing something wrong, but I did notice one thing. According to a KNS-81 manual I found online, the unit should recognize an ILS frequency and display no radial or distance information. What happens instead is that I can input both radial and distance data for an ILS frequency. Maybe the unit isn't properly recognizing ILS approaches? Or maybe I'm setting it up wrong. I'm not sure.

WORKING FINE NOW

Unfortunately, as you say, I believe this will be a limitation of using Chaseplane with some of our products. The Vulcan, and a few of our other products, rely on the core MSFS camera system to move the user to certain locations in and around the aircraft. As Chaseplane overrides the default camera system, the cameras that we trigger in the code no longer exist, so the camera will not change. It's something we have logged on our internal trackers for further investigation, and to see if there is any form of a workaround we can find for Chaseplane users. In the meantime with the Vulcan, it should be possible to create custom Chaseplane cameras inside the AEO/Navigrator compartment and then trigger those via the Chaseplane interface. Mark - Just Flight

@Joulz said in UNS-1: Database Expired: You keep saying that for 2 or 3 years... In the mean time,others devs such as inibuilds, pmdg or aerosoft implemented a way to update na data from inside the sim. So it shouldn't be too complicated. But apparently it's clearly not your priority, which is a little bit a shame for products of great quality that I otherwise appreciate. Just tired of hearing the same melody again and again... @Joulz said in UNS-1: Database Expired: You keep saying that for 2 or 3 years... In the mean time,others devs such as inibuilds, pmdg or aerosoft implemented a way to update na data from inside the sim. So it shouldn't be too complicated. But apparently it's clearly not your priority, which is a little bit a shame for products of great quality that I otherwise appreciate. Just tired of hearing the same melody again and again... Honestly, there’s no point in having an FMS with outdated data. It feels like a promise that's never fulfilled. Imagine if the Fokker 100 is released the same way? I definitely won't be buying it.

I'm not able to replicate that behaviour on my side with the latest version of the 146 and GSX, so it'll definitely be worth creating a ticket with Just Flight Support. In the ticket, if you could provide the information that you have in this thread, plus the video that you have recorded, then that will put our support team in the best position to attempt to replicate that, and log it for further investigation if required. Mark - Just Flight

Re: Feature Requests Can we please get an updated FS Traffic Manual that shows SETUP Global settings for the latest version of MSFS 2024 instead of ones that no longer exist (e.g. "TRAFFIC AIRPORT QUALITY"). Thanks.

Please see: https://community.justflight.com/post/46913 Mark - Just Flight

From our internal testing of the post-SU4 updates, we reliably see the correct state recalled on the first flight of a session, and then it becomes inconsistent on subsequent flights in the same session. Mark - Just Flight

@Derek said in PA-28R Turbo Arrow IV FS 2024 displayed wrong: Have you tried contacting Just Flight Support about this? It sounds like the kind of problem they could advise upon. https://community.justflight.com/topic/2/product-support Thanks, and sorry to the forum, I have sent a ticket, maybe this post can be closed.