I don't anticipate a long delay.
-
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
I don't anticipate a long delay.
Soldato
But what timeframe are we talking? A few days? If you don't know a timeframe then please just say so.
Last edited:
Soldato
@Matt, will this Win 8 64 bit press driver install on Win 7 64 bit?
I shall install at my own risk, i just need to know if it will actually install in the first place, please answer me matey
I shall install at my own risk, i just need to know if it will actually install in the first place, please answer me matey
Soldato
I would say so. Factor in the weekend and it will probably be middle of next week. They should however make an official announcement so people will know when to expect it rather than keep everyone in the dark.
Like a piece of string then ?
Soldato
Soldato
This is becoming abit of a joke now like..
Soldato
Do you mean the delays? or the amount of people complaining?
Associate
- Joined
- 4 Nov 2013
- Posts
- 654
This is absolutely ridiculous
If they want to do the fancy stuff then so be it, take your time.
But cant they just release all CF profile? Basically they are screwing everyone who is on CF.
It used to be one every 2 weeks/ month, now its 3 months? Its insane.
AMD will lose so many customers because of this driver problem
If they want to do the fancy stuff then so be it, take your time.
But cant they just release all CF profile? Basically they are screwing everyone who is on CF.
It used to be one every 2 weeks/ month, now its 3 months? Its insane.
AMD will lose so many customers because of this driver problem
Maybe they should go back to releasing CAP's? Would give a nice short term fix on an existing driver...
I don't know a specific timeframe, but it's not going to be a long delay. As soon as i have a more information I'll post about it here.
Soldato
Maybe they should have done a seperate driver for the 'fancy' stuff while keeping up with profiles etc in a 'normal' driver. 
Associate
Yeah I agree... they really should go back to the way they used to do it, having CF profiles a separate download to drivers...
Soldato
Sorry to be harsh, but it was weeks ago you were saying they were nearly ready.
Perhaps, if you have no clue, you shouldn't be anticipating anything. Just tell people you don't know.
End of the day, there was no good reason at all to leave crossfire users hanging like this. Driver development, like any other software development can be done in small chunks.
Big features and changes should get branched off and smaller updates can still be made and released in the interim.
Don't know what amd are playing at. The only reason I can think of is they have no software developers, or those developers don't know how to manage code.
Or maybe it's just really, really bad management decisions...
Anyway...... So what's the odds of that elite profile now?
Caporegime
Matt can only go off info that's relayed to him.
He won't be giving dates off his back.
And at the end of the day, the driver was delayed as it was meant to be out in Feb, so anytime he said "Nearly there" he was right. The AMD documentation for Freesync quotes 15.2 (Which obviously never saw public release)
And he'd have been given the 19th as a "firm" release date.
It's not his fault that AMD have the management skills of a monkey.
He won't be giving dates off his back.
And at the end of the day, the driver was delayed as it was meant to be out in Feb, so anytime he said "Nearly there" he was right. The AMD documentation for Freesync quotes 15.2 (Which obviously never saw public release)
And he'd have been given the 19th as a "firm" release date.
It's not his fault that AMD have the management skills of a monkey.
The once every month was using two driver teams, one on whql one on beta, so the whql would always end up 2+ months behind the beta+CAP. AMD scrapped this a while back as it was a confusing mess, as an old driver with a cap was required to play a newer game while the whql didn't support it.
They're on the right path but could really do with going back to releasing CAP updates.