-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
[Bug] After Chrome version bump to 113 with WebGPU support, vtk.js render edge error #2819
Comments
I notice that you can manually set viewAPI to 'WebGL' by |
This is now fixed in v27.4.2 by defaulting to WebGL until the WebGPU implementation is stable. The fix will be backported shortly |
Actually, I'll leave this issue open until the backport is complete. |
What version of vtk.js are you using? Right now, versions v19.x.x-v27.x.x all have new patch releases that fix this issue. All you will need to do is either bump the patch version for vtk.js and then re-run npm install.
…On May 11, 2023 2:43:23 AM UTC, mengxiao ***@***.***> wrote:
In our actual application development, we found an error when upgrading Google Chrome to version 113. We hope the development team can pay attention to this issue.
![飞书20230511-104246](https://github.com/Kitware/vtk-js/assets/20436006/9a8079b3-a82c-4b03-960f-45bfbe89bc82)
--
Reply to this email directly or view it on GitHub:
#2819 (comment)
You are receiving this because you modified the open/close state.
Message ID: ***@***.***>
|
Closing as completed. |
Bug description
vtk.js support webgpu if browser support webgpu, and when chrome v113 start support WebGPU by default, vtk.js render edge with some problem, you can see the line was been broken, and you can't change different render mode, if you switch mode
Surface
withSurface with Edge
, you can't switch back. A error showUncaught TypeError: Cannot read properties of null (reading 'getRenderable')
because WebGPUActor.getRenderable() not exsit. Then your app is broken.Steps to reproduce
Upgrade Chrome to version 113, and then go to the GeometryViewer example.
Detailed Behavior
No response
Expected Behavior
You can manually choose whether to support WebGPU feature.
Environment
The text was updated successfully, but these errors were encountered: