Changes between Version 5 and Version 6 of Ticket #16865, comment 4


Ignore:
Timestamp:
Mar 14, 2025, 5:57:20 PM (7 months ago)
Author:
Tom Goddard

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16865, comment 4

    v5 v6  
    1616The 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.
    1717
    18 I see a possible critical difference with the Acer sample code.  It calls xrEnumerateSwapchainImages() only at initialization while my code calls it every frame.  Test if calling it only at initialization fixes the problem.
     18I see a possible critical difference with the Acer sample code.  It calls xrEnumerateSwapchainImages() only at initialization while my code calls it every frame.  Test if calling it only at initialization fixes the problem.  That does fix it.  Now ChimeraX renders correctly on the display using "Screen Mode" in Acer settings (Alt+C when in stereo).
     19
     20In "VR Mode" from Acer settings it kind of works but the depth is compressed depending on how far out of the screen I move the model.  It can look correct in VR Mode moved far in front of screen but looks flattened in depth if I try to move the model to be half in front and half in back of screen.  This probably can probably be figured out with reference to the Acer explanation of the camera views used in these two views and probably it can be fixed to work in either mode, although screen mode may be the preferred mode for ChimeraX viewing.