secondlife / secondlife/viewer

Unloaded emmissive maps should be black, not grey

Open
#5,701 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

All textures, when they haven't loaded yet, default to grey. For the emmissive channel of PBR, a grey texture means the whole object glows quite brightly. Normally, emmisive textures are mostly black. So, when a pbr emmissive texture is present but not downloaded, the viewer should replace it with a solid black texture

https://secondlife.canny.io/admin/feedback/bug-reports/p/unloaded-emmissive-maps-should-be-black-not-grey


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #5701 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @canny[bot] (replace 20 with the amount, and @canny[bot] with the user to tip).

📖 If you want to learn more, check out our documentation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the viewer's PBR emissive texture loading and fallback path, focusing on what happens while an emissive map is unavailable. Verify the result with an object using an unloaded emissive texture: the temporary texture should appear black rather than grey, without changing other texture channels.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.