Fix INSTANCE_CUSTOM.w not being assigned correctly in CPUParticles 2D and 3D
#90095
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AThousandShips
changed the title
akien-mga
changed the title
INSTANCE_CUSTOM.w not being assigned correctly in CPUParticles 2D and 3D
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes an issue with CPUParticles not assigning and using INSTANCE_CUSTOM.w in the same way as GPUParticles, causing any shader that correctly uses lifetime (
INSTANCE_CUSTOM.y/INSTANCE_CUSTOM.w) to misbehave when assigned to CPUParticles from GPUParticles.There's no issue coupled to this because it came out of a troubleshooting conversation on discord that turned into a bug report.
CPU_Particles_Instance_Custom_MRP.zip