Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,675
- Location
- The KOP
WHQL means jack!... All it means is that Driver branch passed testing! it don't make the driver any better than a Beta driver!
-
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.
The AMD Driver Thread
- Thread starter LtMatt
- Start date
WHQL means jack!... All it means is that Driver branch passed testing! it don't make the driver any better than a Beta driver!
Its fact, all whql means is microsoft tested it. Hasn't stopped drivers in the past being dodgy despite being whql.
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,675
- Location
- The KOP
Because its the truth!
All WHQL means is Microsoft has passed it with testing, it dont make the driver any better or gain anything over a beta driver..
You tell me, maybe something I don't know... What makes a WHQL driver any different to a Beta driver!
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,675
- Location
- The KOP
The spelling
I've always used beta drivers. Never had a problem!
Beta drivers always offer the better features and performance.
Yup they do seem to be all their effort into windows 10 but the problem is:
- we have had sub-par support for the last 7 months now
- not everyone is going to jump on w10 straight away, I generally wait for a few months till the issues get sorted out
Permabanned
- Joined
- 12 Sep 2013
- Posts
- 9,221
- Location
- Knowhere
Exactly....
Plus, It's like there's always something else for them to direct there efforts towards
Caporegime
- Joined
- 8 Jul 2003
- Posts
- 30,063
- Location
- In a house
I don't know why they don't just release the drivers now, Win 10 isn't released till the end of the month, so why hold them back for it, just release them now for Win 7/8/8.1 users, then when Win 10 gets released, release em again for that.
The spelling
I've always used beta drivers. Never had a problem!
Can you tell us when the optimized drivers for the 200s will be realised? It's getting past a joke now.
Caporegime
- Joined
- 8 Jul 2003
- Posts
- 30,063
- Location
- In a house
They'll be released end of the month, with Win 10.
Associate
- Joined
- 11 Apr 2014
- Posts
- 67
So after installing the modded drivers for my r9 290's my mouse pointer is massive and I cant change it, windows says default size, anyone got any ideas?. 4K resolution if that makes any difference.
Associate
- Joined
- 4 Nov 2013
- Posts
- 654
When is AMD going to release FreeSync CF profile?
Soldato
- Joined
- 23 Dec 2013
- Posts
- 3,547
- Location
- North Wales
AMDMatt said:
In all serious we don't know when it'll be ready, we've not been told much by AMD. "When it's ready" is probably the most accurate answer you'll get until AMD tell us otherwise. The modded 1040 drivers on Guru3D have semi-working Freesync Crossfire, it's a bit buggy though from what i've heard.
Last edited:
Soldato
- Joined
- 23 Dec 2013
- Posts
- 3,547
- Location
- North Wales
Just seen someone mention that some AMD cards are having problems runnning the DX12 API test correctly. One of which was mine... So now i know why mine wouldn't work no matter what i tried.
Source: http://www.futuremark.com/support/update/3dmark
I'm not too pleased that a 3rd party had to tell us that... AMD obviously didn't bother.
EDIT: At least 15.200.1023.7 fixes the problem and the DX12 now works. Mantle seems to be a no go though now.
Source: http://www.futuremark.com/support/update/3dmark
I'm not too pleased that a 3rd party had to tell us that... AMD obviously didn't bother.
EDIT: At least 15.200.1023.7 fixes the problem and the DX12 now works. Mantle seems to be a no go though now.
Last edited:
its a beta driver for a beta unreleased OS? did you submit a report with AMD on finding the problem and are unhappy they didn't reply or did you not tell them about the bug and just expected them to tell you that a 3rd party bit of software had a problem between 2 unreleased bits of software?
Seems like there was an issue, the two companies knew about it and it was fixed in a following update, before release?
Seems like there was an issue, the two companies knew about it and it was fixed in a following update, before release?
Soldato
- Joined
- 23 Dec 2013
- Posts
- 3,547
- Location
- North Wales
I'm well aware that it's a beta and that there are likely to be issues, i would just like like AMD to be a bit more communicative when a problem is found. 3DMark obviously knew about it so no doubt AMD would have known.
Previously in this thread i was having problems getting the DX12 API test to work and no matter what i tried it would not work. I did report it to AMD (and Microsoft) but never heard a thing and it was never acknowledged. All i think they need to do is be a bit more proactive with regards to reported issues and publicly state the issues.
3DMark knew there was an issue and that it was going to be fixed by AMD in the next update (which it was). My point is basically asking why AMD is not acknowledging these problems? Mantle seems to have some issues in the latest driver, it seems i'm not the only one by looking on Guru3D. I have reported it but i'm doubtful i'll hear anything back or even just get an acknowledgement.
If Matt was still here as much as he used to be then i'm sure he would have chased it up, but since Matt has gone over to the AMD Forums there is no chance of getting hold of anyone at AMD. The one post i made on the AMD forums only got a snotty reply which is why i didn't want to bother on there. I still report the issues i have to MS and to AMD directly as i know they get them but what would be nice is just a bit more communication.
TL;DR - AMD needs to communicate with their customers better and be a bit more forthcoming with information on known issues.
FAO Matt or Joe - Would you mind passing this on if you can?
Last edited: