Changing memory clocks with Radeon WattMan with more than one display connected may cause memory clocks to intermittently become stuck at their minimum setting or switch between min and max ranges intermittently causing display flickering.
Diablo®III May experience smoke or lighting effects may appear corrupted when using DirectX®9 API.
Some applications may experience an intermittent or random runtime crash in atidxx64.dll.
FIFA®17 may experience a black screen on launch when using Hybrid Graphics or AMD PowerXpress system configurations.
Watch_Dogs®2 may experience an intermittent game crash after extended periods of play on some Radeon RX 300 series products.
Paragon™ may experience flickering in profile or store preview pages after changing graphics settings when using Multi GPU.
Forza Horizon 3 may experience a crash or application hang with the Blizzard Mountain DLC on some select Radeon GCN products.
Known Issues
A small amount of apps may still experience issues with Borderless Fullscreen mode and AMD FreeSync™ technology if other applications or game launchers are running on the primary screen in the background.
Counter-Strike™: Global Offensive and World of Warcraft™ may experience flickering or performance issues the first time the game is launched on a system boot with AMD FreeSync™ technology enabled. Workarounds include exiting and restarting the application or task switching (alt+tab) in and out of the game to fix the issue.
Radeon RX 400 series products may experience scaling issues for some applications when using the display scaling feature.
Deus Ex: Mankind Divided™ may experience an application hang when running in Multi GPU with DirectX®12 and performing a task switch.
Mouse cursor corruption may be intermittently experienced on Radeon RX 480.
Counter-Strike™: Global Offensive has incorrect default slider values with Radeon Chill enabled. Users can modify these values to suit the experience they want.
Known Issues for Radeon ReLive
The XBOX™ DVR application may cause conflicts with Radeon ReLive, users are suggested to disable XBOX™ DVR if Radeon ReLive is experiencing issues.
Radeon ReLive may fail to install on AMD APU Family products or experience a system hang or failure to record when using the recording feature on AMD APU Family products.
Radeon ReLive may stop working after hot unplugging of a secondary display.
Battlefield™1 may experience UI flickering and/or performance drops when recording gameplay with Radeon ReLive on graphics products with 4GB or less of VRAM.
Radeon ReLive recordings or overlay may experience flicker when creating a single recording for many hours.
Radeon ReLive may experience minor graphical corruption for the first few recorded frames when launching UWP applications.
Radeon ReLive will not allow recording settings to change with Instant Replay enabled. A workaround is to disable Instant Replay and change settings then enable Instant Replay.
Vulkan™ applications may experience a game hang when using Radeon ReLive to record.
Radeon ReLive will not notify an end user of low disk space during recording.
DayZ may experience an application crash when Radeon ReLive Instant Replay/Recording is active or the feature may not work as expected.
Krteq píše:Jinak AMD v ReLive Edici přešla na OverdriveNext API což může způsobovat problémy s MSI AB/TriXX a dalšími utilitami pro OC ve vlastním, neoficiálním OC módu
Unwinder píše:Old good and traditional Overdrive 6 overclocking/monitoring/fan control API for 2x0/3x0 series cards have been totally locked for such hardware and now AMD try to port support for those old cards to new Overdrive 7 (aka OverdriveNext) API, which was previously supported by Polaris architecture only. So you'll absolutely need a software with OverdriveNext API support to get it working, old legacy software with Overdrive API support will simply stop working now due to lacking support of legacy Overdrive API...
...4.3.0 in official overclocking mode is already compatible with OverdriveNext API.
U MSI AB se to dá obejít vypnutím Unofficial overclocking mode v nastavení (přepnout na disabled a restartovat)
Jinak, pokud používáš utility třetích stran, je dobré Wattmana v Radeon Settings vůbec nezapínat - dochází potom ke konfliktům.
No, stačí aby jsi po instalaci neakceptnul ten disclaimer a wattman je víceméně neaktivní, tj. nezasahuje do řízení karty a nehádá se s utilitami třetích stran.
Proč bych měl nastavovat 120Hz, když mám 144 monitor? Nejde to řešit nějak jinak? Stáhl jsem poslední BIOS poslední ovladače a stejně nic. Nemá vliv ani to, když si s tou frekvenci hraju..
Když necháš 144Hz tak budeš mít prostě plný takt pamětí.. musíš se s tím smířit.. AMD to prostě ještě nevyřešilo.
Rozdíl mezi 144Hz a 120Hz nepoznáš...
Je to chyba na straně AMD.
Download a kompletní release notes: Radeon Software Crimson ReLive Edition 17.1.2 Release Notes
