i tried everything that the video told me to do, and IT DIDN'T WORK!! i don't know what the problem is.....it still says my fps goes to 60 but i tried everything.
i tried everything that the video told me to do, and IT DIDN'T WORK!! i don't know what the problem is.....it still says my fps goes to 60 but i tried everything.
1. This is from 2015. Still works though.
2. You don't want to go higher than 60fps. Especially no-where near 200 fps. first off you cant really see your game go any faster than 60fps, any higher is a waste of view distance or graphics. Second, anywhere above 60 will cause screentear, which is worse than fps loss. (Unless you spend over 300$ just to buy a monitor)
Rollback Post to RevisionRollBack
Hello! I am jacklego5, i have played since the alpha days and i am a Veteran at minecraft ( I'm pretty good )
If i am helpful, why not give me a thanks? THANKS! <--- Get it?
2. You don't want to go higher than 60fps. Especially no-where near 200 fps. first off you cant really see your game go any faster than 60fps, any higher is a waste of view distance or graphics. Second, anywhere above 60 will cause screentear, which is worse than fps loss. (Unless you spend over 300$ just to buy a monitor)
There are cases where you want the framerate higher than 60FPS, especially if your monitor is overclocked or you have a TV/monitor with a refresh rate higher than 60hz. Also, getting over 60 FPS doesn't always mean you will get screen tearing, although it's possible and it's very easy to fix (vsync).
If I have 250 fps, but what to do if game freezes with sounds:on and not freezes with sounds:off? I want to play with sounds and I don't know how to update lwjgl.
Thats a nice bit of info, but i dont think having 200+ frames would be needed. Basically if you have to many frames the gpu might send out two frames during one cycle which will oft create the problem know as screen tearing. Consider reading the wiki page about screen tearing. Dont know if you people consider Wikipedia reliable, but it says the same stuff just about anywhere else. the also got those references at the bottom...
There are two buffers in OpenGL. The active one and the one being written to. When the scene is being drawn it's writing to the second buffer. when it's done being drawn the buffers are swapped. No two screen updates are available at any point in time for the monitor to physically select. With this render pipeline screen tearing simply does not happen unless the person coding the renderer makes a mistake and writes to the primary buffer. The problem with screen tears appears when the buffer is being written to at the same time that the monitor is copying the buffer. Since in the OpenGL pipeline the primary buffer is never written to, this doesn't occur. I get between 190 and 220 fps and have never had screen tearing on any OpenGL game. I've seen it on DirectX games, because they don't have a duel buffer.
I don't need to read the wiki page on screen tearing, I'm very aware of what it is. I'm a programmer and I deal with 3D on a regular basis.
VSync automatically requires that double buffering doesn't swap while the refresh cycle is being ran, however OpenGL does this automatically (And minecraft does take advantage of this function).
Also, frame stitching is not very apparent in most cases, only inter times of extreme movement, where every frame has a high amount of difference from the last frame. at 60 fps, the frame stitching would have to occur around 8% or the time or more for your eye to even register having seen it.
I'm not just spewing out anything I can think of. There has been research going on for years on this topic. People used to say that the human eye can't see more than 60 fps. This was proven false many years ago, and led to a series of very large investigation of framerates higher than 60.
Screen tearing occurs when there is a discrepancy between the refresh rate and the frame rate, so basically, always. That's what VSync is for. It limits your fps to your refresh rate, which for most people, is 60. However, due to the way frame limiting works, you'll generally end up with something more like 50fps, which results in a poor gameplay experience. That's why disabling VSync and setting your own frame limiter is often a better option. You can set it to 60fps, but that'll basically be the same as VSync. Because of the way graphics cards work, setting your frame limiter to a multiple of 60 is the best option. Then, if you're hitting 120fps the entire time, your computer doesn't have to work to mash frames together to make a fluid experience.
For an example, If you've got 7 friends, but 13 presents to give out to your friends, how are you supposed to do it? You can give each friend 1 present, but now you have 6 extra. You've got to use all of them. You can give out the last 6, but that means one friend gets only one present, and is sad... You can take the presents and cut them up so each friend gets 1.857 presents, but honestly I'd be disappointed to receive only 0.857 of my new present, or even worse, to receive small portions of multiple presents. There's just no way to do it. And that's what your computer has to figure out every time there is a difference between frame rate and refresh rate.
That's why multiples of the refresh rate, such as 120fps, or 240fps are best because they always divide nice and evenly, resulting in minimal screen tearing if at all.
Also, if you set your limiter to 60fps, that means the game only updates 60 times per second. So say you move your mouse, the player won't actually move until it calculates the next frame, resulting in some extra latency. It's minimal, but everything feels slightly slow, kind of like syrup. With a higher frame rate, the game will be able to update faster and result in a smoother experience.
On top of all that, limiting your frame rate will reduce the strain on your computer, resulting in a marginally, negligible increase in lifetime as well as lower power consumption, so your electricity bills will be lower. Every penny counts.
omg from 1fps - 60 fps, is 600% Fps increase in minecraft 1.7.10 with 140 mods
lol
Fog: fast makes render faster
(¯`·.¸¸.·´¯`·.¸¸.-> <-.¸¸.·´¯`·.¸¸.·´¯)
i tried everything that the video told me to do, and IT DIDN'T WORK!! i don't know what the problem is.....it still says my fps goes to 60 but i tried everything.
1. This is from 2015. Still works though.
2. You don't want to go higher than 60fps. Especially no-where near 200 fps. first off you cant really see your game go any faster than 60fps, any higher is a waste of view distance or graphics. Second, anywhere above 60 will cause screentear, which is worse than fps loss. (Unless you spend over 300$ just to buy a monitor)
Hello! I am jacklego5, i have played since the alpha days and i am a Veteran at minecraft ( I'm pretty good )
If i am helpful, why not give me a thanks? THANKS! <--- Get it?
There are cases where you want the framerate higher than 60FPS, especially if your monitor is overclocked or you have a TV/monitor with a refresh rate higher than 60hz. Also, getting over 60 FPS doesn't always mean you will get screen tearing, although it's possible and it's very easy to fix (vsync).
Hey great tutorial, can you give me link for your theme? Is it for Win7?
it's not OS related.
If I have 250 fps, but what to do if game freezes with sounds:on and not freezes with sounds:off? I want to play with sounds and I don't know how to update lwjgl.
the update lwjgl thing is not possible anymore since 1.6 afaik (and a lwjgl bug really shouldnt express via sounds).
this sounds like a corrupt sound library or resource. reinstall minecraft or create a new topic with the crashlog.
What windows theme is that?
That is true. Before this video, i had 19-25. Now i got 50-67 tank yu
Screen tearing occurs when there is a discrepancy between the refresh rate and the frame rate, so basically, always. That's what VSync is for. It limits your fps to your refresh rate, which for most people, is 60. However, due to the way frame limiting works, you'll generally end up with something more like 50fps, which results in a poor gameplay experience. That's why disabling VSync and setting your own frame limiter is often a better option. You can set it to 60fps, but that'll basically be the same as VSync. Because of the way graphics cards work, setting your frame limiter to a multiple of 60 is the best option. Then, if you're hitting 120fps the entire time, your computer doesn't have to work to mash frames together to make a fluid experience.
For an example, If you've got 7 friends, but 13 presents to give out to your friends, how are you supposed to do it? You can give each friend 1 present, but now you have 6 extra. You've got to use all of them. You can give out the last 6, but that means one friend gets only one present, and is sad... You can take the presents and cut them up so each friend gets 1.857 presents, but honestly I'd be disappointed to receive only 0.857 of my new present, or even worse, to receive small portions of multiple presents. There's just no way to do it. And that's what your computer has to figure out every time there is a difference between frame rate and refresh rate.
That's why multiples of the refresh rate, such as 120fps, or 240fps are best because they always divide nice and evenly, resulting in minimal screen tearing if at all.
Also, if you set your limiter to 60fps, that means the game only updates 60 times per second. So say you move your mouse, the player won't actually move until it calculates the next frame, resulting in some extra latency. It's minimal, but everything feels slightly slow, kind of like syrup. With a higher frame rate, the game will be able to update faster and result in a smoother experience.
On top of all that, limiting your frame rate will reduce the strain on your computer, resulting in a marginally, negligible increase in lifetime as well as lower power consumption, so your electricity bills will be lower. Every penny counts.
How do I make this work for a twitch install where I'm playing the mod pack "Project Ozone Lite"?
Thanks! o/
This worked perfectly for me. Thank you so much