I noticed the current package has some legacy stuff that is incompatible. I have been able to fix it with codex automatically on a short moment. But it would be good to update the original package as I can’t push my package edits to Cloud Build.
The Cesium Team is already working on it:
main ← unity6.5
opened 11:19AM - 17 Jul 26 UTC
## Description
Add support for Unity 6.5, while retaining compatibility with … Unity 6.3. In Unity `instanceIDs` have been replaced with an opaque `EntityId` which is actually a 64 bit integer. Our native code will use one or the other as appropriate.
Additionally, the `TreeView` classes now require templated versions, so their usage was updated.
## Issue number or link
#704
## Author checklist
- [X] I have submitted a [Contributor License Agreement](https://github.com/CesiumGS/community/tree/main/CLAs) (only needed once).
- [X] I have done a full self-review of my code.
- [ X I have updated `CHANGES.md` with a short summary of my change (for user-facing changes).
- [ ] I have added or updated unit tests to ensure consistent code coverage as necessary.
- [ ] I have updated the documentation as necessary.
## Remaining Tasks
Test with Unity 6.5 in GitHub CI?
## Testing plan
Gave it a spin with Unity 6.3 and 6.5.
## Reviewer checklist
Thank you for taking the time to review this PR. By approving a PR you are taking as much responsibility for these changes as the author.
As you review, please go through the checklist below:
- [ ] Review and run all parts of the test plan on this branch and verify it matches expectations.
- [ ] If the issue is a bug please make sure you can reproduce the bug in the main branch and then checkout this branch to make sure it actually solved the issue.
- [ ] Review the code and make sure you do not have any remaining questions or concerns. You should understand the code change and the chosen approach. If you are not confident or have doubts about the code, please do not hesitate to ask questions.
- [ ] Code should follow the [C++ Style Guide](https://cesium.com/learn/cesium-native/ref-doc/style-guide.html)
- [ ] Review the unit tests and make sure there are no missing tests or edge cases.
- [ ] Review documentation changes and updates to `CHANGES.md` to make sure they accurately cover the work in this PR.
- [ ] Verify that the [Contributor License Agreement](https://github.com/CesiumGS/community/tree/main/CLAs) has been submitted, if needed.
Jake
July 30, 2026, 3:38pm
4
Hey @quizcanners - can you specify what “legacy stuff” is blocking you and incompatible? I can make sure that’s investigated as we work on support for Unity 6.5.
The PR referred to by @hv_nico above is slated to be in the upcoming August release. Some of the problems introduced by 6.5 are quite subtle, as you can see by the commit log. Do let us know of any ongoing problems with 6.5 after the release.