Changes between Version 3 and Version 4 of Ticket #16865, comment 4


Ignore:
Timestamp:
Mar 14, 2025, 5:12:45 PM (9 months ago)
Author:
Tom Goddard

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16865, comment 4

    v3 v4  
    1313
    1414More debug output shows the swapchain image count is always 3 and the swapchain index is always 0,1, or 2.  But the texture ids keep rising on every render.  I use a separate swapchain for each eye.  Maybe that is the issue, switching between swapchains may be where Acer OpenXR goes haywire.  Maybe it is only implemented to work efficiently with one swapchain.  I changed the code to use just one swapchain and it still increases the texture ids on every render and wipes out in the same way with the memory errors.
     15
     16The Acer example OpenXR code uses a single swapchain. There is some alarming code in my _create_swapchains() routine that adds the swapchain images to a list with a comment saying it is to keep the images alive.  That list is never used by saved as an attribute.  But it seems as if a deallocation was happening in Python that led to the textures being recreated it would happen on the Sony display too.  It would be useful to know if the Acer example code keeps creating new textures.  That would be some work to compile the C++ on Windows.