Skip to content

Fixes for API deprecation warnings when using plugin in Unity 6.4 #1714

Open
MaxPalmer-UH wants to merge 4 commits into
developfrom
mjp/fix_unity64_obsolete_warnings
Open

Fixes for API deprecation warnings when using plugin in Unity 6.4 #1714
MaxPalmer-UH wants to merge 4 commits into
developfrom
mjp/fix_unity64_obsolete_warnings

Conversation

@MaxPalmer-UH

Copy link
Copy Markdown
Collaborator

Fixes several warnings when importing the plugin in Unity 6.4

@rblenkinsopp

Copy link
Copy Markdown
Member

The code changes all look good, have you checked that the .meta file changes increase in serializedVersion don't mean they have issues importing in older but still supported versions?

@MaxPalmer-UH

Copy link
Copy Markdown
Collaborator Author

The code changes all look good, have you checked that the .meta file changes increase in serializedVersion don't mean they have issues importing in older but still supported versions?

No, that's a good shout. There will likely be issues there.

@rblenkinsopp rblenkinsopp left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good but check that serialised assets and it needs a changelog entry as well.

@MaxPalmer-UH

Copy link
Copy Markdown
Collaborator Author

Just checked importing the plugin in Unity 6.0, seemed to work fine and not show any warnings related to meta files or those components. Also added a changeling entry.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants