Ensure PIPCamera maintains render state in NoDisplay #2518
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a bug with
"ViewMode": "NoDisplay"
where the FPV camera would disregard both intrinsic (e.g. auto exposure settings in json) and extrinsic (e.g. world postprocessing volume) render settings. PIPCamera blueprint now has thebAlwaysPersistRenderingState
flag turned on so the render state persists even when the main viewport render is disabled.Sample settings.json:
Sample script capture.py:
Steps to test:
"AutoExposureBias": 10
in settings).