Recent content by doompc

Streaming systems usually deal with devices that are many orders of magnitude slower than RAM; ie mecanical or even optical drives. I guess it comes down to "schedule it far enough in advanced that it will be ready by the time you need the data". Other examples come to mind. The Far Cry guys...

Search for the DX12 implementation in The Division, they use 3 copy queues to manage texture streaming. https://developer.download.nvidia.com/assets/gameworks/downloads/regular/GDC17/DX12CaseStudies_GDC2017_FINAL.pdf

The Star War Reflections demo is built using DXR. RTX accelerates DXR but DXR can run on any DX12 GPU using the fallback layer.

The full Volta Whitepaper is out http://www.nvidia.com/object/volta-architecture-whitepaper.html

PresentMon is not as accurate as FCAT but works in a simular fashion, looking at the interval between the frames are presented. Until recently DX12 games on AMD (even Steam games, like Ashes) were forced into a borderless window mode, so no matter how many frames per second your game is running...

My guess is that the internal benchmark counts the frame to frame time at the begining of processing, not at the time the frame is presented (like presentmon).

Hi, first time posting here. Ashes uses async compute for post processing, so it immediately starts the next frame, but the "previous" one will only be presented when the post is done. from here...