Originally posted by Dimension
OK, I was going a little overboard there. Most of what you're saying is correct. I certainly don't agree, though, with your explanation for lag. The net just isn't that slow, and prediction is mostly used to smooth out motion in realtime games. That is, say I'm playing Quake with a guy on dialup who has a ping of 200, so his character is only updating five times a second. My machine is running at 60 FPS, so there must be prediction to keep things from looking choppy. Prediction does not, however, compensate effectively for dropped packets or a legitimately bad connection.
OK, I was going a little overboard there. Most of what you're saying is correct. I certainly don't agree, though, with your explanation for lag. The net just isn't that slow, and prediction is mostly used to smooth out motion in realtime games. That is, say I'm playing Quake with a guy on dialup who has a ping of 200, so his character is only updating five times a second. My machine is running at 60 FPS, so there must be prediction to keep things from looking choppy. Prediction does not, however, compensate effectively for dropped packets or a legitimately bad connection.
I have never seen a drive just randomly get corrupted (especially an NTFS drive) where I couldn't link it to a legitimate hardware problem. Last week, PTW locked my machine during a delayed write and corrupted my hard drive. It destroyed my SYSTEM32 directory (making the machine unbootable) and my Documents and Settings folder (destroying my financial records and a large project I was working on, both of which had changed a lot since I backed them up two weeks ago). This really isn't acceptable behavior for retail software.
Comment