stride
stride copied to clipboard
Fix failing navmesh for static meshes
PR Details
There seems to be a common error that I think comes from GameStudio. This error makes references not available when processors attempt to reference them in code.
This is a band-aid fix that should resolve issues with reading static mesh data that's not available.
A bit of added info, this seems to only affect procedural meshes.. not sure why that would be.
Related Issue
https://github.com/stride3d/stride/issues/2326
Types of changes
- [ ] Docs change / refactoring / dependency upgrade
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
- [ ] My change requires a change to the documentation.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
- [x] I have built and run the editor to try this change out.
Some more research may be needed here. This got rid of the first hurdle but now it seems to crash when a second static mesh collider is added.
Cool, I'll mark this as wip then