Increased Temperature With New AMD Drivers?

[dn7309]

I just updated my AMD Driver from 14.4 to the new 14.7 driver. Since then I noticed my 290x has been running hotter than usual. going from 65C to 78C.

anyone else experience the same?

 

[Bateluer]

I just updated my AMD Driver from 14.4 to the new 14.7 driver. Since then I noticed my 290x has been running hotter than usual. going from 65C to 78C.

anyone else experience the same?

I've been running the 14.7s for a while now, and it seems like many games ignore v-sync now. Example, Risen 1 and Witcher 1 both run at 100+ fps despite my having set Catalyst to force V-sync. This seems to cause my 290X to run at maximum clock speeds. So these older games that really shouldn't tax the 290X, have the card hitting 90C because its just running at max clocks.

Was debating rolling back to 14.4 just to see what happens, but I think we'll probably be seeing the WHQL 14.8s or 14.9s very soon.

 

[RaulF]

I am running a 295X2 and have not noticed an increase in temp.

 

[Final8ty]

I've been running the 14.7s for a while now, and it seems like many games ignore v-sync now. Example, Risen 1 and Witcher 1 both run at 100+ fps despite my having set Catalyst to force V-sync. This seems to cause my 290X to run at maximum clock speeds. So these older games that really shouldn't tax the 290X, have the card hitting 90C because its just running at max clocks.

Was debating rolling back to 14.4 just to see what happens, but I think we'll probably be seeing the WHQL 14.8s or 14.9s very soon.

Catalyst V-sync is for OpenGL only.

Do you have more than one display? if so make sure the display you are gaming on is number 1 in CCC.

 

[Bateluer]

Catalyst V-sync is for OpenGL only.

Do you have more than one display? if so make sure the display you are gaming on is number 1 in CCC.

Didn't know what.

And I'm gaming on display 2 . . .

 

[dn7309]

I am running a 295X2 and have not noticed an increase in temp.

What are you max temperature? I got mine stuck in a h55 from corsair (very basic AIO I know) and it avg 76 peaking at 78. It used to be around 62-65.

 

[bystander36]

Catalyst V-sync is for OpenGL only.

Do you have more than one display? if so make sure the display you are gaming on is number 1 in CCC.

Is that new? It didn't used to be OpenGL only. I think you may be thinking about triple buffering, which is OpenGL only.

 

[Final8ty]

Didn't know what.

And I'm gaming on display 2 . . .

That's why Vsync will not work.
In CCC swap the Identity numbers of the displays, once that's done you can drag the displays to put them back in arranged order.

Example:
My Primary monitor is number 3 here and with some games Vsync would not work.

So i swapped the numbers which would also move the display arrangement, so i just dragged the displays back in order

 

[Final8ty]

Is that new? It didn't used to be OpenGL only. I think you may be thinking about triple buffering, which is OpenGL only.

Its been that way since MS changed the rules with Windows Vista.

 

[bystander36]

Its been that way since MS changed the rules with Windows Vista.

Umm...I could force V-sync on with my AMD cards with Windows 7, which is long past Vista. You have to be thinking of triple buffering. V-sync is not an OpenGL only thing. Granted, not all games can be force on or off, but many could be, well past Vista.

 

[blackened23]

Umm...I could force V-sync on with my AMD cards with Windows 7, which is long past Vista. You have to be thinking of triple buffering. V-sync is not an OpenGL only thing. Granted, not all games can be force on or off, but many could be, well past Vista.

From what I remember with 7970s, forced vsync never worked in CCC ever the entire time I had those cards, ever. If the game did not have ingame vsync, or had a 30 fps vsync (dead space) - you were SOL or had to use a framerate limiter. Which sucked because fps limiters usually cause tearing. Good example is Dead space because the ingame vsync is 30 fps, but if you force vsync it's 60 fps. So what most people do on NV cards is force vsync via NV CP for that game or use adaptive vsync - and disable vsync in game. This would give you vsync'ed 60 fps. I could not get 60 fps vsync with the 7970s, but i'm not sure if that changed. I'd hope it's not still a driver issue now, because that would frankly be pathetic if so.

 

[Final8ty]

Umm...I could force V-sync on with my AMD cards with Windows 7, which is long past Vista. You have to be thinking of triple buffering. V-sync is not an OpenGL only thing. Granted, not all games can be force on or off, but many could be, well past Vista.

Not NVIDIA Issues

This section lists issues that are not due to the NVIDIA driver as well as features
that are not meant to be supported by the NVIDIA driver for Windows Vista.
Windows Vista Limitations
These are behaviors that may be different from Windows XP and are related
directly to the Windows Vista operating system.
• Selecting Vertical Sync (vsync) from the NVIDIA Control Panel has no
effect with DirectX applications.
Due to architectural changes in the new Windows Vista Window Display
Driver Model (WDDM), the graphics driver can no longer disable vsync
from its own driver or Control Panel. Selecting this option from the NVIDIA
Control Panel will have no effect with DirectX applications. For applications
that use Direct3D on Windows Vista, use the vertical sync setting within the
application. We are adjusting the help text in the NVIDIA Control Panel to
make this clearer to our customers.

http://us.download.nvidia.com/Windows/100.65/100.65_ForceWare_Release_Notes.pdf

Which means you can't force enable or force disable VSync in Apps/games through the CP[before NV hacked it].

*sigh* @ people in this thread.

Vsync was changed rather a lot when Vista & Win7 came out. Before then the OS desktop was not vsync'd so it was a lot easier to alter the vsync state for apps since you didn't have the desktop manager in the background screwing things up. Microsoft also said that they didn't want vsync to alter Aero so they made it more difficult too. Both RadeonPro and ATI Tray tools and other things like that use hacks which go against what is the the WDDM spec. Nvidia also do this so their drivers shouldn't be WHQL certified IMO.

Forcing Vsync on or off globally can ah heck things up for quite a few apps which is why AMD did not go the same route as Nvidia and ignore the WDDM spec & Microsoft guidelines. Now that there will be app specific profiles there should be no reason to not allow it to be forced on or off for a particular app so I have asked AMD to take another look at it which hopefully they will do.

http://www.rage3d.com/board/showthread.php?t=33984337&highlight=Vsync

 

[blackened23]

Nobody actually cares about how and why, give me a break. Let's be real here...When someone forces vsync they expect vsync to be forced, period. That's what should happen regardless of any silly nonsense that you mention. I don't care how or why but with 7970s in 2012, force vsync actually never did a thing. Which for some games is a detriment (dead space series being a good example, since vsync'ed 60 fps is only possible with CP vsync, and fps limiters cause tearing).

Now I don't know if this still happens. But by what you're insinuating, it does, which i'd HOPE is not the case. Does this still happen with CCC? I figured this would have been fixed more than a year ago. Guess not. I guess there's always the app not actually programmed by AMD, radeon pro since AMD's software team can't be bothered.

 

[Final8ty]

Nobody actually cares about how and why, give me a break. Let's be real here...When someone forces vsync they expect vsync to be forced, period. That's what should happen regardless of any silly nonsense that you mention. I don't care how or why but with 7970s in 2012, force vsync actually never did a thing. Which for some games is a detriment (dead space series being a good example, since vsync'ed 60 fps is only possible with CP vsync, and fps limiters cause tearing).

Now I don't know if this still happens. But by what you're insinuating, it does, which i'd HOPE is not the case. Does this still happen with CCC? I figured this would have been fixed more than a year ago. Guess not. I guess there's always the app not actually programmed by AMD, radeon pro since AMD's software team can't be bothered.

1) its to answer bystander36 comment and not you.
2) its not about opinions of the matter, mine our yours, its about why and if you dont care about the facts of why and only what you want should magically be the facts then that's just too bad.