Overclock.net › Forums › Industry News › Video Game News › [WCCF] HITMAN To Feature Best Implementation Of DX12 Async Compute Yet, Says AMD
New Posts  All Forums:Forum Nav:

[WCCF] HITMAN To Feature Best Implementation Of DX12 Async Compute Yet, Says AMD - Page 38

post #371 of 799
Quote:
Originally Posted by Defoler View Post

Even though nvidia can only implement the queue it in drivers right now, the actual compute is done on their GPU just like with AMD.
Since the last drivers fix from nvidia for ashes to actually implement it, we have seen nvidia being just as competitive on it.
This is not true. The driver only brought nVidia's performance of DX12 up to DX11 level, since DX11 was faster in the earlier versions.

nVidia's current hardware cannot do concurrent graphics + compute asynchronously, while AMD's can. This has been tested extensively.
post #372 of 799
Yeah I did quick search jut to be sure but if Nvidia would have enabled A-sync in AotS logically all sites would have benchmarked it and would have talked about it, but nothing. Also I haven't seen an nvidia driver that mentions they have enabled that feature in AotS.
post #373 of 799
Quote:
Originally Posted by spyshagg View Post

I understand your point, but because benchmarks and analysis and conclusions were made based on that version, the graphical discrepancy matters in that point in time.



I don't know how it went unnoticed. People are not looking at image quality anymore. No one expects mistakes from the past (lowering image quality) to be made again in 2015, but they were and we should be aware for our own good.



Losing a company such as AMD to this type of dishonesty would be criminal and everybody's loss.


you don't have to answer but what do you mean?

that game is not even out yet its beta for all we know a lot of graphics might be cut out to make it easier to run.
how many times has a game dev done this like a million times...I am not saying that game will but I would not put it passed any game maker in this day and age.
that game does not run too well on anything anyways by just the looks of higher rez benches
post #374 of 799
Quote:
Originally Posted by Defoler View Post

Quote:
Originally Posted by KyadCK View Post

Soooooo you just hate efficiency then? It really isn't an AMD only thing forever, it just is for now.

Even though nvidia can only implement the queue it in drivers right now, the actual compute is done on their GPU just like with AMD.
Since the last drivers fix from nvidia for ashes to actually implement it, we have seen nvidia being just as competitive on it.

With more CPU load that doesn't need to exist, and with pausing the GPU to do them, and with one of the lightest ASync loads. This very thread is about it being used more.
Quote:
Originally Posted by Kand View Post

Quote:
Originally Posted by KyadCK View Post

Soooooo you just hate efficiency then? It really isn't an AMD only thing forever, it just is for now.

Windows 10. Actually.

So other APIs do not exist? Apple's Metal, Vulkan?

Huh. I've been edumakated.
Quote:
Originally Posted by Serios View Post

Quote:
Originally Posted by Defoler View Post

Even though nvidia can only implement the queue it in drivers right now, the actual compute is done on their GPU just like with AMD.
Since the last drivers fix from nvidia for ashes to actually implement it, we have seen nvidia being just as competitive on it.
I've seen no mention of that, you are just assuming.

The new driver allows them to be capable of accepting the DX12 command associated with using them.

It then proceeds to half-ass it on the CPU, load it into the queue at the driver level, pause the GPU, context switch, process it, and context switch back to graphical load.

It's a typical software solution for a hardware problem until they add the hardware.
Quote:
Originally Posted by NightAntilli View Post

Quote:
Originally Posted by Defoler View Post

Even though nvidia can only implement the queue it in drivers right now, the actual compute is done on their GPU just like with AMD.
Since the last drivers fix from nvidia for ashes to actually implement it, we have seen nvidia being just as competitive on it.
This is not true. The driver only brought nVidia's performance of DX12 up to DX11 level, since DX11 was faster in the earlier versions.

nVidia's current hardware cannot do concurrent graphics + compute asynchronously, while AMD's can. This has been tested extensively.

^ That.
Forge
(17 items)
 
Forge-LT
(7 items)
 
 
CPUMotherboardGraphicsGraphics
Intel i7-5960X (4.625Ghz) ASUS X99-DELUXE/U3.1 EVGA 1080ti SC2 Hybrid EVGA 1080ti SC2 Hybrid 
RAMHard DriveCoolingOS
64GB Corsair Dominator Platinum (3000Mhz 8x8GB) Samsung 950 Pro NVMe 512GB EK Predator 240 Windows 10 Enterprise x64 
MonitorKeyboardPowerCase
2x Acer XR341CK Corsair Vengeance K70 RGB Corsair AX1200 Corsair Graphite 780T 
MouseAudioAudioAudio
Corsair Vengeance M65 RGB Sennheiser HD700 Sound Blaster AE-5 Audio Technica AT4040 
Audio
30ART Mic Tube Amp 
CPUMotherboardGraphicsRAM
i7-4720HQ UX501JW-UB71T GTX 960m 16GB 1600 9-9-9-27 
Hard DriveOSMonitor
512GB PCI-e SSD Windows 10 Pro 4k IPS 
  hide details  
