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

Hi, I do not have the PMS. Only have what comes with the package. It's completely a matter of hit or miss. The same config sometimes yields to a successful ILS capture, sometimes the ILS does not capture. Yes, the indications are fine, the needles move as they should, but HDG mode remains active, APP remains armed but not activated. So far I only noticed this behavior when I was using a config which included the KNS81 RNAV computer, in which case, the issue happened more than 50% of the time. Yes, I always use the NAV 1 radio for the ILS approach, change the NAV source well in advance, change HSI source, the DME source. Everything is well prepared for the capture. I also tend to use HDG mode to intercept the localizer, even when my RNAV waypoint could achieve the same, I switch to HDG mode and expect the LOC to take over - but it does not happen consistently. I never noticed this before I started to use the RNAV computer. In the early BS days, the RNAV computer wasn't working with the autopilot and so I never chose a RNAV panel config - never experienced the problem of non-captured ILS either. But since I bought the new Baron, and since then the Duke, knowing the RNAV can be used with the autopilot, I actually use it a lot - and interestingly, the issue with the ILS appeared. Therefore, I dare to say this behavior is somehow related to the RNAV system and its methods of utilizing the autpilot. Perhaps 3rd party scnery also play a role here (I only fly to 3rd party scenery, never use stock ones, except for those "enhanced" ones). So it may be more than just one thing.

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

Stand down everyone. I figured it out. Well, not so much 'figured' but stumbled upon it. You know the saying 'If you throw enough s**t at the wall, some of it will stick'? That the method I used.