How can that be? You are still just watching a screen right?bobgreen5s wrote:
Thats only true when your passively watching moving images (like a movie) not when you are actively playing a game.ilyandor wrote:
the human brain can not notice the difference between 24 fps and above.
i get on avg. 10-15FPS its fun.
I have everything set to low, or off. and i have a draw distance of 45%
it sucks to have my PC
just check out my XFIRE page and my specs are on there.
I have everything set to low, or off. and i have a draw distance of 45%
it sucks to have my PC
just check out my XFIRE page and my specs are on there.
i have 2 gig or ram and a 7800gt i run everything at low/med @ 8xaa & 16x anitstopic filtering constantly 100+ frames per second 70 during warlord grenade spamming and gas spamming sessions........ with dynamic light on high so you can see everything really well
i used to run everything on high but i dont really notice a difference with the aa and af maxed out between high and low...... well not enough to run bf2 at 40 fps slower
i used to run everything on high but i dont really notice a difference with the aa and af maxed out between high and low...... well not enough to run bf2 at 40 fps slower
i have the same card as you and 2 gb ram and i dont get anywhere anytime lower than 40 fps. This is with EVERYTHING on high and playing on 1600x1200 resolution.
false, this a rumor from the fact that cinema runs at 24 fps... the reason it looks like completely fluid, is that the image is an average of itself and the last one... for example if you stop your movie while a kung fu fight, you will see the arm of the fighter larger than usual.. I dont know how to say it as my english is not perfect but the arm will be ..."stretched?".ilyandor wrote:
the human brain can not notice the difference between 24 fps and above.
Ok thanks, considering i have an average high end rig and high settings:PSnake wrote:
FPS also depends on what the engine is rendering. i.e. areas with LOTS of detail will mean the engine is "drawing" a lot more detail on your screen = lower FPS.
Areas with little detail, equals quicker draw time = higher FPS.
I used to do a bit of mapping for CS and CSS, and the rule of thumb was to limit what the engine was drawing with "blockers", i.e. buildings to block line of sight.
Example, you are at a corner of a building. The engine will be drawing what can be seen both in front and behind of your current position. It will also most likely be drawing around the corner a certain distance. Its quite complicated, but can be changed/restricted with good mapping.
If you are interested, just google "VIS Blockers" and you will find a wealth of info.
As I say, that was for CSS. I assume its the same with any game since its how they work.
Therefore...karkand, nade spamming/armour spawnraping/claywhores and god knows how many bullets = lots for the engine to draw = low FPS.
Same area with half the people = higher FPS.
Thats why they have the fog in the map - otherwise the engine would be drawing a lot more of the map beyond the fog which would mean higher FPS. Not good.
With karkand being the (fucked up) way it is, low FPS is inevitable - especially on high settings, regardless of your own high system specs.
Tech section? Make sure you don't have background tasks running, run scans, defrag the hard drive and clear the cache folder.
Ended all background tasks but didnt defrag, i only used 30gb out of 160.ssonrats wrote:
Tech section? Make sure you don't have background tasks running, run scans, defrag the hard drive and clear the cache folder.
They tested on this, You need 85 fps or above to play optimally. If fps < 85 Your gameplay suffers gradually. Your brain can see the difference, it's smarter than You hehehe. I play with all on high and hide in the dark. Pls turn on shadow and lighting so You can't see me pls. This really sucks.
Wow i got like 19fps in a really crowded area, shooting everywhere, tanks also everywhere.
How dare you compare the jpeg-maped CS to the marvolus BF2!!Snake wrote:
FPS also depends on what the engine is rendering. i.e. areas with LOTS of detail will mean the engine is "drawing" a lot more detail on your screen = lower FPS.
Areas with little detail, equals quicker draw time = higher FPS.
I used to do a bit of mapping for CS and CSS, and the rule of thumb was to limit what the engine was drawing with "blockers", i.e. buildings to block line of sight.
Example, you are at a corner of a building. The engine will be drawing what can be seen both in front and behind of your current position. It will also most likely be drawing around the corner a certain distance. Its quite complicated, but can be changed/restricted with good mapping.
If you are interested, just google "VIS Blockers" and you will find a wealth of info.
As I say, that was for CSS. I assume its the same with any game since its how they work.
Therefore...karkand, nade spamming/armour spawnraping/claywhores and god knows how many bullets = lots for the engine to draw = low FPS.
Same area with half the people = higher FPS.
Thats why they have the fog in the map - otherwise the engine would be drawing a lot more of the map beyond the fog which would mean higher FPS. Not good.
With karkand being the (fucked up) way it is, low FPS is inevitable - especially on high settings, regardless of your own high system specs.
If you want a fckin VIS blockers while flying a jet, just put ur fcken palm in front of ur monitor and give yourself the finger while at it!
Ya go play Worms, u fuckein expert!