search

o3de / sig-graphics-audio

Documents and communications for the O3DE Graphics-Audio Special Interest Group
12 stars 14 forks source link

Proposed SIG-Graphics-Audio meeting agenda for September-21-22 #61

Open galibzon opened 2 years ago

galibzon commented 2 years ago

Meeting Details

The SIG-Graphics-Audio Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

What happened since the last meeting?

Meeting Agenda

Discuss agenda from proposed topics

Outcomes from Discussion topics

Discuss outcomes from agenda

Action Items

Create actionable items from proposed topics

Open Discussion Items

List any additional items below!

santorac commented 2 years ago

Let's consider this RFC for final approval: https://github.com/o3de/sig-graphics-audio/issues/68

santorac commented 2 years ago

Here is a new RFC for discussion: https://github.com/o3de/sig-graphics-audio/issues/74

santorac commented 2 years ago

Discuss https://github.com/o3de/o3de/issues/12027 for awareness.

santorac commented 2 years ago

I propose we use the wiki to publish RFC's instead of GitHub Issues so that revision history can be use to track changes to a proposal. (Or should write an RFC about this? :D)

kh-huawei commented 2 years ago

I would like to put the Upgrade to HLSL Shader Model 6.6 back on the agenda, since i should be able to take part in the meeting today

thefranke commented 2 years ago

Transfer of rights for @adiblev in issue #75

kh-huawei commented 2 years ago

Jenkins build issues of PR#12009 for awareness: Windows version too old?

ghost commented 2 years ago

I would like to put the Upgrade to HLSL Shader Model 6.6 back on the agenda, since i should be able to take part in the meeting today

Can you please specify the reasons to that?

kh-huawei commented 2 years ago

I would like to put the Upgrade to HLSL Shader Model 6.6 back on the agenda, since i should be able to take part in the meeting today

Can you please specify the reasons to that?

From the agenda of the August-24-22 Meeting:

From: K. Haubenwallner [Huawei]#0165
We need access to the 64bit atomic operations that were introduced with HLSL Shader Model 6.6, and i noticed that the Shader Model is hardcoded to 6.2 (and 6.3 for Raytracing), and that the dxcompiler has a custom o3de version 'release-1.6.2112-o3de'.
I now briefly tried to set the Shader Model to 6.6: initially this didn't work, because the dxil.dll is too old, but when i exchanged the entire dxc with the latest version from github (1.7.2207.3) this seemed to work without issue, at least on a first glance.

My question is now what am i missing there? Is it feasible to push for a default Shader Model 6.6, and to update the dxc?

And since that meeting has a comment that the issues will be moved to the meeting on 8/31/2022, but don't show up there, i'm assuming it wasn't on the agenda since then.

ghost commented 2 years ago

I would like to put the Upgrade to HLSL Shader Model 6.6 back on the agenda, since i should be able to take part in the meeting today

Can you please specify the reasons to that?

From the agenda of the August-24-22 Meeting:

From: K. Haubenwallner [Huawei]#0165
We need access to the 64bit atomic operations that were introduced with HLSL Shader Model 6.6, and i noticed that the Shader Model is hardcoded to 6.2 (and 6.3 for Raytracing), and that the dxcompiler has a custom o3de version 'release-1.6.2112-o3de'.
I now briefly tried to set the Shader Model to 6.6: initially this didn't work, because the dxil.dll is too old, but when i exchanged the entire dxc with the latest version from github (1.7.2207.3) this seemed to work without issue, at least on a first glance.

My question is now what am i missing there? Is it feasible to push for a default Shader Model 6.6, and to update the dxc?

And since that meeting has a comment that the issues will be moved to the meeting on 8/31/2022, but don't show up there, i'm assuming it wasn't on the agenda since then.

Awesome thank you for the reply. I was curious since we're going through the shader process ourselves and trying to wrap our heads around it. That clarifies things. I support the upgrade as well.