Do I have OCD or is there something wrong?

Ha! The sign of a true gamer; he would rather have a mental illness himself than have anything wrong with his machine. Respect to you, I feel your pain!

AC

Sorry, no idea what's going on:|

I think it actually might be the coding of the game. Like, I noticed it in Doom 3 and Quake 4 (both ID games). I've noticed it Trine and I haven't noticed it in other games like Crysis, Farcry 2, Prince of Persia (2008), Etc.

Trust me, That does nothing . All that does is get rid of the tearing which is normal for a crappy monitor or more monitors come to think of it.

Okay but, It still happens with or without VSync xD. I'm not crazy it really does happen.

I've noticed the effect you are describing. The problem stems from a mismatch with the framerate and the monitor. At 60fps on a monitor running at 60Hz, things are as smooth as silk. At that point, your monitor's response time won't matter much because its running at a 1:1 ratio.

Now, your games are running at 200fps+, and you're still on a monitor that's running at 60Hz with a refresh rate of 16ms. Your ratio is way out, and your monitor can't keep up and drops frames during the render process. If you're running on a D-SUB connector this further complicates the problem and slows things down. The refresh rate helps, but not by much.

I had a friend who suffered from this and I reproduced the problem with Quake 2 at 1000fps and NFSU2 at 200fps with an older monitor. With a newer one on a DVI connection with 5ms response time, the problem was much less noticeable. Changing the graphics card to a less powerful one also helped this.

So, this is what happens when you play older games on much more powerful systems - it runs way too fast and ends up tripping over itself every now and then.

Well, I'll obviously need more info than just the screen res and settings, but I'll assume you're running a decently-specced PC.

With newer games, the problem becomes more and more tricky to solve. These days its a problem with the game code than anything else - while playing Assassin's Creed on the PS3 I get the effect you describe that only occurs when the camera angle is moved. Perhaps at this point, especially with newer games, the code isn't optimized properly for any given system, and some will have the lagging and tearing problems while others wont.

Its annoying, I know. I guess with the games these days running at these crazy settings with a bajillion pixels on the screen, it creates a ton of information that must be used to render objects on the screen, and sometimes its way too much information and things start to slow down. Are you running a graphics card with more than 512MB memory? It could be that the camera angle changes introduce more information that chews the GPU's memory and forces it to work with the slower system RAM or even the pagefile, depending on how the code handles this kind of thing.

Also, on the subject of optimization, your game is guaranteed to run differently with a different processor or graphics card. Most of the optimization happens on rigs with Nvidia cards and Intel chips these days, hence the reason why the first Crysis always runs better on Nvidia/Intel hardware. The opposite is true of Far Cry 2, F.E.A.R 1+2, and GTA4 which runs so much quicker with an ATi card or AMD processor. Various things like how water effects and explosions and even camera changes are handled are affected by what hardware you are running, so you may find that running the game on a nearly identical system with a different graphics card (or whatever) won't have the same problem.

ANNO 1404 isnt an online game (sadly),but if it was I think my rogers highspeed could handle it easily. I do have a 5ms response time monitor (LG W2343) and also as stated in a previous post I do have a fairly new PC.

my specs are:
Intel E8400 @3.8GHz
ASUS P5Q pro mobo
Corsair XMS2 4Gb @1066mhz
Noctua nh-u12p
XFX Radeon HD 4890 1GB @ (960/1080)
PC Power &Cooling Silencer 610W
LG W2343T-PF 1920X1080 1080P Black LCD 5ms

So I'm thinking Snow_Patrol nailed it with the different hardware/software optimization. I guess I just have to live with it, but its really not that bad, and the game is very playable seeing that its only a minor thing. I'm gonna try and put all the settings and resolution on low and see if the problem goes away.

The answer to "why" you're getting this issue is still plague-ing me too.
If known, please tell....

BUT the workaround-solution for Doom and similar games is this:

try to google for com_preciseTic and/or com_fixedTic

in summary:
go into your console using alt+ctrl+` (the tilde or ¬ character on keyboard)

and change one or both of those settings as follows (I found that com_fixedTic worked okay alone)

seta com_fixedTic "1"

seta com_preciseTic "1"

other games like oblivion and stuff have other settings from console or in the files that can limit the game frame-rate-tic frequency that can also fix the problem in those games.

I doubt that's the issue or it would probably be a little bit more of an issue for not just gaming.