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] useCPURendering image TOUCH_TAP event world coordinate is different #1676

Open
a809924143 opened this issue Dec 5, 2024 · 1 comment

Comments

@a809924143
Copy link

Describe the Bug

i use TOUCH_TAP eventListener get world coordinate
I found that the world coordinates vary depending on whether or not I use the parameter useCPURendering
useCPURendering: false world coordinates is correct

Steps to Reproduce

  1. use CPU render
    await csRenderInit({
    gpuTier: false,
    rendering: {
    useCPURendering: true,
    },
    isMobile: true,
    });
  2. addEventListener
    containerRef.value.addEventListener(cstEnums.Events.TOUCH_TAP, (e: any) => {
    console.log('world', e.detail.currentPoints.world)
    })
  3. touch dicom image

The current behavior

The coordinates obtained using the useCPURendering parameter are different from those obtained without enabling it.

The expected behavior

The coordinates are the same.

OS

macOS 14.6

Node version

18.20.5

Browser

chrome 131.0.6778.86

@a809924143
Copy link
Author

useCPURendering get coordinates is  [-134.9400027722772, -245.13925771089112, -592.3]
QQ_1733395661010
not useCPURendering get coordinates is [-104.9325750009718, -244.33240249562684, -592.3]
X,Y is different,How can i got same ,Or how can the coordinates obtained by enabling the useCPURendering parameter be converted to the coordinates without enabling the useCPURendering parameter?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant