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
I am struggling to get Meshlab to recognise my laptops graphics card. My laptop is a Dell XPS 15 9520 with the following specs:
12th Gen Intel(R) Core(TM) i7-12700H, 2300Mhz, 14 Core(s)
32 GB RAM
NVIDIA GeForce RTX 3050 Ti Laptop GPU
1TB SSD
Windows 11
I am running version 2023.12 Installer (which should be the latest version as I have only downloaded meshlab a few days ago).
When I run meshlab I always get the 'UNRECOGNISED CARD' in the bottom right of the window and can't seem to resolve this on windows 11 (I have tried many online tutorials and the methods they use only seems to work in older versions of windows, such as right clicking on the meshlab shortcut and there is an option to select graphics card which does not exist in windows 11). And this is severly throttling my FPS (on the order of 1-2 FPS on average). Is there any way to force meshlab to recognise my laptops graphics card?
Thanks,
Ben
The text was updated successfully, but these errors were encountered:
Hi,
I am struggling to get Meshlab to recognise my laptops graphics card. My laptop is a Dell XPS 15 9520 with the following specs:
I am running version 2023.12 Installer (which should be the latest version as I have only downloaded meshlab a few days ago).
When I run meshlab I always get the 'UNRECOGNISED CARD' in the bottom right of the window and can't seem to resolve this on windows 11 (I have tried many online tutorials and the methods they use only seems to work in older versions of windows, such as right clicking on the meshlab shortcut and there is an option to select graphics card which does not exist in windows 11). And this is severly throttling my FPS (on the order of 1-2 FPS on average). Is there any way to force meshlab to recognise my laptops graphics card?
Thanks,
Ben
The text was updated successfully, but these errors were encountered: