@kaosfere Yep, just tested it (144 htz monitor). I used a value of 5 and in the bonanza (G1000) i can clearly see that the gauge refreshing at below 10fps...its a bit of a slide show. So the number or setting you choose is adaptive based off your actual fps at that moment. I'd then base this setting off of my lowest fps that I'd normally see to insure that my gauges do not suffer...the gauge refresh rate IMO is the most important one in the game.

So then... I may try a value of 1.5...or I may end up leaving it alone and not use this tweak at all, tbh.

Edited August 27, 20205 yr by hangar

8 minutes ago, hangar said:

@kaosfere Yep, just tested it (144 htz monitor). I used a value of 5 and in the bonanza (G1000) i can clearly see that the gauge refreshing at below 10fps...its a bit of a slide show. So the number or setting you choose is adaptive based off your actual fps at that moment. I'd then base this setting off of my lowest fps that I'd normally see to insure that my gauges do not suffer...the gauge refresh rate IMO is the most important one in the game.

So then... I may try a value of 1.5...or I may end up leaving it alone and not use this tweak at all, tbh.

I just tested now, I think the value of 2 is good comprise. Value of 3 gives a very good fps boost but the displays are choppier 

6 minutes ago, hangar said:

@kaosfere Yep, just tested it (144 htz monitor). I used a value of 5 and in the bonanza (G1000) i can clearly see that the gauge refreshing at below 10fps...its a bit of a slide show. So the number or setting you choose is adaptive based off your actual fps at that moment. I'd then base this setting off of my lowest fps that I'd normally see to insure that my gauges do not suffer...the gauge refresh rate IMO is the most important one in the game.

So then... I may try a value of 1.5...or I may end up leaving it alone and not use this tweak at all, tbh.

So if it's based on your FPS count (50 in your case) how come people with 144hz are gaining 20 FPS? I am not saying your wrong as I have not tried it but because I run 120Hz but locked frames at 30, I was hoping for a nice FPS jump because of my 120Hz, your saying its not and works of your FPS count in game. All them reports on the original post are well!!!! confusing!

12 minutes ago, hangar said:

I may try a value of 1.5.

 

Edit:  disregard this response, I had a brain fart. 🙂

🙂

Edited August 27, 20205 yr by kaosfere

In order not to mess around with the core package, somebody in a discord server extracted the required files to modify into its separate zip file, I took this out and modified it like this:

CanUpdate() {
        var quality = this.getQuality();
        if ((this.frameCount % 2) != 0) {
            return false;
        }
        return true;
    }

 

The zip is here: https://www.dropbox.com/s/acen5jp39nt4w3d/FPS-Fix.rar?dl=0, and then just extract it to the community folder. 

 

Note: You will need to modify the coefficient depending on your system, is mostly try and error process.

4 minutes ago, Nyxx said:

So if it's based on your FPS count (50 in your case) how come people with 144hz are gaining 20 FPS? I am not saying your wrong as I have not tried it but because I run 120Hz but locked frames at 30, I was hoping for a nice FPS jump because of my 120Hz, your saying its not and works of your FPS count in game. All them reports on the original post are well!!!! confusing!

I can't speak for the folks on the original post, but in general by making this change you're going to be reducing the amount of work your GPU is doing.   If you're using modulo 3, you'll basically be cutting the amount of work it takes to render your glass by 2/3.  I don't know how much of the render load is caused by the gauges, but given that people reported much better performance in views without the glass it seems like it may be a bit.   So it would stand to reason with the GPU spending less time on the glass it can spend more time on other stuff and your overall framerate goes up.

But I'd be cautious about any claims of FPS gain that aren't backed up by actual measurements over an extended period of time, in the same situation, before and after   It's really easy when making a change like this to see the effect you *want* to see, not the one actually there.  🙂

4 minutes ago, kaosfere said:

I can't speak for the folks on the original post, but in general by making this change you're going to be reducing the amount of work your GPU is doing.   If you're using modulo 3, you'll basically be cutting the amount of work it takes to render your glass by 2/3.  I don't know how much of the render load is caused by the gauges, but given that people reported much better performance in views without the glass it seems like it may be a bit.   So it would stand to reason with the GPU spending less time on the glass it can spend more time on other stuff and your overall framerate goes up.

But I'd be cautious about any claims of FPS gain that aren't backed up by actual measurements over an extended period of time, in the same situation, before and after   It's really easy when making a change like this to see the effect you *want* to see, not the one actually there.  🙂

I am locked at 30 FPS so it might be just a waste of time to try it. If it ran of my 120hz then it could've been huge.

