MSFS Products

For any WASM crash-related behaviour, we would recommend opening a ticket with Just Flight Support via the following link: https://www.justflight.com/support If the WASM crash is reproducible, please provide steps on how to reproduce it in the ticket, as well as the platform you are using at this time (PC 2020, Xbox 2024, etc.). That will provide our support team with the best information for tracking and reproducing this behaviour. As the initial topic of this thread has been fixed in the most recent updates to our products (changes in SimConnect logic in SU4 causing the flight to hang in the 2024 loading screen), we will lock this thread to prevent confusion with unrelated topics. Mark - Just Flight

Just to double check, there are two separate settings in the menu, "Crash Damage", and "Aircraft Stress Damage". Do you have both disabled? I think it's only the stress damage setting that actually needs to be off to avoid the "open door = instant crash 'feature'" of MSFS.

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

FS Traffic does include Norwegian liveries by default; however, as there are various "Norwegian" airlines, all with slightly different carrier ICAO codes, I believe there are some ICAO codes that aren't being correctly assigned these liveries. It is something we have logged on our internal trackers, and the development team will investigate this ahead of the next FS Traffic update. Mark - Just Flight

[image: 52160b1a-9f73-48d0-b7b1-6d5dcc4c1963.png] This is what I getting as the map.

After doing some additional tests, it appears that only certain items save state properly for the instance. The following ARE set back to the way they were (ie works properly) when I closed the flight and reloaded it: Battery and Alt Switches Fuel Pump Switch Landing Light Switch Anti Collision Light Switch Pitot Heat Avionics Master Switch Transponder state switch - Off, Stby, On, Alt, Tst Fan Speed - Hi, Off, Low The following are NOT saving and are reverting back to their default: Transponder Code - It resets to 7000 normally, but sometimes 2000 or 7004, which is odd. Throttle - It would reset to fully closed (ie fully down) Mixture - It would reset to cutoff (ie fully down) Parking Brake Switch - It resets to ON Carb Heat Switch - It resets to OFF Comm 1 and Comm 2 Frequency - Each resets to 124.850 for both active and standby. Nav 1 and Nav 2 Frequency - Each resets to 110.50 (Active) and 113.90 (Standby) Altimeter Setting Nav/GPS switch next to the Nav 2 VOR Note 1: If it wasn't listed above as saving or not saving, I didn't test to see if its state saved or not. Note 2: During each test I am using the save livery / tail number. Note 3: It appears using End Flight or Main Menu to exit out of the active flight works when restarting. I also tested exiting out of MSFS 2024 and reloading, and it appeared to work but I didn't test multiple state changes for that. The aircraft is setup as follows in the EFB: Auto Fuel Selector - Disabled (Black background) GPS: WT GNS DUAL - Enabled (Light gray background) State Saving - Enabled (Light gray background) HSI - Enabled (Black background)

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