Skip to content

Commit 9dfefef

Browse files
authored
[0041] Spec precision of TriangleObjectPositions returned position (#788)
Spec update to address: #697
1 parent 932ba5f commit 9dfefef

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

proposals/0041-triangle-object-positions.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,17 @@ triangle for a hit. The hit is the current hit inside an
139139
the candidate or committed hit state of a RayQuery object, or the
140140
committed hit state of a HitObject.
141141

142+
Returned position values exactly match what the user provided as input
143+
during acceleration structure build, albeit as float32 regardless of what
144+
the input vertex format was (potentially lower precision).
145+
146+
The exception is if the user includes a nonidentity transform along with
147+
input positions at build, which the driver immediately applies to those
148+
positions before storing them in the acceleration structure. In this case
149+
the position values in the acceleration structure, and thus what
150+
`TriangleObjectPositions` returns, may not exactly match the values the user
151+
would get if they tried transforming their input positions manually.
152+
142153
May only be used if the hit BLAS was built with
143154
`D3D12_RAYTRACING_ACCELERATION_STRUCTURE_BUILD_FLAG_ALLOW_DATA_ACCESS`
144155
(See [build flags defined here][dxr-build-flags]),

0 commit comments

Comments
 (0)