-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG - ColorLayer] ColorLayer rendering issue on firefox with planar view #2236
Comments
Hi and thanks for your detailed bug report! The different type of effects on color layers are clearly not well-documented (especially the In the case where Moreover, I too question the need for line 29 since
I'll open a PR fixing those three issues (documentation, undefined and shader code)! |
Closes iTowns#2236: - Fix undefined value passed to uniforms effect_type and effect_parameter - Remove useless intensity parameter of applyWhiteToInvisibleEffect function
Closes #2236: - Fix undefined value passed to uniforms effect_type and effect_parameter - Remove useless intensity parameter of applyWhiteToInvisibleEffect function
Closes iTowns#2236: - Fix undefined value passed to uniforms effect_type and effect_parameter - Remove useless intensity parameter of applyWhiteToInvisibleEffect function
Your Environment
Context
We used a WMS source (to render a GeoTiff) with a ColorLayer and a PlanarView and with map background.
We want to replace white color of WMS source by transparency so we try to use
effect type:2
on ColorLayer (applyWhiteToInvisibleEffect).But it seems to render black color in firefox so we apply
custom effect type
.Steps to Reproduce (for bugs)
online demo
Expected Behavior
With effect_type:2 on ColorLayer => white color must be invisible (on all browsers).
Actual Behavior
With effect_type:2 on ColorLayer => white color is replaced by black color (only on firefox, it's working on chrome).
Possible Cause/Fix/Solution
It seems it's caused by applyWhiteToInvisibleEffect.
I think we can replace line 29 by
color.a = 0.0
.It's how we fix it in our demo.
The text was updated successfully, but these errors were encountered: