fix(multi-client): Prevent duplicate lights when multiple clients connect #250
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.
Problem Summary:
Issue: Light intensity accumulation with multiple client connections
Description: When multiple web clients connect to the same gzbridge instance, the existing client's scene becomes progressively brighter with each new client connection.
Symptoms:
Root Cause: The
initScene()function in gzscene.js creates a new sun light on every client initialization without checking if lights already exist, causing duplicate light sources to accumulate in the shared THREE.js scene.Impact: Visual degradation where scenes become unnaturally bright as more clients connect, making the simulation unusable for existing clients.
Reproduction: