-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
FrameGraph: add support for shadow generators (CSM included) #15962
FrameGraph: add support for shadow generators (CSM included) #15962
Conversation
… framegraph-internaltexture-refactor
… framegraph-internaltexture-refactor
… framegraph-internaltexture-refactor
… framegraph-resourcecont-shadowgen
… framegraph-resourcecont-shadowgen
… framegraph-resourcecont-shadowgen
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15962/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/15962/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/15962/merge#BCU1XR#0 |
Visualization tests for WebGPU (Experimental) |
WebGL2 visualization test reporter: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if possible but the nullable camera seems to complexify the code. should we not have a dummy one ? and do we render without one ?
Test PG for shadows: https://playground.babylonjs.com/#FTAT6U#11
Also in this PR:
ResourceContainer
block added