MSFS Products

Hi Mark... Uninstalling and reinstalling worked... no message about out of date nav data... thanks, Rob

Thanks for this suggestion. I'll try it next time.

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

Nothing further to share on this at the moment. It remains something we would like to add to our aircraft in future updates, but there is no timeframe we would be able to share for that. Mark - Just Flight

It is expected behaviour that the APU TGT will vary depending on load. The APU has more load when the APU AIR/PACKS are ON, so EGT will increase. When the APU switch is set to OFF, it is expected behaviour for the APU RPM and TGT needles to instantly drop to 0 in early examples of the 146 (as we have simulated). This is due to power being removed from the APU ECU, which also removes power from the APU instruments (something which an ECU mod changed on later 146/RJ examples). The cabin temperature in the 146 is simulated to be affected by a variety of factors, including air supply, temperature selection on the Air Conditioning panels, passenger/service door position, and if the aircraft is in direct sunlight. If the aircraft's doors are open in cold weather, the cabin temperature will decrease. We're not aware of any issues with the APU remaining at 100% after APU shutdown, and we haven't seen any reports of APU EGTs as low as 100/200℃. However, if this is something that is repeatable behaviour, could I kindly ask you to open a ticket with Just Flight Support via the following link: https://www.justflight.com/support In the ticket, if you are able to provide steps for how to reproduce this behaviour, including the steps taken to set up the aircraft in the state in which this behaviour occurs, as well as the weather at the time, then our support team will be in the best position to assist with further troubleshooting, or pass this information over to the development team if required. Mark - Just Flight

Thank you Mark.

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

@Mark said in Aircraft Configuration Not Saved in MSFS2024: All of the items listed are included in our state-saving logic (and I have seen them save/recall correctly in the current build), but there is something which is causing discrepancies with the state saving with each load of an aircraft in a session. It's something we are actively investigating across various products. Mark - Just Flight @Mark Thanks for the heads up about the other thread. I have commented on that one as well and put in on watch in hopes something will turn up one day about it being resolved, or at least a work around of some sort. Although, as things tend to trend with MSFS from version to version, it might just be broken the next update. It's interesting that you mention you have seen them save/recall correctly in the current SU4 build; I would believe that. When testing earlier, there was an inconsistency in the behaviour of state saving, as not all items saved and recalled correctly on the first try. During the initial tests mentioned previously, the Fuel Pump Switch state reset back to OFF, even though it was switched ON before exiting the flight. However, all of the following tests it would remain in the ON or OFF state as expected upon save and restart. Likewise, the Transponder Code wouldn't always reset back to 7000, but would rather reset back to another value such as 2000, 7004, along with the standard 7000 - it would never set back to the pre-save value of 1200 though. The inconsistency adds to the frustration and makes it more difficult to debug, especially if the person trying to debug it doesn't have the code in front of them. Question for you and others on this thread: Have there been any workarounds that seem to result in an improved state recall, or has it just been inconsistent no matter the method? Thanks.

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