Reply
Forge
(17 items)
 
Forge-LT
(7 items)
 
 
CPUMotherboardGraphicsGraphics
Intel i7-5960X (4.625Ghz) ASUS X99-DELUXE/U3.1 EVGA 1080ti SC2 Hybrid EVGA 1080ti SC2 Hybrid 
RAMHard DriveCoolingOS
64GB Corsair Dominator Platinum (3000Mhz 8x8GB) Samsung 950 Pro NVMe 512GB EK Predator 240 Windows 10 Enterprise x64 
MonitorKeyboardPowerCase
2x Acer XR341CK Corsair Vengeance K70 RGB Corsair AX1200 Corsair Graphite 780T 
MouseAudioAudioAudio
Corsair Vengeance M65 RGB Sennheiser HD700 Sound Blaster AE-5 Audio Technica AT4040 
Audio
30ART Mic Tube Amp 
CPUMotherboardGraphicsRAM
i7-4720HQ UX501JW-UB71T GTX 960m 16GB 1600 9-9-9-27 
Hard DriveOSMonitor
512GB PCI-e SSD Windows 10 Pro 4k IPS 
  hide details  
Reply
post #375 of 799
Quote:
Originally Posted by cowie View Post

you don't have to answer but what do you mean?

Hi

AMD is in a fragile position without there being a good reason for it. Their graphics cards performance should warrant a much stronger market position. Yet its not happening. Why?
Market perception perhaps. And this market is easily swayed by reviews opinions etc, as it should! but it seems that every time AMD market perception is brought down, nvidia as finger on it. And they are willing to go dirty big time. Gameworks was a stroke of genius. Its nothing but a cancer, but its being spread as a cure for games for the benefit of gamers. And by gamers I mean everyone who buys their currently available hardware, not their 2 year old hardware. And now, we have async. A dx12 spec feature in its own right. Capable of providing double digits performance gains when supported. Maxwell cant do it natively, so what do they do? fix the game with drivers! as it turns out, image quality was brought down and nobody noticed when it mattered. But that is OK!!! Its OK because performance reviews and articles were already written! the market was already swayed when it mattered. The resulting perception? = nvidia only needed drivers! its async performance is on PAR with AMD. Job done nvidia.

Only our money can keep companies honest. spend it on fallacies tricks and dishonesty and soon this will be the only choice on the market.
post #376 of 799
Quote:
Originally Posted by KyadCK View Post

With more CPU load that doesn't need to exist, and with pausing the GPU to do them, and with one of the lightest ASync loads. This very thread is about it being used more.
So other APIs do not exist? Apple's Metal, Vulkan?

Huh. I've been edumakated.
The new driver allows them to be capable of accepting the DX12 command associated with using them.

It then proceeds to half-ass it on the CPU, load it into the queue at the driver level, pause the GPU, context switch, process it, and context switch back to graphical load.

It's a typical software solution for a hardware problem until they add the hardware.
^ That.

Async compute is currently forcibly disabled on public builds of Ashes for NV hardware. Whatever performance changes you are seeing driver to driver doesn't have anything to do with async compute.
post #377 of 799
Quote:
Originally Posted by Kollock View Post

Async compute is currently forcibly disabled on public builds of Ashes for NV hardware. Whatever performance changes you are seeing driver to driver doesn't have anything to do with async compute.

Does NV hardware support Async compute?
post #378 of 799
Quote:
Originally Posted by escksu View Post

Does NV hardware support Async compute?
probably not at same level as AMD does.
post #379 of 799
Quote:
Originally Posted by escksu View Post

Does NV hardware support Async compute?
Rhetorical question, right?
Lil' Roy Taylor
(11 items)
 
  
Reply
Lil' Roy Taylor
(11 items)
 
  
Reply
post #380 of 799
Quote:
Originally Posted by KyadCK View Post

With more CPU load that doesn't need to exist, and with pausing the GPU to do them, and with one of the lightest ASync loads. This very thread is about it being used more.
So other APIs do not exist? Apple's Metal, Vulkan?

Huh. I've been edumakated.
The new driver allows them to be capable of accepting the DX12 command associated with using them.

It then proceeds to half-ass it on the CPU, load it into the queue at the driver level, pause the GPU, context switch, process it, and context switch back to graphical load.

It's a typical software solution for a hardware problem until they add the hardware.
^ That.

Async compute is currently forcibly disabled on public builds of Ashes for NV hardware. Whatever performance changes you are seeing driver to driver doesn't have anything to do with async compute.
Quote:
Originally Posted by escksu View Post

Does NV hardware support Async compute?

I can confirm that the latest shipping DX12 drivers from NV do support async compute. You'd have to ask NV how specifically it is implemented.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Video Game News
Overclock.net › Forums › Industry News › Video Game News › [WCCF] HITMAN To Feature Best Implementation Of DX12 Async Compute Yet, Says AMD