P5.js: image() in WEBGL affected by the material/lighting conditions

[stalgiag]

Nature of issue?

• [x] Found a bug
• [ ] Existing feature enhancement
• [ ] New feature request

Most appropriate sub-area of p5.js?

• [ ] Color
• [ ] Core/Environment/Rendering
• [ ] Data
• [ ] Events
• [ ] Image
• [ ] IO
• [ ] Math
• [ ] Typography
• [ ] Utilities
• [x] WebGL
• [ ] Other (specify if possible)

Which platform were you using when you encountered this?

• [ ] Mobile/Tablet (touch devices)
• [x] Desktop/Laptop
• [ ] Others (specify if possible)

Details about the bug:

This is more of a question about what is expected. Should calls to image() in WEBGL mode use the current lighting and material conditions? Currently if you call image(img) it behaves similarly to texture(img); rect() which is to say that it takes on the current material and lighting state. Here is an example that shows this.

My instinct is that people will usually expect image() to appear as unlit, similar to 2D mode.

[singhvisha]

hi @stalgiag , Can I work on this issue?

[stalgiag]

Hi @singhvisha yes definitely. But first we should decide what the behavior should be. What do you think?

[aferriss]

@stalgiag I think your instincts are correct, it should probably be unlit. Though now you should be able to call noLights() before a call to image to remove all lighting.

[stalgiag]

Okay I think that this has been open long enough to draw any likely responses. I definitely agree that image() should be unlit.

This could be a good opportunity for contribution from new contributors interested in WebGL.

[singhvisha]

@stalgiag @aferriss
hi , Can I work on this issue?

[stalgiag]

@singhvisha sounds good!

[stalgiag]

Closed via #4128