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
When opening the dialog for importing a file (CTR-I, or over the menu) it's restricting the display of objects to the extensions defined by the DDL.
In the previous version v2.8.0) it showed all objects in the directory this included a link to my 3D object directory on the NAS.
Now I can't access this location anymore since is preselecting the objects that will be visible..
On top of that I can't not even access my 'mount' directory to access the NAS.
There should be an entry in the DDL that's allowing to list ALL objects in a given directory.
Project file & How to reproduce
Not project data available (first start of PS)
Checklist of files included above
Project file
Screenshot
Version of PrusaSlicer
v .2.9.0 flatpak
Operating system
Linux Mint v21.3
Printer model
Ender-3
The text was updated successfully, but these errors were encountered:
Please search for existing issues. This one has so many duplicates that there's a stickied item at the top of the page #13820
Its a flatpack issue. #13820 (comment)
Description of the bug
When opening the dialog for importing a file (CTR-I, or over the menu) it's restricting the display of objects to the extensions defined by the DDL.
In the previous version v2.8.0) it showed all objects in the directory this included a link to my 3D object directory on the NAS.
Now I can't access this location anymore since is preselecting the objects that will be visible..
On top of that I can't not even access my 'mount' directory to access the NAS.
There should be an entry in the DDL that's allowing to list ALL objects in a given directory.
Project file & How to reproduce
Not project data available (first start of PS)
Checklist of files included above
Version of PrusaSlicer
v .2.9.0 flatpak
Operating system
Linux Mint v21.3
Printer model
Ender-3
The text was updated successfully, but these errors were encountered: