Skip to content

Fix --wsi auto behaviour#2736

Open
roman-berger-arm wants to merge 2 commits intoLunarG:devfrom
roman-berger-arm:fix-wsi
Open

Fix --wsi auto behaviour#2736
roman-berger-arm wants to merge 2 commits intoLunarG:devfrom
roman-berger-arm:fix-wsi

Conversation

@roman-berger-arm
Copy link

Before when replaying captures from a different device --wsi had to be specified explicitly and the --wsi auto options was ignored. Even when captures recorded on the same device were replayed the --wsi auto option was ignored and the surface from the capture device was chosen.

Now the --wsi auto option (already default behaviour) picks the surface extension from the capture device if it is available. Otherwise the first available surface extension of the replay device is used. If there was not surface extensions available on the capture device, all --wsi options are ignored and a warning is emitted. Furthermore, a check if a compositor is available is made after initializing the WSIContext.

Documentation and cli --help commands were updated to reflect these changes.

@roman-berger-arm roman-berger-arm requested a review from a team as a code owner February 27, 2026 13:29
@CLAassistant
Copy link

CLAassistant commented Feb 27, 2026

CLA assistant check
All committers have signed the CLA.

Before when replaying captures from a different device --wsi <WSI>
had to be specified explicitly and the --wsi auto options was ignored.
Even when captures recorded on the same device were replayed the
--wsi auto option was ignored and the surface from the capture device
was chosen.

Now the --wsi auto option (already default behaviour) picks the
surface extension from the capture device if it is available.
Otherwise the first available surface extension of the replay device
is used. If there was not surface extensions available on the capture
device, all --wsi options are ignored and a warning is emitted.
Furthermore, a check if a compositor is available is made after
initializing the WSIContext.

Documentation and cli --help commands were updated to reflect these
changes.

Change-Id: I578ee1f50a797ec81a9b48ab3ee4b4a9817a91bf
@fabian-lunarg fabian-lunarg added the approved-to-run-ci Can run CI check on internal LunarG machines label Mar 2, 2026
@fabian-lunarg fabian-lunarg self-assigned this Mar 2, 2026
@fabian-lunarg
Copy link
Contributor

investigating an issue our internal CI had with a replay of vulkaninfo ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-to-run-ci Can run CI check on internal LunarG machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants