Skip to content
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.

vkreplay: can't replay a trace made at the same resolution as the monitor #3

Open
johnzupin opened this issue Jul 19, 2018 · 2 comments
Assignees

Comments

@johnzupin
Copy link
Contributor

My monitor is set at 1920x1080 and when I create a trace of a game at that resolution and try to replay it, I receive the error:

Errors: bad window size, aborting!
Errors: bad window size, aborting!

When I create a trace of a game below 1920x1080 resolution the replay works fine.

@davidlunarg
Copy link
Collaborator

Re-opening. This still does not work, although the bad window size error is no longer displayed. Instead get numerous errors from replay and the replay hangs.

@davidlunarg davidlunarg reopened this Jul 20, 2018
@erik-kz
Copy link

erik-kz commented Jul 20, 2018

The original motivation for adding that error was that with certain window managers, when vkreplay tries to set it's window size to the full size of the screen, the window manager will forcibly clamp it to a slightly smaller size (for example to avoid covering the clock / launcher bar, ect.). If this happens, the trace can't really be replayed as our surface is a different size than it was when the trace was taken.

I think most games use ICCCM to get a proper full screen window. It might be possible to have vkreplay query the size of the screen and do the same if it detects that the trace is using a surface of the same size.

Another alternative would be to use the OVERRIDE_REDIRECT flag when vkreplay's window is created, which would bypass the window manager completely. Maybe have this be a command line option?

@KarenGhavam-lunarG KarenGhavam-lunarG transferred this issue from LunarG/VulkanTools Jun 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants