Radeon Software Adrenalin 2019 Edition 19.3.2

[Seyiji]

Support For

• Tom Clancy’s The Division 2
• Sid Meier’s Civilization VI: Gathering Storm
  Up to 4% average performance gains on AMD Radeon VII with Radeon Software Adrenalin 2019 Edition 19.3.2 vs 19.2.3.
• DirectX 12 on Windows 7 for supported game titles
  AMD is thrilled to help expand DirectX 12 adoption across a broader range of Windows operating systems with Radeon Software Adrenalin 2019 Edition 18.12.2 and onward, which enables consumers to experience exceptional levels of detail and performance in their games.

Fixed Issues

• Radeon ReLive for VR may sometimes fail to install during Radeon Software installation.
• Fan curve may fail to switch to manual mode after the manual toggle is switched when fan curve is still set to default behavior.
• Changes made in Radeon WattMan settings via Radeon Overlay may sometimes not save or take effect once Radeon Overlay is closed.

Known Issues

• Rainbow Six Siege may experience intermittent corruption or flickering on some game textures during gameplay.
• DOTA 2 VR may experience stutter on some HMD devices when using the Vulkan API.
• Mouse cursors may disappear or move out of the boundary of the top of a display on AMD Ryzen Mobile Processors with Radeon Vega Graphics.
• Performance metrics overlay and Radeon WattMan gauges may experience inaccurate fluctuating readings on AMD Radeon VII.

Added Vulkan® Support

• VK_EXT_depth_clip_enable
  This extension allows the depth clipping operation, that is normally implicitly controlled by the driver to be controlled explicitly by the application instead. This is useful for translating Direct3D content, which assumes depth clamping is always enabled, but depth clip can be controlled by the DepthClipEnable rasterization state.
  
• VK_EXT_memory_priority
  This extension allows applications to set a priority value at memory allocation time, which could be used to determine which allocations are more likely to remain in device local memory if heap limits are reached.
  
• VK_EXT_memory_budget
  This extension adds support for querying the amount of memory used and the total memory budget for a memory heap.
  
• VK_KHR_vulkan_memory_model
  This extension formally defines how to synchronize memory accesses to the same memory locations performed by multiple shader invocations.
  
• VK_EXT_debug_utils
  This extension allows developers to obtain more debug information. When combined with validation layers, more detailed feedback on the application's use of Vulkan can be further obtained.
  
• VK_KHR_depth_stencil_resolve
  This extension adds support for automatically resolving multisampled depth/stencil attachments in a subpass in a similar manner as for color attachments.
  
• VK_KHR_shader_float16_int8
  This extension allows use of 16-bit floating-point types and 8-bit integer types in shaders for arithmetic operations and improves usability of those types by adding implicit conversions.
  
• VK_EXT_transform_feedback
  This extension adds transform feedback to the Vulkan API by exposing the SPIR-V TransformFeedback and GeometryStreams capabilities to capture vertex, tessellation or geometry shader outputs to one or more buffers.

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-3-2

 

[Falck]

Metro Exodus w. VII and Samsung C34F791 w. Freesync enabled is a real pain in the ass to get to work...

I experienced similar problems with Deus Ex - Mankind Divided, and it turned out DX12 x. Exclusive Mode was the culprit, but no such setting in Metro...

 

[LordHawkwind]

Until they fix the POS they call fan curve I'm avoiding all these updates. Whomever came up with the idea of the fan curve needs to be taken to one side and severly bollocked and told to fix it! Won't happen, of course, as RTG has no real leadership and as Einstein once said “Insanity is doing the same thing over and over again and expecting different results.” This is where the AMD driver team are at the moment.

 

[Seyiji]

Until they fix the POS they call fan curve I'm avoiding all these updates. Whomever came up with the idea of the fan curve needs to be taken to one side and severly bollocked and told to fix it! Won't happen, of course, as RTG has no real leadership and as Einstein once said “Insanity is doing the same thing over and over again and expecting different results.” This is where the AMD driver team are at the moment.

Not saying things are fixed or anywhere close to being where they need to be but I noticed after playing the division 2 with these and exiting the game the fan actually stayed at a higher rpm instead of immediately dropping away like previous drivers.

Might wanna check them out if you're on 19.2.2 or lower.

Other than that I agree 100%

 

[LordHawkwind]

Not saying things are fixed or anywhere close to being where they need to be but I noticed after playing the division 2 with these and exiting the game the fan actually stayed at a higher rpm instead of immediately dropping away like previous drivers.

Might wanna check them out if you're on 19.2.2 or lower.

Other than that I agree 100%

Seyiji what speed does the fan ramp up to when you're gaming? Mine is set to a max of 2700 rpm and I get about 1525 on the core and temps in the 70's. When I tried the new drivers the fan was going over 3000 rpm FFS. Not in a rush I can wait until they fix it or go back to the old fan style.

 

[LordHawkwind]

Just checked I'm actually on the 18.12.1.1 drivers

 

[Seyiji]

Seyiji what speed does the fan ramp up to when you're gaming? Mine is set to a max of 2700 rpm and I get about 1525 on the core and temps in the 70's. When I tried the new drivers the fan was going over 3000 rpm FFS. Not in a rush I can wait until they fix it or go back to the old fan style.

It ramps up to my target fan speed of 65% which for me is about 3100 rpm.

Just tested in Division 2.

I ran 2 benchmark runs back to back. The fan ramped up properly and sustained its fan speed locked at 65% when the game was benching. After exiting the bench and loading back to the settings menu it slowly ramped the rpm/speed during that time as the gpu was cooling down due to no load. On the second run after the bench mark started the fan started ramping back up and it again hit my target fan speed of 65% at around 3100 rpm.

Looks like it's properly doing what I told it to do in the fan settings above at least for the part where I set it to go ham at up to 65% at 75 degrees.

I've only tested this in The Division 2 but if you need any more info ask and I'll see what I can do.