Hello everyone, there is now an editor scene that I believe everyone has seen before. Now there is a material preview scen
example video:
It is a video of the interface operation of the PlayCanvas editor:
So I’m planning to use babylonjs to implement this feature，The following is the envisioned UI structure diagram:
The Main Rendering in container is mainly responsible for rendering the main scene, the Material Preview Container is responsible for rendering individual material balls, and the Material Setting container is responsible for setting the material. The Material Preview container is a separate canvas with a separate camera for users to operate.
So for this situation, I have two options in mind:
- The Main Rendering container and Material Preview container use two engines, but Babylonjs’ Texture cannot be used across engines, which means that the Material Preview container needs to repeatedly load the same texture resources onto this engine
- Use multi view, both using the same Engine but with different Scene and Camera to ensure their respective rendered views. However, I saw this sentence in the official documentation：
So for this type of material preview, does anyone have a good implementation solution?
PS: For playcanvas and Threejs, their Texture can be used across renderers, so they can ensure resource reuse and reduce performance expenses in this situation