@04dcarraher said:
@demi0227_basic said:
There's no real difference between where your game is installed (2nd drive vs os drive).
Lagging could be what you saw, but it's unlikely. The only time you'd "lag" due to the hard drive is when the cpu is pulling data from the hdd too slow to be fed to memory, which is unlikely, though possible on some game's like Arkham. Usually when a game loads a level, you wait because you are pulling data off the hd and feeding it to memory, which is MUCH faster than even an ssd, let alone a hdd. Hdd would only cause stutters in instances where you are loading something and it takes too long to get the data off the hdd. Most games address this by loading things into memory. Like...95% of games. Some games can't do that, such as wow, just cause 2, etc, because there are no load times. I'm not sure if Arkham loads the entire city into memory, but I doubt it.
Basically, if it was stuttering when you go to a new part of the city, then it could have been your drive. If it stuttered in the same place of Arkham, then it's something else, because you wouldn't be pulling data off the hdd in that instance.
I hope I was helpful.
Fact that the TC is not experiencing any more issues after installing the game onto another drive proves that its not the cpu/memory or the game. Something was going on the OS drive while playing and it could not handle all the load.
So your wrong about "There's no real difference between where your game is installed (2nd drive vs os drive)" Your pc performs more than one disk activity at once, and when you have alot of tasks in the background it can affect the performance of what your doing. Installing onto another drive allows the OS drive to do its functions and the game do its thing other another without bogging down the drives.
Yup. A faulty drive could be the cause. There's still negligible difference from installing on os drive or secondary drive. Sorry man. That's how it is. Tasks running in the os aren't constantly loading from hdd...they are running in system memory and were pulled off the hdd when they were loaded. That's just how things are, whether you accept it or not.
First, let's assume his perceived lag/stuttering was a change in fps, shall we. He wasn't online, so his stutter was a rapid change in fps one way or the other, rather than internet latency.
These boards are so fun...no matter what you say, there's always some guy that's sure he's got it licked. If the move from a faulty drive to a not faulty drive fixed his issue, great. It doesn't change the validity or soundness of my argument. CPU loads from HDD/ssd, then caches in memory for use until the program is closed because memory is much faster than hdd/ssd. If you'd like to prove me wrong, please post graphs/sources indicating that changing hdd changes perceived lag in games (read: quick changes in fps=lag). You won't be able to find it. CPU/ram/gpu are the only things that, if nothing is broken, will create anything to due with lag. Benchmarks for fps will be the same whether you are using the newest, fastest ssd, or a 5400 green hdd. Once data is cached for the program to load, hdd doesn't matter.
Also...you can't find any info on games being on a secondary hard drive performing any better than the os drive. Because it doesn't matter. The game is initially loaded into ram. When you change levels on some games, that load screen is there because the cpu is pulling data from hdd and caching it in ram, which is what you'd need to play.
Anyways...who cares. He probably had a faulty drive somehow, someway. Whether windows wasn't defragging, or he had bad sectors, or whatever.
Log in to comment