The point cloud cannot be displayed normally.
After running yarn tauri dev,
you can view the normal scene in the browser at the same time.
http://localhost:1420
@Rocan One test you could perform is to pass the point size to the shader through a uniform. This is a difference between the Threejs and Babylon.js repro, where a direct value (2.0) is set in the former case, whereas in the latter, a uniform variable is used to pass the value.
Actually I have tested as per your previous suggestion
const engine = new BABYLON.Engine(canvas, true, { disableWebGL2Support: true });
engine.disableUniformBuffers = true;
But it has no effect, and I didn’t continue to update the sample code.
After completing the cross-test, it can be determined that there is a conflict between MeshBuilder and PCS (or a custom shader implementation), which is limited to the ubuntu18.04 webkit environment. This is a problem I want to report.
Maybe waiting for @bghgary to do some reproductions will be more convincing, thanks again everyone
In fact, it’s not the same test. The new one would mean you add a uniform float pointSize; in the vertex shader, and replace gl_PointSize = 2.0; with gl_PointSize = pointSize;. This way, it would be in line with what we do in Babylon.
We could try to compare two Spector reports, but we would need a link to the Threejs snippet/jsfiddle to do so.
Can we delete uniform float pointSize; directly?
This does not affect the reproducibility of the problem
Do you mean you tested in your Threejs jsfiddle that passing the point size through a uniform variable work? Can you provide the link to this jsfiddle?
I updated the example for threejs, hope it helps
Thanks for the repro.
Can you test this PG: https://playground.babylonjs.com/#Y8KCUM#3 => trying to be as close as possible to the Threejs fiddle.
Also this one: https://playground.babylonjs.com/#Y8KCUM#4 => the points won’t rotate, but it checks if the problem comes from the fact that the vertex buffers are STATIC_DRAW in Threejs and DYNAMIC_DRAW in Babylon.
Everything works fine in chrome(of course all problems only occur in ubuntu18.04 webkit).
Do you think it needs to be transplanted to ubuntu18.04 tauri webkit for testing?
Yes, you should copy/paste the contents of the createScene function from the playground I provided into the createScene function of your own Tauri project and see how it goes.
I did the following test as you said, and you can see that neither code can see the point cloud.
Maybe I can provide a remote like teamviewer for you to debug?
If you have any ideas you can connect directly and don’t worry about breaking anything, it’s just a virtual machine, I’ll keep it running for a few days, hope that helps solve the problem
Password: Babylonjs2024
I can’t install Teamviewer:
I think I’ll check with @bghgary regarding what testing we might be able to do, but we’re currently in the home stretch before the v7 release, so please be patient as we may not be able to take a look right away.