Anyone has problems with ATT and Gothics 3?

Yes!!! It's true This setting resolve my problem :bounce:

You saved my money man :mhp:

I tried also to activate by ATT the Vsync to on an all worked perfectly... :eek2:

 

Well on a second look I did manage an improvement, with Geometry Instancing turned on I can at least see the area immediatley surrounding nameless (avatar).

Weird, heh?

 

Bad new, as I thought, the fact that the game ran without artifacts was not due to the activation of geometry instancing but was due to the fact that i reinstallaed drivers (Sometimes If I reinstalled drivers the game runs well, but If I made some changes in the profile of Gothic3 soon or later the game re-show me artifacts) As a matter of fact I tried to disable the Geometry instancing and game showed me artifacts (for the moment all ok) BUT when I re-enabled IT the game showed artifacts too !!! So like I said before, there's no an option that makes this artifacts but seems like that randomly If you change some options from ATT soon or later the game will cause problems.

And sometimes (!!) this problems could be resolved reinstsalling drivers (but sometimes is required also to reinstall ATT).

Just a big mess

 

I encountered the same oddness,
I have managed to succesully run the game with ATT once but it was immediatley after I reverted back to 6.9 Cats. After modifying basic some D3d options I could no longer run the game without artifacts.

I didn't report this earlier because I figured it was a fluke

 

If you understand what geometry instancing does, you'd understand that it's not at all relative to the problem you guys are discussing.

I've been into 3d cards for over ten years(i'm 37) and all of those screenshots, to me, are showing memory errors. It has to be a voltage issue.

Can any of the guys having this issue bump their memory voltage up a notch and see if the problem continues?

 

Teach me what I have to do and I will do it.

But in this case what is the fault of ATT ?
Just because without ATT installed the game runs perfectly

 

I installed the NGO Driver and it works with Gothic3

 

I'm having the same problem with Call of Juarez.
I think Far Cry(PS 3.0) is also having this problem with ATT. When you start the game everything is fine but the moment you go outside the same problem happens. Without ATT everything is fine no matter what driver version. If you run the game with ATT and PS 2.0b instead of PS 3.0 everything is fine also. Strange. Can somebody who is having these problems with Gothic and Call of Juarez test Far Cry?


Edit: the latest Omega drivers in combination with ATT beta v1.2.6.978 is working great. No problems with Call of Juarez and Far Cry and for the first time overclocking is working wth my X1950 Pro.

Thanx Ray.

 

Artefact when changing 3D Settings with ATT

Hi ..

I use ATI Driver version 7.3 with Catalyst. I use ATT to change my Fancontrol and OC my x1950GT to PRO. Everything works fine until I use ATT for only that. As soon as I change any 3D Settings with ATT I have unplayable artifacts in FarCry and Gothic 3. They only disappears after I deinstalled ATT AND the ATI Driver.
I have no Problem as long as I make my 3D Settings with CCC and NOT with ATT. I would prefer to make changes with only one tool, no question about what tool , so i can deinstall CCC. Maybe there is any solution?

Thanks for help.

EDIT: I use the latest beta from ATT 1.3.6.1031

 

Problem gone

Hi ..

I've installed the newest ATI driver 7.4 and ATT 1.3.6.1033. From know the Problem is gone! I don't know why.

Cu

 

Yeah this one still comes and goes for me too, G3 and Call of Juarez Demo although I never noticed it in Far Cry :shrug:

Bumping the voltage as Unity suggested seems to have improved matters, although I could just be imagining things.

@ Rafnagud
Thanks for the comment about ATT and PS 2.0b, good to know

 

Also check G.I. option. It MUST be enabled. Sometimes when you install only drivers without CCC, G.I. option will be turned off. So you have to turn it on manually.

 

Update: like Ray is saying turning on Geometry Instancing indeed fixed the problem for me a few months ago while we were discussing this problem @Rage3D