Skip to content
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] Cannot destructure property 'direction' of 'metadata' as it is undefined #4405

Open
myousefipour opened this issue Oct 4, 2024 · 0 comments
Labels
Awaiting Reproduction Can we reproduce the reported bug?

Comments

@myousefipour
Copy link

myousefipour commented Oct 4, 2024

Describe the Bug

Some mobile devices, such as the Samsung A51, are unable to display images. On these devices, the following error occurs, which is related to the GPU:

"Failed to load OES_texture_float_linear. Texture filtering is not available for 32F internal formats.
[.WebGL-0x700a77ce00] RENDER WARNING: texture bound to texture unit 0 is not renderable. It might be non-power-of-2 or have incompatible texture filtering (maybe)?"
To resolve the issue on these devices, it is better to use CPU rendering capabilities.

By enabling the parameter useCPURendering: true, the following error occurs for all modalities:
"Cannot destructure property 'direction' of 'metadata' as it is undefined."

Steps to Reproduce

۱. In the config file, make these corrections :
useCPURendering: true
imageRendering: 'wadouri',
thumbnailRendering: 'wadouri',

The current behavior

This error occurs:
Cannot destructure property 'direction' of 'metadata' as it is undefined.

The expected behavior

It is expected that the image will be displayed as in the Cornerstone 3D template in the link below:
https://www.cornerstonejs.org/live-examples/localcpu

OS

windows 11

Node version

20.12.2

Browser

chrome latest

@myousefipour myousefipour added the Awaiting Reproduction Can we reproduce the reported bug? label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Reproduction Can we reproduce the reported bug?
Projects
None yet
Development

No branches or pull requests

1 participant