MSFS2024 compatibility?
-
Last night I removed the PMS GTN750 stuff from my Community Folder (MSFS2024) and then fired up the sim and the Grand Duke. The stutters unfortunately remained for me...
And I do have the most recent version of the PMS 750 suite. So I guess I'm gonna have to wait and hope that Asobo can get CoherentGT working better in MSFS2024. Ugh! I miss the Duke and the TBM 850. -
@ Tap Road
Update: When piston is removed from community folder then all liveries are shown for turbine duke.
I suggest that BSQ investgates a potential conflict when both versions are installed in community.@notedmoyai This is due to how Asobo changed the aircraft selection menu UI grouping. I know what can be done to fix your specific problem, but as you've probably seen, strange liveries are shown as the main aircraft, and variants are often hidden among the liveries. Believe it or not, the current aircraft selection menu displays thumbnails in random order, influenced by the order in which the files were loaded from the community folder! Hence, if you removed the Turbine Duke, and then added it back, you would find all the Piston Duke liveries hidden under the Turbine Duke. I can currently do some things to improve the situation, but there is currently no way for developers to display aircraft variants or liveries in the order we desire for them to appear.
-
Thanks for sharing your report. Here is what I wrote elsewhere on this forum about the potential cause of stutters within the last 48 hours:
"I have been looking into these stutters recently, as I have seen them reported with all of my complex aircraft, and several other complex 3rd party aircraft in MSFS 2024. This surprised me, as I take a substantial effort in development to make my aircraft frame rate friendly. I suffered for too many years with a lower-end PC not allowing me to enjoy the aircraft I wanted to fly for my users to face the same dilemma, so performance has always been a top priority of mine.
Unfortunately, to the best I can tell, this is a MSFS 2024 problem with the CoherentGT system used to render avionics and my tablet displays. Asobo has said that they are working on a solution in our developer forums, and there may have been some improvement in SU1 Beta already, but other developers are reporting that there is still a significant loss of performance and stuttering for Coherent-based avionics. I will keep you updated if I learn more, or if there is anything I can do to mitigate the problem on my end. Hopefully they will correct this problem so that we can have the same performance that we did in MSFS 2020."
It's very unfortunate that we are experiencing these steps backwards with the new simulator, but it's also very difficult for us developers to predict what is worth pursuing on your own, and what might "fix itself" with the next sim update. Unfortunately for performance issues, unless there is one single function call that causes the issue, only a drastic change of core software architecture could remediate the issue if the problem really does lie within changes to the CoherentGT system. Like I said, I will keep you all updated as I learn more. Thank you for your patience.
@Black-Square Looks like the stutters have been fixed, or at least improved with the latest SU 1 beta. I've only done one flight but I didn't have any stutters at all. Hopefully it wasn't a one time thing.
-
I've scrolled though all of this thread but not come across any mention of magnetos in the piston Duke. Magnetos 1/2 inc/dec have no effect and I can't find any other command in the manual that works.
If this is an MSFS 2024 issue then I'm happy to use a mouse to turn them on/off. If there IS a secret command it would be nice. Other than that, I'm happy to use the Duke in 2024 because there's nothing else that spoils a beautiful plane. (Dynamic registrations apart)
Keep up the good work.
-
After a lot of trial and error I've had a sort of success. I've managed to get both switches to go from Off to Both with no stops in between. I've not been able to get them to go one step forward to Start.
Hello, hello, hello o o o o -
Don't worry, I'll try another plane.
-
@Ron-Attwood There are B vars you can use if that suits your fancy. I have SPAD.neXt configured to send the following:
B:BKSQ_MAGNETOCONTROLLER_(L or R) = 0 (OFF)
B:BKSQ_MAGNETOCONTROLLER_(L or R) = 1 (Right)
B:BKSQ_MAGNETOCONTROLLER_(L or R) = 2 (Left)
B:BKSQ_MAGNETOCONTROLLER_(L or R) = 3 (Both)
B:BKSQ_MAGNETOCONTROLLER_(L or R) = 4 (Start)If I recall correctly the MAGNETO_SET1/2 event can be sent with the same parameters and it works, too. Thus, you can "increment" that event in the simulator key mapper (if not using an external mapping program) to have the same functionality.
-
Thanks for this. I was thinking this place was abandoned. I am using those assignments but didn't use 4 as it went straight to Start. You may gather that I'm not au fait with these types of code doohickeys. But I'll play with it a bit more before throwing in the towel. Why on Earth not MAGNETO_1_INCREASE/DECREASE like everyone else?
I know, Assobo, right?
-
Forgot to add. I use FSUIPC7
-
Right! Got it sorted. 4 for the 'On' + Repeat when held. Starter has a little dig but I'll live with that. Can't do a mag check though but I'll live with that as well.
Thanks again for replying, I appreciate it. No need to look for another twin now.
