-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
Support Question: What are the ideal thumbnail dimensions? #648
Comments
To me, it only appears from the file browser, but when printing, the thumbnail does not appear, I am using PrusaSlicer |
Any Square aspect ratio should work fine. I think I did 256x256 and don’t have this problem. @EPDCenter just tap the percentage and will switch around :) |
Thanks, yes square ratios work a bit better. Possibly worth adding to the "Tips and Tricks" section. |
That circle doesn't look round, is there something janky with the resolution on your screen which is affecting the layout on the UI? Edit: Yes definitely. There's huge gaps between Layer and the printer name as well. They are normally right on each other. Your UI elements are all over the place, not just the thumbnail. |
Solved, many thanks !!! |
Has been updated, thanks :) |
@EPDCenter What was the fix for this? I have OctoDash running on a Pi 3, Adafruit 3.5" PiTFT display (480x320) and have the same issue that you posted above? The circle on mine is round, but the thumbnail looks like the image you posted and there is a gap between the 'Layer x of x' line and the name of the printer. |
Is there an ideal set of dimensions to generate thumbnails for use in OctoDash?
When setting up PrusaSlicer I have adopted the Prusa Mini settings of 16x16 and 220x124. In OctoPrint it simply crops its display. In OctoDash it doesn't.
The result is: https://imgur.com/a/OjnRVpl
Fine in the file selection, but absolutely pointless on the print progress display (7" 1024x600 display)
Does OctoDash benefit from a specific dimension of thumbnail?
The text was updated successfully, but these errors were encountered: