Skip to content
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] v9 LightingEffect and TerrainExtension do not work consistently #8680

Closed
7 tasks
Pessimistress opened this issue Mar 18, 2024 · 0 comments
Closed
7 tasks
Labels

Comments

@Pessimistress
Copy link
Collaborator

Pessimistress commented Mar 18, 2024

Description

In v9 ShaderAssembler took over the v8 ProgramManager’s “default shader module” functionality. However, ProgramManager checks for updates every time before redraw, and ShaderAssembler does not. As a result, default shader modules added after a model is created will be ignored. LightingEffect and TerrainExtension are affected because they need to insert a shader module into every layer (shadow and terrain respectively).

As discussed with @ibgreen, the proposal is to move default module registration into deck. When a change is made, all layers invalidate their models.

Flavors

  • Script tag
  • React
  • Python/Jupyter notebook
  • MapboxOverlay
  • GoogleMapsOverlay
  • CartoLayer
  • ArcGIS

Expected Behavior

No response

Steps to Reproduce

Enable the commented out shadow and terrain render tests - the added shader modules do not take effect.

Environment

  • Framework version: 9.0.0-beta.9
  • Browser:
  • OS:

Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant