Well, the article is good, but your statement is direct contradict to the article. Humans can see vay above 30 FPS easily. They way human eye perceives different frefresh rates changes varies. But everyone can notice the difference between 30 FPS and 60 FPS quite easily. Heres some more reading for you on this matter.
"I can see and feel the difference between 290 and 500 frames. Its smoother now!"
whoa, mind tricks in play... The only difference between 290 and 500 frames is like max ~1-2ms in input lag? Otherwise you get the same 100 different frames, with another 190-400 of their copies in between those which differ. And the screen tearing may happen like 1/10 of screen "sooner" (higher on the screen). Or am I missing something...
there is no difference between 290 and 500 frames if you dont have monitor from NASA worth 5864537248€ 144Hz(means 144FPS) is the maximum achieved commercialy.
No, not with LFS, because only 100 screens per second are different (physics+world updates are working at 100Hz in LFS). The rest of 400 screens (to do 500 FPS) will be identical to one of those 100 frames.
So above 100 FPS you are just maybe getting lower input latency. And the improvement is under 10ms at most, more likely around 2-5ms. Which is probably easily adjusted by brain anyway, by forecasting, so it shouldn't matter.
What matters a lot is the variation.. if you had 80-150FPS before, with occasional drops to 40-60 for single frame, then new version may feel better, if it now works in stable 100+ with for example single drop to "80".
Theoretically 100Hz video mode would lead to most smooth LFS experience, practically it may still stutter a bit due to vsync vs physics timer not going in absolute sync together. Or 144Hz mode + vsync only, so some of those 100 (different) frames get postponed only by 7ms at most... should be hardly noticeable (unless you have perfect 100Hz running next to it for direct comparison).
Or Oculus Rift, where I believe (not sure about it) the position tracking is working every frame, so you have only 100Hz physics, but the camera(head) movement is tracked at current fps. The the lcd in DK2 has only 70 or 75Hz, so I'm not sure if it's enforcing vsync, or tearing (I don't own DK2, so I have no exact idea, how it works).
TL;DR: The new physics give a great improvement to framerate.
The joke is the fact that movies/ PS#, XBox only play 30 FPS (Yes, movies/TV are really different but I don't care in 'THIS' conversation)
Here is Wikipedia on the subject: "The human eye and its brain interface, the human visual system, can process 10 to 12 separate images per second, perceiving them individually.[1] The threshold of human visual perception varies depending on what is being measured. When looking at a lighted display, people begin to notice a brief interruption of darkness if it is about 16 milliseconds or longer.[2] Observers can recall one specific image in an unbroken series of different images, each of which lasts as little as 13 milliseconds.[3] When given very short single-millisecond visual stimulus people report a duration of between 100 ms and 400 ms due to persistence of vision in the visual cortex. This may cause images perceived in this duration to appear as one stimulus, such as a 10 ms green flash of light immediately followed by a 10 ms red flash of light perceived as a single yellow flash of light.[4] Persistence of vision may also create an illusion of continuity, allowing a sequence of still images to give the impression of motion." https://en.wikipedia.org/wiki/Frame_rate
My crappy laptop got broken and now we get this...
Excellent, now I need an update where I get a new gaming rig for LFS ( and other random stuff )
hmmmmmm...
I remember when my fps was 1,7 - 19... In some cases it was 55-60, depending how high you were driving ( with my layouts, the Z-factor amount was pretty much, not much needed to render track itself )
No idea what this is, what happened or anything. As this is the laptop for streaming. Looks like it simply crashed after hours of sitting in the multiplayer join screen.
I don't know if the bug is really in the ogg player code itself, or if LFS caused a crash by supplying faulty data to the ogg functions. Though strangely in all these years I have not heard of this happening...
But either way, it is probably because LFS switched on the entry screen music in the recent patch. You'd better switch that off then this crash should be impossible.
I learned something three days ago in nightclub...
Never be sure, just act you don't know, even if you knew it!
EDIT: This is already off topic and spam, let's find it later elsewhere okay? I can give you some good tips about how to drive a car off with eyes closed off by meaningless bravery of hard-hitting weak brick wall made by random workmen with no payoff.
The only difference between 290 and 500 frames is like max ~1-2ms in input lag? Otherwise you get the same 100 different frames, with another 190-400 of their copies in between those which differ. And the screen tearing may happen like 1/10 of screen "sooner" (higher on the screen). Or am I missing something...
)