Global Conflict

Just playing on GC and.....................

Don't do drugs guys, drugs are bad, even for your PC.

[youtube]http://www.youtube.com/watch?v=d0Mq_EELEb4[/youtube]

I get this also at times - on various servers. I thought it is my old graphic card being stressed. I usually get rid of the "effect" when changing servers/rejoining the server.

... if this is a broader phenomena we will move the thread to the help forum, lets see.

reminds me of Half Life 1 madness, when near the end you keep getting teleported into different universes and crap

THE RAINBOW CATS ARE SABOTAGING OUR GAMES NOW?!

I had this several times, with different driver versions.
Not sure what's causing it (my guess is drivers).

K.A.R.T HACKED THE SATELITES! ;p

Its caused by a windows security update if you back that one out and restart you will be fine.

http://forum.symthic.com/battlefield-3- ... n-bf3-fix/

ZientMazza wrote:Its caused by a windows security update if you back that one out and restart you will be fine.

http://forum.symthic.com/battlefield-3- ... n-bf3-fix/

The update in question updates this:

- Direct2D
- DirectWrite
- Direct3D
- Windows Imaging Component (WIC)
- Windows Advanced Rasterization plattform (WARP)
- Windows Animation Manager (WAM)
- XPS-dokument API
- H.264-videodekoder
- XR JPEG-codec

Usually the reason for glitched textures (aka artefacts) is overheated or broken graphicscards or bad drivers, in this case it's possible it's that update from Windows, even though the post in the Symthic forum points to "yellow roads", not the rainbow colors that you get.

Someone said that happens when the GPU gets overheated.
In my situation that's not the case, unless it's overheating at 45-50 degrees C, which it isn't.
I have a GeForce GTX670 graphiccard, which is more than enough to run BF3.

I did NOT get this error on my laptop, which runs on GeForce GTX580m, a card that could
barely keep the game at good FPS.

I suspect this conflict lies either in some kind of graphical compatibility update on BF3's side,
OR on Nvidia's new driver. Anyway, really weird....

When it happens, it seems as if grenades/explosions/smoke intensifies the bug to a point
where you can't see crap. I believe it is a software problem, not a hardware one.

No solution that I know of at the moment.

nice f*ing dead post revive...

Necromancer wrote:nice f*ing dead post revive...

Ahaah. Give him a break. He's new here! I for one hadn't seen this so it was mildly entertaining.

Its the drivers. Going back to 3.14 drivers solves it for most people.