secondlife / secondlife/viewer
Reflection Probes updating when crossing parcels sharing same EEP within same region, same parcel owner.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Reflection probes trigger an update every time you cross a parcel connected even when both parcels are using the same EEP setting and same large probe, that is disrupting, it should not trigger an update if both parcels are using the same EEP within the same region, same owner. It's very common in regions like Bay City, Nautilus (not limited to it... ), where we cannot merge parcels, that was not problem before PBR, and reflection probes are quite slow to update ( 1 to 3 seconds ) noticeably "brightening" the scene while its updating. In my case I have several in Bay City, and 3 scenes share two or more parcels connected.
Left an example here: http://maps.secondlife.com/secondlife/Bay%20City%20-%20Moloch/162/227/26
2 parcels, same owner, same region, same EEP... 1 probe, 1 scene... can be observed by walking the concrete walkway.
That only happens with "Use Shared Environment", does not happen if you select Midday (the new one) on the viewer as a fixed environment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Reproduce the issue at the Bay City - Moloch location while crossing the connected parcels, then trace reflection-probe updates when Use Shared Environment is active. Done means crossing parcels with the same owner, region, EEP, and shared probe no longer triggers a visible update, while fixed Midday behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100