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
[FEATURE REQUEST]<embed image in GCODE for all target machines - not just for MINI #3488
Comments
It is supported through a configuration value of a Printer profile. The mini defines So you can set it and test it for your printer, though not from the UI, but by editing the printer profile with a text editor. We will do more once you point us to other machines or octoprint implementation that reads the images from the G-code. |
TronXY X5sa does that. It uses "own" slicer which is basically a fork of Cura |
@bubnikv, I'm working on an OctoPrint plugin that will extract this thumbnail from the GCODE and I have it working, but need to know better how this is implemented currently in PrusaSlicer. Best I can tell the The plugin is still in very early stages of development and needs to be redone before release to the OctoPrint community, but any feedback you can provide would be greatly appreciated. |
I've got the plugin in a state that I'm comfortable enough to release to the OctoPrint Community and have submitted it to the Plugin Repository for acceptance. If you'd like to test it out, you can install using the url below in Plugin Manager of OctoPrint. https://github.com/jneilliii/OctoPrint-PrusaSlicerThumbnails/archive/master.zip It will automatically extract the last thumbnail specified in the PrusaSlicer printer's profile thumbnail setting. In the case of the Mini the image will be 220x124. Default Option - Modal Pop-Up opened by pressing image button in file list. Inline Option Enabled - Images show in file list, modal pop-up opened when clicked. |
Plugin has been officially accepted into the plugin repository and users are now wanting this feature enabled. Non-Mini printer users are probably going to start asking for this to be added/configurable via the application instead of fiddling with ini files. |
yeah would be a great (and simple for prusa) addition |
Looks like I am one of those that was predicted would "start asking." :^) It would be great to have a Prusa Slicer setting to embed thumbnails for my MK3s. |
@jneilliii I already got requests to support your plugin in OctoPod app. This means that many more people will be asking how to enable this feature in PrusaSlicer. Is there a ticket for adding the setting for other printers? I can create one if not. |
@bubnikv I cannot find a commit that solved this request. Was this issue solved or should we open a new one? Thanks. Gaston |
@gdombiak that was fast. I'm not aware of an issue created for enabling this for all printers except for this one, but haven't really looked. |
@bubnikv since there is an option now available, in lieu of opening a new issue, maybe you could just reopen this one? |
@jneilliii talking about fast. Just out of the oven ... compiled for the first time. :) |
Nice, I hope it was easy enough for you to implement. Quick question, if I used the same meta tag for the ufp plugin would that also work with your change or are you creating the path programmaticaly? |
@jneilliii the code is not specific to your new plugin. I read the JSON that comes back when I request all files (using REST API). There is a new field called thumbsnail (added by your plugin I guess). If you set that same field then the image will appear in your other plugin. BTW, which plugin is ufp? It was literally minutes to get this implemented. And Swift is not my main programming language .... or maybe it is by now. :) |
Cool. UFP = Ultimaker Format Package plugin. It does the same thing as this prusa thumbnails one, but for cura and ufp packages. The prusa plugin spawned from a feature request on the UFP plugin. |
Oh, that's awesome! If that plugin includes the same extra field thumbnail then it will work automagically. Let me know and I will add both plugins to the list of supported plugins. This will help spread the word and awareness about these plugins. I already support many more that you also created. :) |
@bubnikv On January 9, when the issue was closed, you mentioned to revisit it, when shown evidence for implementation. This evidence is in this thread now, see comments.
|
Sharing some more context: Printoid and OctoPod apps have added support for @jneilliii plugins. Facebook posts about these thumbnails are getting a lot of traction. Feedback is heating up. Lots of questions about how to enable things. Once we release the new version of the apps I expect a bigger spike of demand. |
And... indeed, the new release of Printoid also supports @jneilliii 's plugin, also from those users there is a lot of attention for enabling this easily. Apperently many people appreciate to see a picture of the GCODE file they select for printing. Since all the coding / processing for embedding the image is obviously allready there, and it just requires enabling selection, it looks like a quick win. |
This is quite a useful feature. I updated my custom profiles. It makes it infinitely easier for my wife and kids to pick the correct print. |
@bubnikv not sure you had a chance to catch up with this thread. Please let us know if you want us to open a new ticket for what is being discussed? Since this is a closed ticket there is a chance you are not following this conversation. I will wait a couple of days and open a new ticket (that we can close if you prefer to use this one). Thanks, |
If you want to see this feature (thumbnails available for any printer) please vote (thumbs up) #4112 |
@bubnikv Why not reopening it, given ALL the discussion here and your comment when closing to reopen it under conditions like fulfilled now??? |
@jneilliii Everyone in this thread, and also the people discussing in #4112 Right now I cannot see the difference between: "rejecting", "low prioritization (which is strange considering the wide spread support for this in apps around Prusa Slicer), "failing to see it" or anything else. This is my last attempt to reach @bubnikv . Any reaction is OK, but I will leave it alone after this if I hear nothing, since I interpret that as "no communication possible" through this channel". |
bump. |
+1 |
+1 |
There are 3488 issues open and each and every issue is important to somebody. I am sorry, but I am not that good to take care of the flood of issues and ideas continuously while being productive as a software architect and product manager. I can only look into these issues in waves, ideally somewhere after the first public alpha and before the final release. |
"There are 3488 issues open and each and every issue is important to somebody. " That is Ok, I know that kind of difficulties, having supported software for banks myself. I will live with the current way of doing it in the .ini file and will see something coming if/when it comes. |
If it makes it any easier @bubnikv SuperSlicer has already implemented the change, so maybe you could pull those back from their fork. |
Adding such a configuration field for an existing config value is quite trivial. It is only a matter of a bit of development time. We know that @supermerill added a plenty of parameters into the parameter pages, that PrusaSlicer keeps hard coded. However, we at Prusa Research are responsible to our customers to make the software easy to use and navigate, thus we |
version
2.2
target
All
firmware 3D printer brand / version + firmware version (if known)
All
Behavior
In 2.2 alpha there is support for an embedded thumbnail picturing the printed object. This is only supported for the MINI.
It would be great to also have that (configurable output) feature for other slicer variants, then it e.g. could be made visible in an octoprint plugin, or even with the (windows) browser as thumbnails and in preview with a suitable configured GCODE editor / viewer.
Project File (.3MF) where problem occurs
not applicable
The text was updated successfully, but these errors were encountered: