Discussion in 'Videocards - AMD Radeon Catalyst Drivers Section' started by trevtrev19, Jul 10, 2017.
Hey. Now on the site amd
July 17? Driver coming from the future? :nerd:
Well, his access rights "hack" is no different than installing windows on FAT32.
Only difference is that FAT32 has higher tendency to commit suicide.
For Attacks. To do any harm to full access FS. Attacker 1st needs to gain execution privileges on localhost.
Therefore Attacks which his approach is vulnerable to, can as easily wipe all your regular data because very same access level protects them.
And you do not hear about that, nor it happens to you.
Secondly, telnet? I know that you know how it works, so don't go that route.
And backdoor? If you have that, then it no longer matters what access rights you have anywhere.
Yup, it's true peeps... on AMD downloads 17.7.1 release date 7-14-2017, radeon-software-crimson-relive-17.7.1-win10-64bit .exe is dated 7-17-2017.
Just how they pulled this one off is beyond me. Something fishy going on here? :cop:
Anyone seen 'Doc Emmett Brown' lurking about on the dl page? :3eyes:
Eyes peeled, he may be in disguise :eek3:
That seems to have been added to the "Known issues." section, list of fixed issues is the same though.
EDIT: Driver revision is different so they changed something.
Some additional files in the driver folder too.
(171 in total instead of 156)
EDIT: Perhaps WHQL signed?
(Well there's a Microsoft signature on the .dll files in addition to the AMD one now.)
I have no problems with AB with my older CGN 1.0 card, could you by any chance have AB set to unofficial OC mode? I believe that's the one that got broken, but regular mode works fine.
Yup it's WHQL one
It will be avaible at Monday.
You can already download it.
No, unofficial overclocking is disabled in my case. As long as clocks are in 3D mode in games, everything works fine, but during video playback in games where clocks drop, my machine freezes very quickly if my 3D clocks are anything other than the default ones; this includes downclocking.
Has anyone of you had problems with Memory Controller usage? Mine is always at 100% (checked with Msi Afterburner and GPU-Z).
I'll go back to WHQL versions for a while
GCN 1.0 Fluid Motion is still busted.
Guess I'll have to wait for 17.20.
Wait until Monday :nerd:
But why? What's gonna be different?
I mean, I'm using them and they work great...
mod for 7670m?
You get Microsoft's seal of approval.
But these are already WHQL...
Can anyone please test overriding application settings like AA for any game and check if it works?
Would depend on the game, pretty sure it mostly only works for Direct X 9 and earlier whether you're forcing MSAA or SSAA and the "enhance" mode requires the game in question to support MSAA natively plus probably a driver-side compatibility profiles for whatever the game is.
(Forcing SSAA in old Skyrim made a difference at least on the FPS counter, pretty sure it wouldn't do a thing in the new one since it's DX11 now though.)
Unless you mean that the current drivers broke it totally.
As for other settings like AF those definitively work, near texture detail would be a soupy mess if it didn't for games that don't themselves have a AF setting.
(And VSync and triple buffering are mostly OGL only as per API standards or some such, overriding those are unlikely to affect D3D in any way far as I know.)
I've seen New driver for 17.7.1 from July 14 (now unavaible)
And 17.7.1 380MB from July 10 and now new 17.7.1 from July 17 500MB
Somebody please compare those two :nerd:
IMO July 17/14 is WHQL one.