Overclock.net - An Overclocking Community - Reply to Topic
Thread: [TPU] Microsoft Details DXR Tier 1.1, New DirectX 12 Features Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
11-04-2019 12:26 AM
zGunBLADEz
Quote: Originally Posted by skupples View Post
the new norm for sub 4K users

hopefully ampere ushers in 4K120 days.
that should require a uplift boost between 75-120% over an 2080 Ti just for that just for current games (the typical 25-30% would not cut it lol) that do over 60 on a 2080 ti already lets say 70-80fps
2080 ti cant do 4k 60 in a good amount of games with everything cranked up.. and this is without RT activated lol

RT still a niche feature and would still be in the next 5yr so +
10-31-2019 07:22 AM
EastCoast Humus has been around for a long time and seems to always be on the bleeding edge of AMD/Nvidia API. Read what he thinks about it.

https://twitter.com/_Humus_/status/1173326963391569920

Quote:
I have updated the Metaballs2 demo with a compute path, allowing it to run on GPUs without mesh shader support. Final results for performance is that it's pretty much a wash between mesh shader and compute. Compute needs intermediate memory though.
Quote:
Compute shader gets ahead at very high grid density, whereas mesh shader gets a clear win at lower density. The reason for this is unclear to me, intuitively I was expecting the reverse if any difference emerged at all, i.e. more geometry to dump out -> slower for compute.
This looks like the difference between how games are on console (AMD) and Nvidia use of it.

Quote:
Currently the compute shader operates very similarly to the mesh shader path, with a task-shader equivalent pass first followed by a mesh-shader equivalent pass. In both implementations, the task shader part seems to be the most expensive.
DXR 1.1 is looking more and more very proprietary in hardware in order for it to work.

Mesh Shader = Nvidia
Compute = AMD (I assume).
10-31-2019 07:16 AM
skupples
10-31-2019 07:09 AM
EastCoast
Quote: Originally Posted by NightAntilli View Post
I'm not going to pretend to know what the latter two mean, nor what its implications are. I only hope that they are neutral and not catering to specific hardware vendors.
From what I've found this is catering to Nvidia's Mesh shaders.
https://devblogs.nvidia.com/introduc...-mesh-shaders/
That's dated Sept. 2018.





I've not found any technical documents from AMD/Radeon about mesh shaders. If someone finds any presentations/Demo from AMD about MS please link me. From what I understood AMD is doing something similar through next gen generation geometry (NGG). It's a unification of:
-vertex
-hull
-domain
-geometry
into surface shader(s) which have control over tessellation and geometry LOD. But I'm going on memory (I'm sure I missed something). And it's not clear to me if this is in the December 2019 performance update for Navi or if this is in RDNA 2.0.

However, as I said before, AMD has their own patent idea for RT. MS is catering to both.
10-30-2019 06:06 PM
skupples
Quote: Originally Posted by NightAntilli View Post
I'm not going to pretend to know what the latter two mean, nor what its implications are. I only hope that they are neutral and not catering to specific hardware vendors.
this is an expansion of the ray tracing libraries used in directX, the root coding at the base of 99% of PC games. This is technically "hardware agnostic"

In 5 years we'll be like "lulz, lets' load up the dx11 emulator n play some old games"


edit : i guess i can only cater to NV when they're the only ones actually messing with RT on PC atm.
10-30-2019 05:45 PM
NightAntilli I'm not going to pretend to know what the latter two mean, nor what its implications are. I only hope that they are neutral and not catering to specific hardware vendors.
10-30-2019 04:42 PM
skupples yep, I'm seeing way less hate than usual for the new consoles. Though I don't spend much time on reddit where I'm sure the shills have had many epic battles over the topic. I'm trying to hold out for the flagships that come AFTER the consoles drop. Not the last few cards running up to the console drops that're the last cash grabs of a generation. Unfortunately though, I had to grab a 5700xt to hold me over due to my 1080ti's being fubar

either way, when was the last time a console actually forced PC to do anything? This time around its forcing HDMI 2.1
10-30-2019 03:25 PM
EastCoast
Quote: Originally Posted by skupples View Post
the new norm for sub 4K users

hopefully ampere ushers in 4K120 days.
With next gen consoles offering 4k/1440p/HDR/RT along with 8cores/16 threads (along with kb/mouse support now) I know I won't be alone going that route next year for all those juice games I want. By the time I reach the price of just an ampere card I would have a console and several games.
10-30-2019 03:22 PM
skupples the new norm for sub 4K users

hopefully ampere ushers in 4K120 days.
10-30-2019 03:17 PM
drewafx Wish there was an option to turn on ray-tracing on main objects and keep traditional rendering on unnoticeable background. 120fps is the new norm, so 4k60f for eye candy replay/highlight/cinematics and 3440x1440x120f for gameplay would be preferred...
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off