-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
My blog page & some feature requests #266
Comments
Currently Slic3r does not visualize the G-code, but an intermediate result, where the path ordering has not been decided yet, therefore the tool position cannot be shown yet. This is something to be improved, but I believe there is more important stuff to do.
That is easy and it has been asked for before.
This has been asked for before, but it is not that easy to do as the firmware controls the acceleration. Closing as the requests are duplicates of existing issues. Thanks for the blog link. |
Excellent response - many thanks. I understand the issue with visualizing GCode; obviously you can't do it before it exists. I don't know how many people would actually use this feature, but I do fairly often. I'm in the process of posting a new blog page about Plic3r and it will include a couple of paragraphs about using Craftware's GCode viewing capability to check Plic3r's final output. Both programs produce output PS: I am also going to amend my blog to say Plic3r is now my slicer of choice. Keep up the great work. |
… fix. Also big pass to not make the app crash even if there is no setting ui file.
Version
1.34.1.3-prusa3d-win64
I was so impressed with this version I posted this blog page: http://birkbinnard.com/blog/variable-layer-height/
After a bit more use I came up with these feature requests for the Preview screen:
The text was updated successfully, but these errors were encountered: