Skip to content

Vfx/fix/1327623 vfx recompiles for no change #5518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Sep 13, 2021

Conversation

julienamsellem
Copy link
Contributor

Purpose of this PR

https://fogbugz.unity3d.com/f/cases/1327623/

When clicking on a block value but without changing the value the vfx was always recompiling
RXg6AJ8yXs


Testing status

Tested on the Capacity property


Comments to reviewers

Notes for the reviewers you have assigned.

It was resulting in always recompiling the vfx even if the value had not changed
@github-actions
Copy link

github-actions bot commented Sep 2, 2021

Hi! This comment will help you figure out which jobs to run before merging your PR. The suggestions are dynamic based on what files you have changed.
Link to Yamato: https://yamato.cds.internal.unity3d.com/jobs/902-Graphics
Search for your PR branch using the sidebar on the left, then add the following segment(s) to the end of the URL (you may need multiple tabs depending on how many packages you change)

VFX
/.yamato%252Fall-vfx.yml%2523PR_VFX_trunk

Depending on the scope of your PR, you may need to run more jobs than what has been suggested. Please speak to your lead or a Graphics SDET (#devs-graphics-automation) if you are unsure.

Copy link

@VitaVFX VitaVFX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skipping QA pass as change is minor🟢

@julienamsellem julienamsellem marked this pull request as ready for review September 3, 2021 07:42
@@ -327,7 +327,7 @@ private bool SetSettingValueAndReturnIfChanged(string name, object value)
}

var currentValue = setting.value;
if (currentValue != value)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The variables are of type object which leads to reference comparison instead of value comparison.

Copy link
Contributor

@PaulDemeulenaere PaulDemeulenaere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Your branch doesn't include this fix #5512
it explain this failure.
28_FlipBookArray
28_FlipBookArray expected

I'm more interested in test result in VFX_HDRP edit mode : https://unity-ci.cds.internal.unity3d.com/job/8629702

Can you relaunch yamato after master merge (there is a known issue in edit mode https://unity.slack.com/archives/G1BTWN88Z/p1630664424058600?thread_ts=1630664357.058500&cid=G1BTWN88Z)

@julienamsellem julienamsellem merged commit 769db8c into master Sep 13, 2021
@julienamsellem julienamsellem deleted the vfx/fix/1327623-vfx-recompiles-for-no-change branch September 13, 2021 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants