Created by: Aptriva Ltd (Not me!)

Uploaded by: photogaff (Also not me!!)

MEOW!!

https://www.nexusmods.com/microsoftflightsimulator/mods/109

This particular fix for airliners goes straight to the processing of the data for the individual instruments/screens, preventing the CPU cycles from being used, rather than skipping frames for rendering (which does have an impact, but would still result in wasted CPU processing of data of the skipped frames).

Update September 9th 2020 - v0.1.03 - Update includes optimisations for instruments in the Airliner cockpits (lower latency on non PFD and MFD instrumentation), added instrumentation tuning for Aera, AS3X, AS1000 (MFD and PFD), AS3000 (MFD and PFD) for other aircraft included in MSFS.

Added Benchmarks:

• 21FPS improvements in the Beachcraft King Air 350i
• 17FPS improvements in the TBM930
• 10FPS improvements in the DA62

Update September 6th 2020 - v0.1.02 - Some changes to include the AS3000 instrument on 15ms timings, as well as moving the FCU instrument to 50ms timings.

Having looked through the source code of a lot of MSFS, it appears that there are some further improvements to be made around the place. I’m aware of other fixes, however this particular fix for airliners goes straight to the processing of the data for the individual instruments/screens, preventing the CPU cycles from being used, rather than skipping frames for rendering (which does have an impact, but would still result in wasted CPU processing of data of the skipped frames).

This fix affects the file BaseInstrument.js located in: asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\

The updated is self contained inside the createMainLoop() function, which takes a targeted approach of deciding what sort of update times should affect which instrument or range of instruments.

• 19 FPS improvements in the Airbus A320 Neo
• 16 FPS improvements in the B747-8i
• 15 FPS improvements in the B787-10

You can probably squeeze out further improvements, depending on the level of latency you wish to have on your instrument displays, but this has resulted in a great improvement in FPS for my setup.

I’m operating on:

• Intel i7-4790
• 32GB RAM
• AMD RX 5700
• Samsung 860 EVO SSD (game disk)
• 3440x1440 full screen

I started working on the G1000/AS1000 instrument timings, which are a lot more sensitive to higher values (it shows notable stutter if the value is above 20ms, so there must be some sort of layered processing going to cause that effect). Leaving the G1000 at 15ms appears to keep it happy and doesn’t degrade performance. Effects are minimal, but it’s helpful to have that in place for tweaking if it comes in to effect in later updates of the game.

Installation

• Step 1: Extract the single folder contained in the downloaded ZIP file and place that folder in:
• MS Store Version: %homepath%\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\
• Or more directly: C:\Users\<yourusernamefolder>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\
• Steam Version: %homepath%\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\
• Or more directly: C:\Users\<yourusernamefolder>\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\
• Step 2: Start the game cleanly, making sure not to try to use the fix whilst the game is still running (close down game and start it cleanly, so that the fix is loaded on game start from the community folder)

 

Edited September 9, 20205 yr by HiFlyer

Any plans to implement these improvments on the PL21 found in the CJ4?

Does anyone know if these enhancements work for the glass screens in the Virus 121?

Interesting.  I'm currently fairly happy with the FPS limiter method for glass cockpits, but I do get a bit of stuttering.  Is this an even bigger improvement?

I hope Asobo implements the glass cockpit FPS fix in their next update so we don't need to use community fixes like this.

1 hour ago, Langeveldt said:

Interesting.  I'm currently fairly happy with the FPS limiter method for glass cockpits, but I do get a bit of stuttering.  Is this an even bigger improvement?

Its likely going to be dependent on settings and hardware. Best bet is to try it yourself.

Is this compatible with the glass cockpit fps tweak?

I guess I'm gonna find out 😉 

Ok so initial remarks from me is that with the cpu and fps fix my cpu is working much harder. Sitting still in the cockpit at EDDF at night gives me close to 100% cpu load. 

1 minute ago, Andreas Stangenes said:

Ok so initial remarks from me is that with the cpu and fps fix my cpu is working much harder. Sitting still in the cockpit at EDDF at night gives me close to 100% cpu load. 

But what about frame rates in glass cockpits?

Well I have my frames locked at 30 with the occasional drop. I'll let you know if I think this is in any way smoother. I highly doubt it with so high cpu load. 

15 minutes ago, Andreas Stangenes said:

Ok so initial remarks from me is that with the cpu and fps fix my cpu is working much harder. Sitting still in the cockpit at EDDF at night gives me close to 100% cpu load. 

It seems to suggest that you pick one solution or the other.

Several of the feed back posts stated that it breaks, freezes the vfr map.  Use at your own risk I guess.

38 minutes ago, Andreas Stangenes said:

Ok so initial remarks from me is that with the cpu and fps fix my cpu is working much harder. Sitting still in the cockpit at EDDF at night gives me close to 100% cpu load. 

What CPU are you running and at what Ghz...?

45 minutes ago, Kilo60 said:

What CPU are you running and at what Ghz...?

An i7-6700k at 4.4ghz ht on. 

I was able to fly a leg between EDDF and EDDN tonight on vatsim with both fps fixes enabled. I didn't like how it felt, although I didn't have any stuttering. The cpu kept being buzzed at 100%, which occasionally does happen to my cpu with just the glass cockpit fps fix "of old", but now it was almost constant. As a result, audio kept cracking. Frames we ok - locked at 30.