You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In OpenXR, there are several structures that are filled in by various API calls that require some initialization before being passed in. The initialization includes, setting values appropriately (beyond type and next) such as counts and array memory allocations. These should be handled automatically in code gen.
Currently there are two locations that need to be code generated appropriately:
The API call itself which handles such a structure
This includes at least the following APIs that are hand generated right now in openxr_replay_consumer_base.cpp (prepended with Process_):
xrLocateSpaces
xrLocateHandJointsEXT
xrGetMeshFB
xrLocateBodyJointsEXT
next chain structures that are handled in such a wa:
This includes at least the following structures that are hand generated right now in openxr_replay_consumer_base.cpp (prepended with OverrideOutputStructNext_):
XrSpaceVelocities
XrHandJointVelocitiesEXT
The text was updated successfully, but these errors were encountered:
MarkY-LunarG
changed the title
Handle input/output structures automatically in codegen
[openxr] Handle input/output structures automatically in codegen
Sep 5, 2024
In OpenXR, there are several structures that are filled in by various API calls that require some initialization before being passed in. The initialization includes, setting values appropriately (beyond
type
andnext
) such as counts and array memory allocations. These should be handled automatically in code gen.Currently there are two locations that need to be code generated appropriately:
openxr_replay_consumer_base.cpp
(prepended withProcess_
):next
chain structures that are handled in such a wa:openxr_replay_consumer_base.cpp
(prepended withOverrideOutputStructNext_
):The text was updated successfully, but these errors were encountered: