This repository was archived by the owner on Feb 3, 2025. It is now read-only.
LensFlare: initialize OGRE compositors during plugin initialization #2764
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.
There are several
SensorPlugin
s that create Ogre compositors (such as LensFlareSensorPlugin). It was reported by @mogumbo that the order in which compositors are applied affects the rendered output, but theLensFlareSensorPlugin
always seems to be applied last, regardless of the order in which plugins are specified in an SDFormat file. @iche033 suggested moving the code for initializing agazebo::rendering::LensFlare
compositor fromLensFlare::Update
toLensflare::SetCamera
, so that the compositor would be added during plugin initialization.The initialization code expects a pointer to a
DirectionalLight
, which is not available until the first render update. It seems to work to initialize with anullptr
for theDirectionalLight
since the light ptr is being set every update. I also added logic to exitnotifyMaterialRender
early if the light pointer isnullptr
.