Skip to content

SER: Possible HitObjectAttribute divergence from DX #373

@dgkoch

Description

@dgkoch

Re

'Hit Object Attributes' contains the attributes of the hit which are to be encoded in 'Hit Object'. This must be an OpVariable in *HitObjectAttributeEXT* storage class. +

This currently differs from DX as it says that we always store attributes, even for triangle hits, is this intentional?

The DX SER doc says:

An overload takes a user-defined hit kind and custom attributes associated with COMMITTED_PROCEDURAL_PRIMITIVE_HIT. It is ok to always use the overload, even for COMMITTED_TRIANGLE_HIT. For anything other than a procedural hit, the specified hit kind and attributes are ignored.

Originally posted by @Flakebi in #368 (comment)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions