# Slime Simulation WebGPU example not working **URL:** \ **Category:** Bugs\ **Tags:** webgpu\ **Created:** [July 13, 2022, 4:12pm UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140 "2022-07-13T16:12:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![milad\_hakim](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/milad_hakim/32/25632_2.png) [@milad\_hakim](https://forum.babylonjs.com/u/milad_hakim)\ **Post date:** [July 13, 2022, 4:12pm UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140/1 "2022-07-13T16:12:21Z")
Hi, I am having trouble running one of the compute shader webgpu examples for the slime mold. Before, I was able to run it without any problems. Sometimes google canary was down or something and I noticed all the webgpu examples could not run. But recently, I could not open the slime mold example. It opens everything and the UI without giving any error in the playground, but just not showing the simulation and anything. > **[Babylon.js Playground](https://playground.babylonjs.com/?webgpu#GXJ3FZ%2348)** > > Babylon.js playground is a live editor for Babylon.js WebGL 3D scenes It’s just not running but the other compute shader examples can run. Does anyone have the same issue, and if yes, do you know what causes it? Anything in the code changed or? I am starting research based on this specific example, and it’s crucial for me to have this working. @Evgeni_Popov I would highly appreciate it if anyone could help me with that. ---
**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\ **Post date:** [July 13, 2022, 4:14pm UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140/2 "2022-07-13T16:14:48Z")
Hey and welcome!! cc @Evgeni_Popov our WebGPU master ---
**Author:** ![milad\_hakim](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/milad_hakim/32/25632_2.png) [@milad\_hakim](https://forum.babylonjs.com/u/milad_hakim)\ **Post date:** [July 13, 2022, 4:17pm UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140/3 "2022-07-13T16:17:58Z")
Hi, thank you so much for letting me know. ---
**Author:** ![Evgeni\_Popov](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/evgeni_popov/32/4432_2.png) [@Evgeni\_Popov](https://forum.babylonjs.com/u/Evgeni_Popov)\ **Post date:** [July 13, 2022, 9:21pm UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140/4 "2022-07-13T21:21:36Z")
Here’s the fixed PG: > **[Babylon.js Playground](https://playground.babylonjs.com/?webgpu#GXJ3FZ%2351)** > > Babylon.js playground is a live editor for Babylon.js WebGL 3D scenes Others compute shader samples have been fixed: > > [@milad\_hakim](#): > > and it’s crucial for me to have this working A warning: The WebGPU spec is not finalized yet, it can/will still evolve before v1 is out and some things can break in the meantime. You should not rely on WebGPU being ready yet for production use. ---
**Author:** ![milad\_hakim](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/milad_hakim/32/25632_2.png) [@milad\_hakim](https://forum.babylonjs.com/u/milad_hakim)\ **Post date:** [July 15, 2022, 12:42am UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140/5 "2022-07-15T00:42:11Z")
Thank you so much. Just if it happens again, is it something that I can do myself, or do you need to change and update it from the git? Because I noticed you just changed an id number. ---
**Author:** ![Evgeni\_Popov](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/evgeni_popov/32/4432_2.png) [@Evgeni\_Popov](https://forum.babylonjs.com/u/Evgeni_Popov)\ **Post date:** [July 15, 2022, 8:28am UTC](https://forum.babylonjs.com/t/slime-simulation-webgpu-example-not-working/32140/6 "2022-07-15T08:28:06Z")
It depends on how the spec evolved. In this case, the “write” modifier was not valid anymore for storage buffers and it had to be changed to “read\_write” instead. That’s why I updated the playground(s) and saved the new id into the doc page.