Fix failing navmesh for static meshes #2367
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
#2326
Types of changes
Checklist