"Because the game drivers aren't ready yet" would be the obvious answerI still don't get the FE brand. It would make more sense to have a consumer optimized card (gaming) and a pro card (content). This thing seems to try to replicate Nvidias market strategy with the Titan brand but with semi-optimized game drivers... why?
There was no need, TitanXp has just a small performance bump over TitanX Pascal, which already got sent to every major media outlet at the time of it's release.Funny how there wasn't such chaos and grief when NVIDIA didn't send Titan Xp to press (yes, of course new architecture is different thing, but still no-one even shrugged at that)
32 bytes for GDDR5 and HBM2, 64 bytes for GDDR5X.[...]
None of those anything to do with BW reduction.
AFAIK, the prefetch size is 32 bytes for both HBM and GDDR5 (and 64 bytes for GDDR5X?) It's just that you trade clock rate for bus width.
[...]
Then, release it when it's ready?"Because the game drivers aren't ready yet" would be the obvious answer
From said driver's INF file:Note that AMD themselves are providing and linking to game drivers for the FE dated 6/27
http://support.amd.com/en-us/download/frontier?os=Windows+10+-+64
Then, release it when it's ready?
These kind of "Funny how..." posts never get old, do they?Funny how there wasn't such chaos and grief when NVIDIA didn't send Titan Xp to press (yes, of course new architecture is different thing, but still no-one even shrugged at that)
Well... which is worse for AMD? Bad benchmarks or a month delay with (hopefully) good or at least better benchmarks?Then they'd miss the H1 2017 release goal.
I could be wrong, but I thought that the prefetch length increases from 2n to 4n in pseudo channel mode for HBM2. So it's still 32 bytes.HBM2 does support Pseudo-Channels, if utilized one ca have 16 byte access granularity.
Pascal was already proven at that point. Who knows what's the state of Vega exactly is. A press briefing would have done wonders for damage control.Funny how there wasn't such chaos and grief when NVIDIA didn't send Titan Xp to press (yes, of course new architecture is different thing, but still no-one even shrugged at that)
Then, release it when it's ready?
That's the thing: this is the month delay.Well... which is worse for AMD? Bad benchmarks or a month delay with (hopefully) good or at least better benchmarks?
Well... which is worse for AMD? Bad benchmarks or a month delay with (hopefully) good or at least better benchmarks?
Those are forward looking statements. Schedule slips are a fact of life. Unless AMD provably misled investors, there'd be no repercussions at all.As written above, that would mean failing the H1 2017 release window which could mean significant repercussions from investors.
You are right, I didn't looked at the prefetch lenght.I could be wrong, but I thought that the prefetch length increases from 2n to 4n in pseudo channel mode for HBM2. So it's still 32 bytes.
Results from the 3DMark Fire strike, as of now is on level of 1080. I have dig on the drivers as they are not showing correctly and I've downloaded correct package from AMD but I've used half pro and game drivers now I will use just the gaming ones to see the difference.