2 hours ago, Nyxx said:

Really! never know that trick will disable it, thank you. Were in option is that to disable it?

Its in the in game menu at the top....the little white drop down where you can change the weather , etc on the fly...just select the spokewheel and disable as many icons in that menu as you want. The VFR map is one of them. I tested it out and sitting at KLAX I was at 38 FPS. disabled...43 FPS. Enabled again...38 FPS. Disabled again..43 FPS. 

9 minutes ago, alexcolka said:

So this is adaptive to your current fps

essentially yes...technically its adaptive to an overall average of your fps over time.

 

9 minutes ago, alexcolka said:

there is no way to lock the 2d display refresh rate?

I dont think we know the answer to that yet, but as of right now we dont have a way to specify it (ala PMDG).

Edited August 28, 20205 yr by hangar

46 minutes ago, Bilal2104 said:

Anybody else screen goes black on the NEO after the tweak?

 

got no gauges, all black screens NO pfd or nd

Restore the backup. I bet you accidentally deleted an essential line or missed a bracket.

2 minutes ago, atlflyer said:

Its in the in game menu at the top....the little white drop down where you can change the weather , etc on the fly...just select the spokewheel and disable as many icons in that menu as you want. The VFR map is one of them. I tested it out and sitting at KLAX I was at 38 FPS. disabled...43 FPS. Enabled again...38 FPS. Disabled again..43 FPS. 

Yep done it a straight +5 FPS fantastic boost from 44 to 49 BOOM!

Backed up original files did a straight copy of the mode into 

D:\MSFS 2020\Official\OneStore\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared

15 FPS boost BUT the G1000 in the 172 where blacked out and not working, any ideas?

Restored back ups and all is fine.

Edited August 28, 20205 yr by Nyxx

28 minutes ago, Nyxx said:

Backed up original files did a straight copy of the mode into 

D:\MSFS 2020\Official\OneStore\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared

15 FPS boost BUT the G1000 in the 172 where blacked out and not working, any ideas?

Restored back ups and all is fine.

same for me even though i did it correct , all gauges are gone

2 hours ago, Nyxx said:

Yep done it a straight +5 FPS fantastic boost from 44 to 49 BOOM!

Good to go! Sometimes its the small things that make a difference! 5 FPS is alot when youre in the low 40s! Thats over a 10% increase! 

6 hours ago, atlflyer said:

personally, I would rather have smoother instruments. In low FPS situations, with the default config, the instruments still move in very fluid fashion. If you want about 5 FPS, disable the VFR map. That really does eat up about 5 FPS even if its not open. Get rid of that. 

That's a great tip, realy saves about 5 FPS

Thanks.

10 hours ago, Andreas Stangenes said:

Thanks for the tweak! I just implemented it in my sim, and on my 100mhz screen I set it to 4 and got great results. The screens aren't lagging too much, and the overall fps is better. 

Hi there. What did you set to 4? Mind to clarify please? I am trying to figure how it works. I added the section to the file this.frameCount % 3, but I see in the zip file offered here there are two options where it show %3 and %2. Which one is the good one, or it depends? 

Also, do I have to change anything in the sim settings? Thanks 

5 hours ago, odourboy said:

Do I need a customized layout.json or manifest.json to have this work?

There are two root files absolutely necessary for all customized 'stuff.' 

layout.json = this file provides the path to the custom BaseInstrument.js file

{
    "content": [
        {
            "path": "html_ui/Pages/VCockpit/Instruments/Shared/BaseInstrument.js",
            "size": 15657,
            "date": "132402817714110148"
        }
    ]
}

manifest.json = describes the dependencies and other information required

{
  "dependencies": [
    {
      "name": "asobo-vcockpits-core",
      "package_version": "0.1.12"
    }
  ],
  "content_type": "CORE",
  "title": "",
  "manufacturer": "",
  "creator": "community fix",
  "package_version": "0.1.39",
  "minimum_game_version": "1.7.12",
  "release_notes": {
    "neutral": {
      "LastUpdate": "",
      "OlderHistory": ""
    }
  },
  "total_package_size": "0000000000000015657"
}

This is the complete folder tree for this custom .js file:

57 minutes ago, skysurfer said:

Hi there. What did you set to 4? Mind to clarify please? I am trying to figure how it works. I added the section to the file this.frameCount % 3, but I see in the zip file offered here there are two options where it show %3 and %2. Which one is the good one, or it depends? 

Also, do I have to change anything in the sim settings? Thanks 

Its the first number value that I changed to 4. However, it seems this value is a bit sensitive to the various airplanes, and I'm already seeing that 4 isn't viable on many airplanes because it will get too stuttery. Im experimenting now with 3 and 2. 

You dont have to change anything in the sim.

Edited August 28, 20205 yr by Andreas Stangenes

Thanks. I have tried all values (2, 3 and 4). I see no fps boost at all. I was in MSFS forum it might be because of my i9900k CPU. Usually people with less powerful CPU see the effect. 

do you have an fps lock on? ie rivatuner or ncp?

I use RivaTuner

well if your sim is running at the specified fps then of course doing this wont help at all. It cant go beyond the fps you specify 🙂