You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I used usbipd to map the Femto Bolt device connected to Windows into WSL. When I tried to test the camera connection using OrbbecViewer, the color image stream displayed normally. However, as soon as I attempted to switch to the depth image stream, the viewer crashed and an error was reported. (this is not a problem of OrbbecViewer)
Additional context
I suspect the issue might be related to WSL2's inability to communicate with the GPU. However, even after reinstalling the graphics driver and mesa-utils, the same error persists, and the dri/ directory still does not exist.
The text was updated successfully, but these errors were encountered:
Describe the bug
I used usbipd to map the Femto Bolt device connected to Windows into WSL. When I tried to test the camera connection using OrbbecViewer, the color image stream displayed normally. However, as soon as I attempted to switch to the depth image stream, the viewer crashed and an error was reported. (this is not a problem of OrbbecViewer)
Reproduction Steps
On Windows:
usbipd bind --busid
usbipd attach --wsl --busid
On WSL2 Ubuntu22.04:
sudo -i
./OrbbecViewer
Then click on the "Depth" button on the top toolbar
Expected behavior
Depth engine initializes successfully and properly displays the depth image
Log Output
The following is the last normal output before I click on the button and the viewer crashes:
Output of terminal:
Output of eglinfo:
System Environment:
Tool/SDK Version:
Device Information:
Additional context
I suspect the issue might be related to WSL2's inability to communicate with the GPU. However, even after reinstalling the graphics driver and mesa-utils, the same error persists, and the dri/ directory still does not exist.
The text was updated successfully, but these errors were encountered: