nus-vv-streams / vvtk

A toolkit for volumetric video research
MIT License
9 stars 8 forks source link

`vvplay` window stops responding after navigation attempts #54

Open Hsiiiii opened 3 months ago

Hsiiiii commented 3 months ago

After executing vvplay ./Ply and vvplay ./Pcd , where ./Ply and .Pcd are folders containing .ply files and the .pcd files respectively, the window displaying the point cloud becomes unresponsive after navigating using keyboard. The .ply files are sourced from the Long Dress dateset, and the .pcd files are converted from it by vv convert. When the window becomes unresponsive, the window freezes at certain frame even it was playing, and a message "Unknown" is not responding pops up as the attached image. Screenshot from 2024-05-03 14-56-35 However, if the window displaying the point cloud stopped being focused (after clicking out of it), the window will continue to play the point clouds without reacting to the navigation control that made it got unresponsive. In the terminal, there's also an error message MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete. If I only switch between frames using the arrow key, the same issue will still occur. The output of running rustc --version --verbose is

rustc 1.78.0 (9b00956e5 2024-04-29)
binary: rustc
commit-hash: 9b00956e56009bab2aa15d7bff10916599e3d6d6
commit-date: 2024-04-29
host: x86_64-unknown-linux-gnu
release: 1.78.0
LLVM version: 18.1.2

And the output of running lshw -C display is

  *-display                 
       description: VGA compatible controller
       product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 resolution=1920,1200
       resources: irq:28 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff
tiif commented 3 months ago

Thanks for the details. I never encounter MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete before, so I suspect this might be the problem. Our wgpu dependency seems to have something Vulkan related. I am trying to understand the possible cause from this: https://www.linux.org/threads/most-games-from-steam-dont-launch-because-pc-too-old-for-vulkan.47192/.

Could you please try to update the packages through sudo apt update && sudo apt upgrade first?

@weitsang @Shiyuang-scu I am not particularly familiar with hardware and driver related problem, please help to take a look at this.

weitsang commented 3 months ago

To isolate the problem, could you try running wgpu examples and see if the examples run correctly?

wpgu also comes with a few environment variables. You can try setting WGPU_BACKEND to gl to see if Vulkan is an issue.

Hsiii commented 3 months ago

Thank you for your prompt reply.

I tried update the package, they are up to date.

I ran the hello example of wgpu examples with WGPU_BACKEND set to gl, and MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete popped up instead of the expected output.

Hsiii commented 3 months ago

I will test it with a new GPU after a device update of our lab. I will get back to you as soon as the new hardware arrived, thanks.