-
-
Notifications
You must be signed in to change notification settings - Fork 36k
WebGPURenderer: Introduce Inspector
#31869
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
Conversation
📦 Bundle sizeFull ESM build, minified and gzipped.
🌳 Bundle size after tree-shakingMinimal build including a renderer, camera, empty scene, and dependencies.
|
This is really awesome! Everything looks so nice and clean! I especially like the new formatting of the example's description. I love the idea of having a unified GUI for configuration and statistics. In this way, we don't need |
I made some fixes and improvements in the inspector, this part should be fine now. I’ll merge and add other improvements in other PRs. |
Description
Inspector
This PR introduces a native inspector for Three.js that can monitor render calls, logs, parameters, and in the future memory usage and nodes as well, such as thumbnails of passes for example.
Since the Node System can feel like a black box, the goal is to show the rendering flow, as well as tips on what could be improved, without seeming intrusive.
There’s still plenty that can be improved, but it looks like we’re on the right track.
To insert the inspector, just add:
The
Inspector
is added fromaddons
, and since it is not included by default, performance should remain essentially the same.New look
Inspector
, initially trying to preserve the existing syntax.example.css
file was added in the hope of making the info look better to match the inspector.Live
I added some error for the tests.
Toggle inspector panel button
Performance
Console
Parameters