Support the extension VK_QCOM_multiview_per_view_viewports about renderdoc HOT 5 OPEN

You seem to have entangled different issues here. First there is the question of supporting a new extension, but you're saying that if the extension isn't supported then there is a bug in the display of multiple viewports or scissors?

Please open a separate issue for a bug like that and leave this issue only for requesting support of a new extension.

from renderdoc.

Ok, I've removed the bug fix from the request and changed it to just refer to the extension + overlay support change.

from renderdoc.

If there's a bug to report then please file an issue for it and provide steps to reproduce the problem. That is higher priority than a feature request for a new extension, and a bug in the existing code will not get fixed by implementing a new extension.

from renderdoc.

I will, but I'm first trying to confirm with the person who implemented the extension in the engine to make sure that this is a genuine RenderDoc bug and not something that occurred because of the engine's behavior if the extension is not enabled. I have 2 implementations I'm working with and on Unreal Engine I'm not seeing the bug, only on Unity, so it may be a failure on that side to handle the extension not being supported.

What I am getting regardless is only 1 viewport/scissor being submitted, hence the feature request.

from renderdoc.

I've received confirmation that the bug is not a RenderDoc bug, instead being a Unity issue where a part of the pipeline is unable to determine whether the extension was enabled or not and is defaulting to enabled in my sample, causing the frame submissions to be incorrect if the extension is disabled.

The only request is feature enablement to support viewing the correct viewport/scissor regions for each view and an overlay update to likewise display the correct region for each view.

from renderdoc.