• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

AMD Hire Jim Anderson

AMD/ATI's problem is their driver development has ALWAYS been awful. This is the first thing he needs to change.

Fine for single cards, some issues for crossfire if you play certain games.

nVidia's 2 latest drivers are crashing for a lot of their users.

On topic: Hopefully Jim'll fix it.

I'll get my coat.
 
Utter rubbish about AMDs "problem" being drivers are always bad, sure at the moment they are super slow coming out and have had some bad or missing drivers/profiles but NVIDIA also have had their share of issues with drivers as well.

AMD has a whole bunch of issues from really bad marketing techniques, slowing down of driver development (to a complete crawl), slow/ill timed release of hardware and I'm sure a whole lot more. All these have resulted in a shrinking market share, which just worsen the issue. AMD have been spiraling for a while they need to pick them selves up with the 390 for sure. I've been with AMD since 2009, currently own two 290s and really cant see myself spending more money, would rather pay the NVIDIA tax at this point.

Simple said AMD aren't bad, but Nvidia just are better in every department really, but to blame it all on 6 months of missing Xfire profiles and slow drivers is just silly.
 
Last edited:
Jimmy Anderson recently became England's all time leading wicket taker, AMD must really mean business.

James_Anderson_006.jpg
 
They can't even do basic things like force v-sync in D3D, there's clearly something wrong when you have to rely on 3rd party software for simple features.

Choosing not to and cant do are 2 different things and you have been told enough times now so you are just talking your usual BS because if they could not then the option to force Vsync on or off when outside of the freesync range would not exist.
 
Last edited:
Choosing not to and cant do are 2 different things and you have been told enough times now so you are just talking your usual BS because if they could not then the option to force Vsync on or off when outside of the freesync range would not exist.

Choosing not to offer a basic feature that is super useful to customers is pretty stupid business practice though really, it's never stopped NVidia from being WHQL certified so I'm not sure why AMD wouldn't offer it.

Having to use all manner of 3rd party software to enable basic features that NVidia offers as part of their everyday package is one of the reasons why NVidia have run away with the market, whether it's a choice that AMD make or not.
 
Last edited:
They can't even do basic things like force v-sync in D3D, there's clearly something wrong when you have to rely on 3rd party software for simple features.

Is this connected to my computers current inability to keep v-sync turned on while paying Rage?. I turn it on and it seems to turn off 20 minutes later even though I'm still playing and in Rage without v-sync there's a huge crease across the centre of the screen.
 
Choosing not to offer a basic feature that is super useful to customers is pretty stupid business practive though really, it's never stopped NVidia from being WHQL certified so I'm not sure why AMD wouldn't offer it.

Whether you agreeing or not with AMD following the guidelines is besides the point as it was MS that screwed it all up in the first place and as i have said AMD allow it with freesync.
And the amount of games that dont have a Vsync option is tiny which makes it practically a non issue.

And if NV was so great at offering feature that users want there there would not be a need for the 3rdparty nvinspector.
Swings and round abouts.
 
Last edited:
Is this connected to my computers current inability to keep v-sync turned on while paying Rage?. I turn it on and it seems to turn off 20 minutes later even though I'm still playing and in Rage without v-sync there's a huge crease across the centre of the screen.

RAGE is openGL not DirectX, force triple Buffering instead.
 
Is this connected to my computers current inability to keep v-sync turned on while paying Rage?. I turn it on and it seems to turn off 20 minutes later even though I'm still playing and in Rage without v-sync there's a huge crease across the centre of the screen.

Nothing to do with it.





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 bugger 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


Forcing triple buffering outside of the game is also against the WDDM spec & Microsoft guidelines.
 
RAGE is openGL not DirectX, force triple Buffering instead.

How would I do that? The game only has v-sync on and off, There's something called gpu transcode but I think that must be an Nvidia thing as when I try to use it there's a message saying my card either does not have enough ram or is not compatible, I'm using a 4gb 290x running 1440 through a 1080p via vsr.


EDIT: You mean via catalyst. Okay I'll try that thanks.
 
gpu transcoding in that game was put in place to help with texture pop-in, it's nothing to do with Nvidia or amd.

Add rage.exe in ccc and tick the box for openGL triple Buffering..

I can't remember but at 1440p am sure Rage was very vram hungry and adding in more texture reading might be using up the 4Gb reason for the warning.. Been a while since I played that game on my old 7950s
 
Back
Top Bottom