I am attempting to do this on line 235 but it either CTD my sim or I get no displays on the NEO if I change the value of CanUpdate() {
        var quality = this.getQuality();
        if ((this.frameCount % 2) != 0) {
            return false;

 

Where I change it from value 8 to a 2. Am I missing something?

 

 

  CanUpdate() {
        var quality = this.getQuality();
        if (quality == Quality.medium) {
            if ((this.frameCount % 8) != 0) {
                return false;
            }
        }

 

Can you paste the full contents of your CanUpdate function?

12 minutes ago, Nyxx said:

So if it's based on your FPS count (50 in your case) how come people with 144hz are gaining 20 FPS? I am not saying your wrong as I have not tried it but because I run 120Hz but locked frames at 30, I was hoping for a nice FPS jump because of my 120Hz, your saying its not and works of your FPS count in game. All them reports on the original post are well!!!! confusing!

The FPS is the # of frames your video card outputs, whereas the hz is the way your monitor displays them. Technically, hz has nothing do with FPS by itself, but having a certain type of monitor may allow you to set other settings more comfortably (or turn on/off other settings) like Vsynch, or capping the FPS. So all different HZ really does is just allow people to live with the effects of changing other settings without those changes ruining their motion. So it only has an effect in the sense it allows people to experiment in ways with other settings that they may not have been able to prior.

Since Flight Sims are simple animations and movement, it is easier to live with the side effects of different pulldown modes and interpolation, as compared to if you were doing it with a movie. For instance, if you watch a movie that is only 24p (24 fps), and then you output that to 60hz, some people can notice some judder or some jerkiness at times, especially during live action or people talking. The reason this isn't much of a big deal in a Flight Sim is because the frames are not as random, hence the difference when FLYING between the first frame and the third are usually somewhat sequential and predictable, unlike the difference in animation when someone is moving their lips in random directions and talking. That said, panning and certain types of issues may still look funny in some cases if the FPS dips down unevenly, as it sometimes does in this game.

 

17 minutes ago, kaosfere said:

Can you paste the full contents of your CanUpdate function?

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;
    }

 

50 minutes ago, Nyxx said:

So if it's based on your FPS count (50 in your case) how come people with 144hz are gaining 20 FPS? I am not saying your wrong as I have not tried it but because I run 120Hz but locked frames at 30, I was hoping for a nice FPS jump because of my 120Hz, your saying its not and works of your FPS count in game. All them reports on the original post are well!!!! confusing!

I understand your confusion, look at it this way... a very simple way to think of this is that the sim essentially has 2 different fps rates (technically untrue, but this will make it clear nonetheless)...the one for the main sim window (this is the one everyone knows and understands) and another for the gauges in your planes cockpit. The frames per second in your main window control how smooth everything goes by outside your window and the frames per second for your gauges control how smoothly the gauges will move (airspeed,vertical speed,altitude,attitude indicator, etc.).

What happens is that your gauges are assigned a frame rate that is equal to your current fps (lets make believe you are getting 40 fps out your window) divided by the value you used for this tweak. In this case we used a vlaue of 5, so then its 40fps divided by 5 which equals 8. That number 8 is the fps that gets assigned to your gauges in cockpit. So the fps gain you see folks talking about, is the fps rate they see out the window, but this gain also means that their gauge fps has been reduced by quite a bit making the gauges no longer liquid smooth anymore. Which way you prefer it will depend upon how much you rely upon your gauges during approach/landing.

I personally prefer to have liquid smooth gauges during approaches and landings so I dont want anything less than 25-30 fps on my gauges. This is why I probably will not use this tweak...because I get the feeling if you make the number too small (so you gauges wont suffer) then you wont see any real benefit for the fps out the window at that point.

Edited August 27, 20205 yr by hangar

27 minutes ago, kaosfere said:

I can't speak for the folks on the original post, but in general by making this change you're going to be reducing the amount of work your GPU is doing.   If you're using modulo 3, you'll basically be cutting the amount of work it takes to render your glass by 2/3.🙂

Thank you Rob for at least using the correct name for the % operator! 😌

Although modulo is a "form of division" the result of the operation is not what most folks would expect, since it is simply the remainder from the division...

if ((this.frameCount % 8) != 0)

...thus the only time this conditional operation will ever be True is when this.frameCount is evenly divisible by 8.

51 minutes ago, omarsmak30 said:

In order not to mess around with the core package, somebody in a discord server extracted the required files to modify into its separate zip file, I took this out and modified it like this:

CanUpdate() {
        var quality = this.getQuality();
        if ((this.frameCount % 2) != 0) {
            return false;
        }
        return true;
    }

 

The zip is here: https://www.dropbox.com/s/acen5jp39nt4w3d/FPS-Fix.rar?dl=0, and then just extract it to the community folder. 

 

Note: You will need to modify the coefficient depending on your system, is mostly try and error process.

Not a good idea to ignore the quality setting in my opinion. Quality depends on your view setting - external, showcase, etc. 

By setting the refresh rate as the same for all views, you’re going to hurt performance when outside the aircraft (which seems to have refresh rates set at 1/8 and 1/32 the default rate).

Edited August 27, 20205 yr by FlyingInACessna

18 minutes ago, n4gix said:

Thank you Rob for at least using the correct name for the % operator! 

YW 😄

I posted an explanation of modulo in the comment I deleted, because I'd mistakenly stated that using a modulo of 1.5 wouldn't make sense, when in reality it's perfectly fine.    But I took the explanation with it, it seems!