Fixing a weird issue... #2
Open
Conversation
This file contains hidden or 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
…ached" bug on the Unity guts on the second time you switch scenes and foward.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…that was provoking a "Matrix stack full depth reached" bug on the Unity guts on the second time you switch scenes and forward.
The first time you load a vessel things works fine, but as soon as you switch back to KSC and launch anything else, the NavUtils throws a NRE with a lot of logs from Unity complaining about "Matrix stack full depth reached". The ILS doesn't shows, and the whole UI disappears as you were pressed F-2.
I never got into this before KSP 1.7.3, but the behaviour was consistent on my rig today. Researching about that Matrix stunt, I got to a page complaining about this happening on the Editor, and disappeared when an asset was restored on the file system - so I imagined that perhaps the Stop being applied when no sound was ever played before could be the reason, and apparently I was right.