• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Poll: The Vega Review Thread.

What do we think about Vega?

  • What has AMD been doing for the past 1-2 years?

  • It consumes how many watts and is how loud!!!

  • It is not that bad.

  • Want to buy but put off by pricing and warranty.

  • I will be buying one for sure (I own a Freesync monitor so have little choice).

  • Better red than dead.


Results are only viewable after voting.
What features are these? Draw Stream Binning Rasterizer is already enabled on Vega 64.

From everything that been throw about its not, primitive shaders is partly on but primitive discard isnt fully enabled yet, rasterization isnt fully on yet and hbcc isnt fully implimented yet.

Also it would be quite easy for you to clear up, just show us the patch notes for the driver that shows what is and isnt enabled.
 
Turn off all the crap you don't need or like and that will go up to 60 fps easy. Ultra settings are way over rated.
+1

These days there are so many settings that imo makes IQ worse and suck fps. With a 1080ti one could play most games at 60fps with a bit of tweaking. The real 4K card will probably be Titan XV.
I have been tempted to pick up a 1080Ti Aorus extreme as I have seen them at a decent price, but stopped myself as Volta is only roughly 6 months away now. Might as well wait and get some new tech. Not like there anything I am dying to play. Still, very tempting though :p
 
No. It categorically isn't. Stop spreading FUD. Neither is DSBR.

Technically it seems many of these features are "enabled" but not actually working optimally or actually being utilised - some can only function in compatibility "deferred" modes without further developer support or need to be utilised by developers.

Those hoping for a miracle from these features are likely going to be sorely disappointed especially as the bigger gains will likely be power saving when a developer properly utilises them :s
 
Technically it seems many of these features are "enabled" but not actually working optimally or actually being utilised - some can only function in compatibility "deferred" modes without further developer support or need to be utilised by developers.

Those hoping for a miracle from these features are likely going to be sorely disappointed especially as the bigger gains will likely be power saving when a developer properly utilises them :s

Technically we dont have a clue what is enabled and might not be working and whats isnt enabled and isnt working. Anyone wanting to know what is actually going on needs full patch notes to understand what amd have and have not done. Having a game of chase the tail on the donkey of rumors doesnt help.
 
Technically we dont have a clue what is enabled and might not be working and whats isnt enabled and isnt working. Anyone wanting to know what is actually going on needs full patch notes to understand what amd have and have not done. Having a game of chase the tail on the donkey of rumors doesnt help.

AMD have published some information the problem is people looking for something that isn't there. Many of the related rasterisation features for instance are working but just run in a moderately efficient compatibility mode unless the developer specifically selects traditional, deferred (default) or immediate (high efficiency) modes.
 
AMD have published some information the problem is people looking for something that isn't there. Many of the related rasterisation features for instance are working but just run in a moderately efficient compatibility mode unless the developer specifically selects traditional, deferred (default) or immediate modes.


There patch notes are simply a few highlights of what they have done to fix some things and known bugs. And its not a case of people looking for something that isnt there, the problem is to have an actual conversation with factual information is utterly devoid of any fact when we have nothing but rumors and 3rd hand information togo from. What performance difference these features may or maynot provide are irrelivant if we have no idea if these features are even turned on or off, or completly broken.
 
AMD have published some information the problem is people looking for something that isn't there. Many of the related rasterisation features for instance are working but just run in a moderately efficient compatibility mode unless the developer specifically selects traditional, deferred (default) or immediate (high efficiency) modes.

So if developers start using all of Vega's features properly then it might prove to be a much more capable card than we are seeing atm. That's not really looking for something that is not there it's looking for the improvements that these features when used will give. For now it's pretty much a Fury X on steroids.
 
So if developers start using all of Vega's features properly then it might prove to be a much more capable card than we are seeing atm. That's not really looking for something that is not there it's looking for the improvements that these features when used will give. For now it's pretty much a Fury X on steroids.

The biggest gains of many of these features is in reduced power draw not performance (which might be partly why they don't - you still have the same input data and it still produces the same output data, though later stages in the GPU pipeline might be slightly under-utilised due to lack of optimisation but the intermediate stages will be working at "100%" to produce the output when if they were handed more optimised data by the earlier stages they could be working at say 60% instead reducing the power drawn by those parts of the GPU.
 
So if developers start using all of Vega's features properly then it might prove to be a much more capable card than we are seeing atm. That's not really looking for something that is not there it's looking for the improvements that these features when used will give. For now it's pretty much a Fury X on steroids.
It's a bit of a gamble from AMD isn't it, that devs will start to spend time, money and resources using these features that will benefit such a small percentage of customers. It's not just Nvidia domination of the market, it's also that older AMD cards also won't benefit (at least not from all of them).

It seems Nvidia makes cards that do what developers currently do perform well and AMD make cards that will perform well if developers start doing things specifically to make the game work well on AMD products.
 
The biggest gains of many of these features is in reduced power draw not performance (which might be partly why they don't - you still have the same input data and it still produces the same output data, though later stages in the GPU pipeline might be slightly under-utilised due to lack of optimisation but the intermediate stages will be working at "100%" to produce the output when if they were handed more optimised data by the earlier stages they could be working at say 60% instead reducing the power drawn by those parts of the GPU.


I find that an odd statement when the main part of these features is more performance for the same workload, prime example of this is when bethesda broke gameworks and suddenly nvidia slide down in performance, if that was simply for power saving then performance would not have taken a hit as it did.
 
Had a play on amiens (supposed to be a wonky map for frame rate) with my titan system, lowest fps i got was 60, mainly in the 70's for actual gameplay. In maps like Sinai desert that's more in the 80fps range. Recorded a vid will up it later when my upload speed is doing better than it is currently.
 
Technically we dont have a clue what is enabled and might not be working and whats isnt enabled and isnt working. Anyone wanting to know what is actually going on needs full patch notes to understand what amd have and have not done. Having a game of chase the tail on the donkey of rumors doesnt help.

AMD have publicly announced that these features are working in the RX Vega drivers.


The problem is certain AMD fans are just in disbelief at the current situation and are trying desperately to find excuses or keep their hype train rolling. If important features aren't enabled now then they never will be, so it is also an irrelevant question for a performance perspective. Some people mistakenly think that tehse features will add 30+% performance when the reality is individually they give a few percent and even that will be very dependent on the current scene.

The unfortunate aspect of computing is that you are always limited by the slowest tasks, and even when you speed up a task significantly, e.g. by 50%, the overall speed increase is small because other factors become more limiting.
Rendering a scene might invovle 10,000 computational tasks say (exact number irrelevant, but there are lots. Most takes contribute a tiny fraction of a percent to the rendering time. The worst offending tasks that are the slowest might take 4% of the rendering time. You do some sophisticated optimizations in hardware or software and twice as fast, well now your frame rate has improved by the whole of 2%.
 
Back
Top Bottom