Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've been using something similar to this in tpksp for years. Calling the event directly can spew nullrefs and softlock you out of buildings.
My initial fix was to add a component that fires the event in LateUpdate, but this also works and is simpler (tested on my stream).
I suspect the issue occurs because the event is normally fired from the stock ui code which runs late in the frame.
for reference, I originally hit this in RPM with the vessel recovery prop. This is the code I’d been using in tpksp as well: https://github.com/JonnyOThan/RasterPropMonitor/blob/958720c1d9ad2145cacf5f5098d8984682f5e00e/RasterPropMonitor/Core/JSIVesselRecovery.cs#L27