16.6.2 drivers available from AMD

yeah, i cant do it.

i want a 1070, but i dont want to change eco-systems.

 

Under 16.6.1, Dragon Age: Inquisition would b0rk and not run under Mantle. (Closed down before Bioware intro. It also did not go into fullscreen mode when booting) After doing upgrade install to 16.6.2 it will now boot to main menu and is playable.

 

Hmm, not working for me :bang:

Its Time for ZEN x8/16 on my side :thumbup:

Same thing i have with ME Catalyst Beta.... SSE 4.1 etc.

 

my display doesnt sleep any more

 

Soon we will have good news:

In a sign of self-confidence, AMD has announced the acquisition of gaming software specialist HiAlgo

HiAlgo has three key technologies – Boost, Switch, and Chill. Boost reduces lag and improves the framerate of games. It also claims to optimise performance frame by frame' to dynamically scale the rendering resolution: during motion-heavy moments, the resolution is dropped to boost the framerate; during relatively calm moments, the resolution is increased to boost the visual quality of the scene.

Switch gives manual control over the HiAlgo Boost system and provides a 50 per cent resolution rendering mode. However all overlays - including in-game menus and head-up displays remain at full resolution.

Chill is aimed at mobile gamers and modifies the framerate using the same principles as Boost. High-motion scenes get a high framerate, while low-motion scenes get a lower framerate. This, the company claims, results in lower power draw and heat output from both the CPU and GPU.

http://www.fudzilla.com/news/graphi...-cheque-for-gaming-software-specialist-hialgo

http://venturebeat.com/2016/06/29/a...friendly-tools-to-radeon-software-experience/

http://www.hialgo.com/Downloads.html

 

What I would really like from you is an honest comparison between the single-gpu experiences for both. Of course the 1070 would kill your 280x, but I would still be curious about it.

I'm a bit in this boat too, although the NVIDIA Inspector along with the standard features from the driver should more than make up for it. Although the scripting abilities and tessellation control are the sh*t.

I hope that it means that we have an "advanced" part of the driver, where FINALLY things like double vsync/adaptive vsync/triple buffering will finally FINALLY happen. If it is for them to make another "gamer" abomination like the Gaming Evolved app that looks like malware, then no thanks. If you combine the purchase with the beta program though, there might be some hope.

 

Hope so.
Maybe will have some boost in DirectX 11 games.

 

I did download and check all 3 of them. Works fine. But trigger for dynamic resolution is bad as can get.

It changes resolution based on how fast viewport/mouse moves around. That's tragic, because you can have 200+ fps and it will still decrease resolution as you turn around.

Good thing is that they keep HUD at full resolution. I found some fps threshold and motion thresholds. Testing begins.

 

HiAlgo => Our hardware is too slow, so we will dynamically reduce image quality to make up for it.

Switch => Same as HiAlgo but done manually.

Chill => Same as HiAlgo but for Mobile users.

I sure as hell hope this abomination is aimed at Consoles because there is no way AMD is going to shove it down our throat.

 

Since I am not you (dummy), I'll explain to you what they are. (Not that I think HiAlgo's implementation is any good.)
That what you call "HiAlgo" is Actually called "BOOST".
- It dynamically reduces framebuffer resolution based on movement speed of mouse
- That means IQ is reduced only as you move mouse left and right/up and down.
- Considering screen pixel persistence and game's motion blur, many people may not even notice or care about difference
- And on top of your not knowing, it allows you to set manually reduced resolution as you want 50/60/70/80/90% of original (ignoring mouse inputs)
- HUD resolution is always at full resolution
- Probably good for 4k gaming as HUD will be at max while game itself will not be worse than 1080p

"SWITCH"
- It allows you to set manually reduced resolution as you want 50/60/70/80/90% of original
- it has secondary mode which dynamically reduces framebuffer size to keep certain fps (fps range is from 10 to whatever in steps of 10)

"CHILL"
- No, It does not reduce framebuffer size as those two above (and as you think)
- It is actually dynamic fps limiter
- It limits fps at times when you are not moving mouse and pressing keys

 

Thank you for the detailed analysis, but you just proved my point, dude. I don't care if it works well or not (or even what it does under the hood), it just trades quality for performance, which I for one would never want to do. AMD should spend their money on hiring new people to work on their drivers, rather than trying to run away from the problem by cheap workarounds like these algorithms.

If acquiring this company was going to result in RadeonPro-like features being added to the drivers, I'd be all up for it, but as it seems, the new features are going to be "Raptr-like" features.

 

so switch is something like the resolution scale that some games have already incorporated right? like doom, dayz, battlefield 4...

i really wanna see some videos of "BOOST" in action but i am really not sure if i like it for gaming. i can't see how chaning resolution during gameplay wouldnt bother me. do you know any presentation material?
or is it easy to test already somewhere?

 

Boost video:

Code:

https://www.youtube.com/watch?v=5nMa73XvWV0

The effect on visual quality, especially in terms of aliasing, is so apparent you can even see it clearly despite Youtube's horrible compression. Then again this is aimed at people who cannot even sustain 30 FPS in games with modest visuals.

 

Anyone else having problems with Bezel compensation?

When I make my PLP-Eyefinity display group and then click Bezel compensation button, all my displays get disconnected and after reconnecting, Eyefinity has changed itself to LLL-Eyefinity and I can't change it back to PLP without deleting the display group.

Same problem happens with older Crimson drivers as well. I had to revert all the way back to latest Catalyst release to get the bezel compensation working again.
Then I just upgraded to the latest Crimson and it retained the display group, but its a pain in the ass to revert back to CCC if I need to make some adjustments to bezel compensation.

I did file a bug report to AMD but I still think nobody actually bothers to read them at AMD HQ.

 

VSR still not working. T_T

No matter, I've got a 1080 coming soon. So whatever...

 

Not working how exactly? I have no issues on my side.

http://i.imgur.com/AilogBY.png

 

There are always a few cases where things just don't work. Whether it's user error, messed up OS installation or strange hardware combo.

But yeah, no VSR problems here either.

 

And it is never a bug in the software/driver? For example, is the artificial limit AMD has put on maximum VSR resolution for HD 7000 series a user error, messed up OS installation or strange hardware combo?
How about the fact that in most cases, VSR does not work in exclusive fullscreen mode and borderless fullscreen has to be used, while the latter will break CF in many cases, leaving CF users with the choice to either use one GPU or give up on VSR?
Or how about a game like Legend of Grimrock 2 (and probably also 1) which doesn't support MSAA/SSAA and could really benefit from VSR, but VSR doesn't even work with it? (I reported this ages ago, they might have silently fixed it by now but I doubt it.)

No, it is not always a user error or OS problem or bad hardware combo (whatever this last one is...); in many cases, it is a software/driver problem.

P.S. Derko1's reply is pretty vague but people should really stop blaming the user for everything. I have to agree in many cases the user does not bother to do proper research and ends up complaining about something that is his own fault, but this is not always the case and should not be the default judgment either.

 

I was not blaming anyone. Of course there are driver bugs. It's just that there are driver bugs that are easy to reproduce by large number of users and those that only surface with either messed up OS, unusual hw combo, etc.

That's why you have certain users that always seem to have problems with every driver that's released.

As for mGPU, sorry but you guys should have known better.

 

For me it crashes randomly under Mantle. Don't know if it is a game or a driver problem, or both.