crisium
Platinum Member
- Aug 19, 2001
- 2,643
- 615
- 136
Memory type: HBC (High Bandwidth Cache, not HBM2).
AMD just uses the term "HBC" (High Bandwidth Cache) instead of "VRAM" now (as of Vega). It is still HBM2.
Memory type: HBC (High Bandwidth Cache, not HBM2).
We need a hero! Will someone step up?drivers are ready for vega for gaming.Someone buy that thing and test it
http://support.amd.com/en-us/download/frontier?os=Windows+10+-+64
http://pro.radeon.com/en-us/product/radeon-vega-frontier-edition/
Which is exactly what you tried to do in the post I quoted you!!
I'm pretty sure that's because AMD hasn't finalised optimizing the gaming drivers, thus performance is looking really bad vs the competition and the card would be getting bad press
Now this is interesting to me. Does this imply that the Vega FE will be compatible with standard Radeon drivers? I wonder if this means we can get some good gaming performance estimations from it (yes yes, caveat, might not be finalized drivers.)
Let's get this party going!
AMD just uses the term "HBC" (High Bandwidth Cache) instead of "VRAM" now (as of Vega). It is still HBM2.
No samples probably means paper launch, so little availability that they could not even sample reviewers.
Doubt that
Ryan Smith said:I expect these cards to completely sell out, so from AMD's perspective I doubt they saw a need to sample cards.
Switching between PRO and RX modes (see the tab in the bottom left corner).
Source: AMD on Youtube.
I know. I just pointing it out.
It's not a paper launch. The cards are in stock right now at multiple etailers with 1-2 shipping days and are not sold out yet.
So my question is will the strictly gaming variant still be supposedly faster in gaming? Or with this mode switch software both are basically equal?
What exactly does this "gaming/pro" switch do?
it'd be interesting to see a frame by frame differences between the gaming driver output and the dev driver output. or do a full analysis using SSIM or something similar.It switches between the pro and gaming drivers...
Gaming drivers have tweaks / "hacks" for optimization. Pro drivers don't because they are "accurate".
it'd be interesting to see a frame by frame differences between the gaming driver output and the dev driver output. or do a full analysis using SSIM or something similar.
different architectures are designed to run at different speeds and each have their sweet spots. clock for clock comparisons are about as useful as the old hp per cubic inch is.What I really would like to see is a clock to clock comparison with Fury X :>
Yes absolutely this. Clock the memory to a similar level and see what exactly 4096 GCN can do vs 4096 NCU.What I really would like to see is a clock to clock comparison with Fury X :>
What I really would like to see is a clock to clock comparison with Fury X :>
different architectures are designed to run at different speeds and each have their sweet spots. clock for clock comparisons are about as useful as the old hp per cubic inch is.
Yes absolutely this. Clock the memory to a similar level and see what exactly 4096 GCN can do vs 4096 NCU.
Info from RysSebastian Aaltonen said:Just got a Vega FE. Going to test some fp16 optimizations tomorrow. I have a few juicy targets
At some point I also need to test the paging system. It is awesome that we finally have automated paging on graphics workloads. Let's see how it manages a 32 GB volume texture
Update: Maybe I should buy extra 32 GB RAM to test with 64 GB volume texture instead
Full Feature Level 12_1 support, me gustaI handed the board to him [sebbi] myself earlier today in Helsinki, over a beer. The joys of looking after Game Engineering for Europe. Full architecture details will come out later, can't spoil that, but it is FL 12_1 top tier for everything.
Comparison to R300, really? In reaction to a post from another user asking if he is kidding he wrotesI think RX Vega will be comparable to Radeon 9700 in terms of impact.
Source: Beyond3D forumsWhy do you think it is a joke? Just think in analogues - of where AMD was before and where AMD will be after.
Yeah.. but I'm quite curious why we haven't seen something from Johan "repi" Andersson (Technical director & "pixel pusher" of Frostbite engine)Holy sh***
It's something when you have guys of that caliber saying such stuff..
So, are you trying to say that Vega doesn't fully supports FL12_1 or automated paging on graphics workloads or what?People have biased opinions when they get free stuff before it's released. I see it all the time.
You don't know these people though. Rys works for AMD RTG now as European game engineering relations and obviously really likes the product, but he has a high level technical background, runs Beyond3D and has been in the industry for a long long time. sebbbi is a no-nonsense dev who simply loves to talk programming and hardware and has displayed no bias whatsoever in many years I've read B3D other than when he really loves features for what he does, irrespective of the company. He is probably one of the most knowledgeable people around when it comes to GCN architecture.People have biased opinions when they get free stuff before it's released. I see it all the time on junior bloggers and tech journalist because they don't have an experienced editor behind them to correct and control their biases.