Yeah, I had the same issue with Valve games. I had to quit playing Half Life 2 about two hours into it because I was about to vomit. It was just after the long-ish boat sequence -- my theory at the time was the excess of brown was making me ill. I learned years later about the FOV thing, but never went back to finish the game.redknightalex said:Yup, that's motion sickness. Had a lot of issues with Valve games before I could fix the FOV and turn it up from the horrible setting of 45 (normal for a console) to 75 or higher for a PC. Normally I stick with 90 for a game, particularly ones I play long stretches of, like Skyrim. On a console, FOV doesn't matter as much due to the distance between you and the TV.
The reason why one can get motion sickness from video games, particularly ones with low FOVs, is because our brain sees us "doing" something on the screen but our inner ear, which controls balance and other functions, doesn't feel it and hence can't adjust. Same reason why people get sick at 3D movies.
Another title that gave me motion sickness was, strangely, The Unfinished Swan. Probably a low FOV combined with fast controls and changing contrasts did too much to my brain. Can only play that in hour stints.
Well, this was Valve...ten years ago? FOV wasn't a big issue back then, even on PCs (I'm guessing due to the lower resolutions and the rise of widescreen monitors). Even games like Skyrim, which are admittedly made for multiple platforms, have annoying FOVs as defaults (65 I believe). I'm not sure why Valve did that for HL2 (which I also had problems with, and I do remember that exact sequence you're talking about), but I did do some searching of forums for the cause and fixes. It was a pretty big issue at the time and many people were having motion sickness problems.Spectrum_Prez said:Yeah, I had the same issue with Valve games. I had to quit playing Half Life 2 about two hours into it because I was about to vomit. It was just after the long-ish boat sequence -- my theory at the time was the excess of brown was making me ill. I learned years later about the FOV thing, but never went back to finish the game.
It's weird though, I never had the issue with other FPSs released around the same time. Why did Valve decide to set their FOV so narrow my default? Was this ever commented upon? Your point about how consoles don't have this problem because the player is further from the display makes sense, but Valve publishes primarily for the PC so they shouldn't be affected by that line of reasoning.