Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

8134 post processing settings are not reactive #8262

Merged
merged 13 commits into from
Jul 13, 2023

Conversation

SYBIOTE
Copy link
Member

@SYBIOTE SYBIOTE commented Jul 11, 2023

Summary

the effects were being sourced from the global state -> PostProcessingeffectsstate, but we were not setting the state anywhere, therefore its always the default
i replaced the source with the PostProcessingComponent instead, it works now

References

closes #insert number here

Checklist

  • If this PR is still a WIP, convert to a draft
  • When this PR is ready, mark it as "Ready for review"
  • ensure all checks pass
  • Changes have been manually QA'd
  • Changes reviewed by at least 2 approved reviewer

QA Steps

List any additional steps required to QA the changes of this PR, as well as any supplemental images or videos.

@SYBIOTE SYBIOTE linked an issue Jul 11, 2023 that may be closed by this pull request
@SYBIOTE SYBIOTE requested a review from speigg July 11, 2023 14:44
@SYBIOTE
Copy link
Member Author

SYBIOTE commented Jul 11, 2023

@SYBIOTE
Copy link
Member Author

SYBIOTE commented Jul 11, 2023

the other are working accordingly as well

…into 8134-post-processing-settings-are-not-reactive
@HexaField HexaField self-requested a review July 13, 2023 23:01
@HexaField HexaField added this pull request to the merge queue Jul 13, 2023
Merged via the queue into dev with commit 57f82ae Jul 13, 2023
@HexaField HexaField deleted the 8134-post-processing-settings-are-not-reactive branch July 13, 2023 23:01
@SYBIOTE
Copy link
Member Author

SYBIOTE commented Aug 2, 2023

oh this was resolved? im closing the issue then

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Post Processing Settings are not Reactive
2 participants