Repository navigation
fix(pool): restore table interaction after invalid physics option - #144
Merged
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
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.
The live client reported
local model/transform refused: invalid_physicsimmediately after the pool update. The renderer passedphysics = false, but Open77's prop definition accepts a string enum (static,kinematic,dynamic,none). The model failure latched the table unavailable and hid its ALT interaction.Use
physics = "none"while retaining collision=false and visible=true. Update the enabled-client native double to enforce the actual enum before rendering, so a boolean cannot pass the regression scenario again. Correct the operator manual.Validation: real enabled-client lifecycle regression passes, including prop creation, camera/input cleanup and render reuse; diff checks clean. The live server log establishes the native refusal. Fresh client activation is required to clear the previous latched renderer failure. Actual in-game interaction still needs the user retest.
Follow-up to #142 and #140; documentation tracked in opx77-framework/opx77_doc#19.