MS Store version:
C:\Users\YOURNAME\AppData\Local\Packages\Microsoft.FlightSimulator_RANDOMCODE\LocalCache\Packages\Official\OneStore\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\BaseInstrument.js
To edit the BaseInstrument.js file I suggest to use a code editor as Notepad++ or Sublime Text (both free). Backup the file making a copy on your desktop to restore it in case you encounter any problem.
This is the part to be edited (line 235 in my case but may be different):
CanUpdate() {
var quality = this.getQuality();
if (quality == Quality.medium) {
if ((this.frameCount % 8) != 0) {
return false;
}
}
else if (quality == Quality.low) {
if ((this.frameCount % 32) != 0) {
return false;
}
}
else if (quality == Quality.hidden) {
if ((this.frameCount % 128) != 0) {
return false;
}
}
else if (quality == Quality.disabled) {
return false;
}
return true;
}
and overwrite it to his new code:
CanUpdate() {
var quality = this.getQuality();
if (quality == Quality.high) {
if ((this.frameCount % 3) != 0) {
return false;
}
}
if (quality == Quality.medium) {
if ((this.frameCount % 8) != 0) {
return false;
}
}
else if (quality == Quality.low) {
if ((this.frameCount % 32) != 0) {
return false;
}
}
else if (quality == Quality.hidden) {
if ((this.frameCount % 128) != 0) {
return false;
}
}
else if (quality == Quality.disabled) {
return false;
}
return true;
}
All that is changing is that you are adding in these lines:
if (quality == Quality.high) {
if ((this.frameCount % 3) != 0) {
return false;
}
which are setting a refresh rate of the screens when in the cockpit (quality = high) and it’s setting a division of your screen refresh rate (144/3, or 60/3 or 120/3, whatever) and you can change that ‘3’ to be whatever you want. The higher the number, the smaller the end refresh will be and the better performance you should get but the more choppy the little screens will refresh.
Hope this helps some people to get better FPS. Surely helped me a lot!