Skip to content
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

[spine-unity] Fix for the issue [2346] causing canvasRenderers and submeshGraphics to get unsynced #2478

Closed

Conversation

sandolkakos
Copy link
Contributor

@sandolkakos sandolkakos commented Mar 8, 2024

Fix for the issue 2346 causing canvasRenderers and submeshGraphics to get unsynced and throwing null exception reference at:

SkeletonSubmeshGraphic submeshGraphic = submeshGraphics[i];

@HaraldCsaszar
Copy link
Collaborator

@sandolkakos Thanks for the pull request! Unfortunately we have to decline it this time since SyncSubmeshGraphicsWithCanvasRenderers is not intended to be called every frame, as we want to avoid calling canvasRenderer.GetComponent<SkeletonSubmeshGraphic>(); that frequently.

It would be great to know why canvasRenderers and submeshGraphics can get out of sync, then we could provide a more cost-efficient bugfix.

@sandolkakos
Copy link
Contributor Author

sandolkakos commented Mar 27, 2024

@sandolkakos Thanks for the pull request! Unfortunately we have to decline it this time since SyncSubmeshGraphicsWithCanvasRenderers is not intended to be called every frame, as we want to avoid calling canvasRenderer.GetComponent<SkeletonSubmeshGraphic>(); that frequently.

It would be great to know why canvasRenderers and submeshGraphics can get out of sync, then we could provide a more cost-efficient bugfix.

Ohh I see. Fair enough, I haven't checked it was called from Update! 😅
I will try to find a time on the next weeks to see if I can find the reason for both arrays getting out of sync in our project.

@HaraldCsaszar
Copy link
Collaborator

@sandolkakos Thanks very much for your understanding and for all your efforts! :)

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

Successfully merging this pull request may close these issues.

None yet

2 participants