The C17 has many instances of HTML gauges around the aircraft (a total of 33 individual gauges given the massive size of the aircraft and complexity of the cockpit). Arguably this number could be reduced slightly to optimize the number of gauge instances that are individually rendered, however, problem seems beyond that.
In MSFS24, with Glass Cockpit Rendering Frequency set to HIGH, the CoherentGUI Thread is maxed out (red) and showing approx 40-50ms. Just that single setting drops FPS from ~50s to ~25 on my system
Dropping to medium improves significantly, green with spikes of yellow and around 20ms.
Dropping further to low, consistently green and 15ms.
However, the exact same aircraft, with the exact same gauges in FS20 is having very different results:
All settings maxed out, CoherentGUI is at maximum 11.2 Ms (!!!). That is at maximum refresh rate! Doesnāt even get anywhere close to the lowest refresh rate in FS24.
Therefore, and based on these, Iām drawing the conclusion that Coherent is being handled differently in FS24, and thatās having a massive impact in performance across aircraft - despite a general performance improvement all across. Glass Cockpit Refresh Rate is the one setting that consistently has, by far, the largest impact on any aircraft in MSFS using coherent displays.
Keep in mind this is on relatively good hardware, so our followers with lower end PCs are really struggling with it.
@FlyingRaccoon Pls high prio as it makes the aircraft completely unusable on Xbox.
We have identified that one of our gauges has a particularly high impact on performance (on PC at least), and we are attempting reducing such impact. However, we are unsure if this will do anything to Xbox.
Ultimately, the drastic difference between FS20 and FS24 does seem to indicate that there is an underlying issue beyond our control, and the complex nature of the aircraft just renders any other solution unfeasible.
This is really useful to know. In my gauges I create all the html elements āup frontā either in the html or the startup of the gauge, but Iām certainly changing the visibility of those elements during flight (e.g. style.display = block | none).
I already have systematic coding that skips updates in JS routines if the previous one was within some chosen timescale, so e.g. my distance-to-go updates only fire per-second, but thatās not going to avoid a stutter if the display update code accidentally includes an inefficient MSFS2024 method.
Any info about what html/js coding has become āmore expensiveā in msfs2024 is valuable, Iām prepared to make coding changes if needed
Bump - our Xbox community is wanting to enjoy the aircraft with decent fps, and we have been able to confirm that the single source of stuttering and performance issues on Xbox is the Coherent displays (basically forced a āinstrument blackoutā and FPS increased by over 150%)
One of our developers wanted to run a comparison between MSFS 2020 & 2024 on this aircraft but - correct me if I am wrong - it seems exclusively available in 2024 Premium Deluxe & Marketplace.
If you have a 2020 version that we can use for comparison purposes, would it be possible to send it to use through PrivateContent? Alternatively, are there aircraft available in both sims that exhibit the same behavior?
Moreover Coherent GT completely hangs a slower PC like mine Win10 i5-7600K during loading procedure at around 25%
Actually I found showing the console (that reports a Coherent GT error at that point) makes the sim jumping over it proceeding to complete the loading (with no console shown the loading procedure just stucks there forever)
I cannot look at your screenshot - for some reason its size seems to be very small. I am not sure the issue you reported has anything to do with the initial question - you should probably start a new topic with a bigger screenshot.
I meant creating a new topic on DevSupport, not in the official forums.
Do you still get this behavior now that carry-over has been largely deactivated?
I could be wrong but I doubt the issue is related to CoherentGT itself - if it cannot find a file thereās no reason why it should prevent the loading from completing. Unless some carried-over item has tried to override a core file of the UI and has completely destroyed the sim UI.
If I instead leave the console closed then the loading screen always shows 25% and there is no progress at all after minutes
If I open the console window before reaching the 25% the loading just stops at 25% for few seconds (with the usual error shown) than it proceeds forward
What is reall surprising me is that opening (and keeping it open) the console window actually makes the loading to proceed normally (apart some lables like āVFS Activating packagesā that are shown instead of the usual ones)
