5.0.0-alpha.64 has been released
I donât really know what this âCopyâ chart isâŚ
In the demo, thereâs a copy back of a texture from GPU to CPU to get the level of the water and position the buoy accordingly: itâs the WavesGenerator._getDisplacementMap
method which is doing that. If you donât need it, you can comment the call to _getDisplacementMap
in WavesGenerator.update
. Maybe it will help with this chart?
ummm, big change yesterday
Yes but those are only warnings, it does not prevent the demo to work. Iâm not sure Tint is updated yet to not generate the [[block]]
attributes, we are going to have a look.
I donât know why that canvas canât display when using WebGPU after this morning (yesterday is good).
This is work in Engine
This is work in WebGPUEngine
https://playground.babylonjs.com/?webgpu#YX6IB8#35
This PG didnât work too (yesterday work well)
In Canary
In Chrome
https://playground.babylonjs.com/?webgpu#YX6IB8#35 does work for me in Canary.
The black textures are expected in Chrome, itâs because it lacks some of the latest changes that landed only in Canary.
As your screenshot with Canary is the same than with Chrome I suspect you made a mistake and it is really a screenshot coming from Chrome(?)
I donât experience this problem, I refreshed 5 times in a row and it worked 5 timesâŚ
Keep in mind that WebGPU support is still a work in progress, it will normally be shipped in Chrome only in Q2 next year so problems are still to be expected.
Hi Popov, I found why my webEngine throw 500+ warning and canvas display white,
this is question I asked last week:
I create a bug topic about it:
Also Merry Christmas!!!
Enjoying your holidays and remenbering protecting yourself from Omicron
Oh my miss, I forget to set solution