We’ve covered AMD’s progress into open source software development, with most efforts coming through GPUOpen. AMD is keen to point out that over 2016 GPUOpen now provides 70+ SDKs/Samples/Libraries/Tools that are used in common software packages such as VLC, Firefox, Ubuntu, WordPress, Blender and so on. As part of today’s announcement, a few more tools are coming to the box.

Radeon Loom

Radeon Loom was demonstrated earlier this year, and the beta preview is now available through GPUOpen. Loom is AMD’s answer to the current problem of 3D camera content: how to stitch together a sufficient number of flat images to remain seemless in a 360º environment or playback.

With the new preview, using AMD’s open source implementation of OpenVX, developers should be able to use the toolset to create a combined 4K 360º video using 24 images in real time. This becomes important when live video is streamed into a 360º experience, such as sitting on the touchline of a sports game or getting ring-side seats. For non-live content that is pre-processed to consumption, Radeon Loom will support 31 image input for an 8K equivalent display.

OCAT (Open Capture and Analysis Tool)

In the world of benchmarking, two main issues have probed up in recent years. Firstly was the issue regarding multi-GPU frame pacing and runt frames, which exposed not only hardware failure but the failure for software to accurately record what is shown compared to what is computed. To detect runt frames, the FCAT tool was developed involving on-screen overlay, capture, and frame-by-frame processing. This requires a second PC with fast storage, capture cards, and compute resources.

If runt frames aren’t an issue, such as in single GPU environments or with configured multi-GPU profiles, then the most commonly used software for live benchmarking is FRAPS. But due to the way FRAPS takes data, it cannot be used for DX12 or Vulkan due to the different way in which the frame pipeline is managed. AMD’s is promiting a new OCAT tool that is designed to be an all-encompassing frame rate benchmarking tool for modern APIs that is purely software based.

OCAT will support DX11, DX12 and Vulkan with a simple interface and log outputs. Rather than FRAPS that captures any screen that requires a 3D engine, OCAT will operate on software run through itself in order to put in the appropriate hooks required.

OCAT is third-party but also more importantly is open source. Thus despite AMD promoting it, analysis of the code can be performed to make sure there are no hidden tricks to frame calculations. We will be experimenting with the tool for our benchmarking over the course of the next few months.

Increased Game Developer Integration in DX12

One of the key talking points for 2016 has been the move towards DirectX 12, and here at AnandTech we’ve closely followed the sorts of improvements possible from creating content using the latest API as well as extensive testing as the technology was being enabled. As one of the lead partners in the DirectX 12 specifications, we would expect AMD to be promoting its use, and with today’s announcement AMD has stated that they are working with 50+ titles expected to come to market that will use DX12 features, up from the ~15 currently available.

Depth of Field, TressFX 4.0, H.265

As game engines are becoming the go-to tool for certain types of non-game content generation such as storytelling (or even story telling in games), then increased fidelity and realism, along with cinematic effects, are being integrated into these tools. For today’s announcement, AMD has added new tools to GPUOpen for Depth of Field (DoF) and updates to TressFX and H.265.

The DoF update is simple – it applies a relevant set of filters to the parts of the scene that are not meant to be in focus, basically a bokeh for game engines. AMD states this has a low-performance impact.

TressFX 4.0 expands the hair modeling tools initially released with AMD and used heavily in Tomb Raider. Version 4.0 gives increased developer control, and scalable rendering to ensure peak performance with hardware at hand. Version 4.0 is also DX12 supported.

H.265 encoding has been a part of GPUOpen, but with the new launch the tools are being expanded for in-game DX12 frame processing. AMD was light on the details, except to say that more of the H.265 feature set is now available.

AMD Delivers Crimson ReLive: Yearly Feature Update for Radeon Gamers and Professionals LiquidVR: Affinity Multi-GPU, MultiView, MultiRes, TrueAudio Next
Comments Locked


View All Comments

  • PseudoKnight - Thursday, December 8, 2016 - link

    "took a few seconds..." cracked me up

    lol, now i'm imagining you starting up your download manager just in case your sister makes a phone call and you have to resume the download later.
  • A5 - Thursday, December 8, 2016 - link

    It's possible the board designs spec a different HDMI/DP chip that supports it or something.

    Probably just a testing or marketing thing though.
  • Colin1497 - Thursday, December 8, 2016 - link

    Yeah, I have a box with a 285 in it (my son's). Doesn't have an appropriate monitor today, but the monitor is the next thing to get replaced, so it was personal interest driving the Q. :)
  • Manch - Thursday, December 8, 2016 - link

    Was wondering the same thing. Why the rebadge only. Ill start the download :D as soon as I get home. Then I'm requesting the feature for my 290X's
  • nathanddrews - Thursday, December 8, 2016 - link

    The only differences over Hawaii that I know of are that Grenada has refined power delivery, power management, and faster 6 GHz VRAM. Pretty sure that Grenada and Hawaii share the same encode/decode blocks and display outputs, but it's possible that Grenada shipped with higher speed DisplayPort ports and it was never published due to the lack of concrete validation methodology at the time, but I doubt it. Pretty sure AMD/NVIDIA just buy DP/HDMI port hardware/controllers in bulk and order whatever is available at the time.

    Technically, HDR10 metadata can be streamed using older display connections (just like Dolby Vision), but without monitor/TV support, I'm curious to what AMD has planned. My guess is HDR10 will be limited to 8-bit Rec.709 on Grenada, whereas Polaris will get support for HDR10 10-bit Rec.2020, based upon port capabilities alone.

    Why TongaXT is included in the mix and not Hawaii, I don't know.
  • testbug00 - Sunday, December 11, 2016 - link

    Tonga is GCN gen3, Hawaii is GCN gen2.
    Gen1=Cape Verde, Pitcairn, Tahiti.
    Gen2= Bonaire, Hawaii
    Gen3= tonga, Fiji
    Gen4= P11, P11

    There is orland and I think one more 28nm GPU, but I do not know if they are gen 1, 2 or 3z
  • R3MF - Thursday, December 8, 2016 - link

    "On the HDR front, AMD has been promoting that high end R9-300 series"

    What is it about a 390 series card that is absent in the 290 series card, to make the former compliant with HDR when the latter is not?

    Is this purely HDR10 support, or does it include Dolby Vision as EA have said Mass Effect Andromeda will use on the PC? If not, do AMD think this matters?
  • ET - Thursday, December 8, 2016 - link

    Hardware compatibility looks incomplete. It makes no sense for example that user feedback isn't available on APU's, or that VP9 4K60 works on discrete and Stoney Ridge but not on Bristol Ridge.
  • R3MF - Thursday, December 8, 2016 - link

    Re: Linux support

    Does "SLED/SLES 12" support indicate there will be a driver compatible with Opensuse Leap 42.2?
  • PseudoKnight - Thursday, December 8, 2016 - link

    I really appreciate AMD adding features and improvements to even their five year old cards (own a 3 year old card). I've also liked this new direction they've been taking with their software since Crimson. It never felt quite finished (with some things being tacked on) but this looks like it might finally rounds things out. I'm particularly looking forward to testing out ReLive DVR. I suspect I'll stick with OBS Studio, but here's hoping it surprises me.

Log in

Don't have an account? Sign up now