Skip to content

Conversation

@byjtew
Copy link
Contributor

@byjtew byjtew commented Oct 1, 2025

Description

I that something you would be okay with ?
I simply find myself in a position where I have multiple overlapping scene captures and players, and this is the only way to properly disable them from being detected, without having to change my ASceneCapture2D to actors with a USceneCaptureComponent.

I am happy to fill the rest of this PR if you want me to.

Issue number or link

Author checklist

  • I have submitted a Contributor License Agreement (only needed once).
  • I have done a full self-review of my code.
  • I have updated CHANGES.md with a short summary of my change (for user-facing changes).
  • [ ] I have added or updated unit tests to ensure consistent code coverage as necessary
  • I have updated the documentation as necessary.

Remaining Tasks

Testing plan

@byjtew
Copy link
Contributor Author

byjtew commented Oct 3, 2025

I must mention that this PR exists only because having >1 cameras looking with the same configuration at the same location extends the updateViewGroup call durations by a huge amount.

@j9liu
Copy link
Contributor

j9liu commented Dec 4, 2025

Apologies for the delayed response to this, @byjtew. Thank you for opening this PR!

It's looking like our camera system needs deeper reworking (#1768), so we're going to see if we can develop a more generalized solution that also addresses this. But we'll keep this PR open in case we come around to it.

@byjtew
Copy link
Contributor Author

byjtew commented Dec 4, 2025

No worries, Ill keep an eye open for it

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants