-
Notifications
You must be signed in to change notification settings - Fork 11
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: Auto Slice from drop Folder #10
Comments
wouldn't it be better if it just opened a slicer window with a gui for
selecting the options? that way we could have a XML that had the list of
resin brand Type and respective settings for each layer slice height
Robert Silvers <[email protected]> escreveu no dia sexta, 4/01/2019
à(s) 15:18:
… Currently Meshmixer has a way to to work directly with OpenSlicer, but
there is a problem - Meshmixer crashes endlessly, and the support seems to
be a random-number generator. I cannot do the same operation two times in a
row and get the same result. It is sad because it is otherwise so cool.
Netfabb, however, is great, and Autodesk has put all their cards into that
and seemingly abandoned Meshmixer, or at least put an intern or two on it.
Also, people like B9. So my proposed feature is a way for OpenSlicer to
work with *ANY* layout program automatically. It would work like this:
http://forum.makergear.com/viewtopic.php?t=1324
Set up a folder that is monitored by OpenSlicer, and, when an STL is
written to it by B9 Creator, Meshmixer, Netfabb, or other program, it gets
sliced automatically. It would parse the file name for layer size and
erosion. So, if a file were saved as yoda-lh-50-hsc-1.stl, it would print
at a layer height of 50 microns and do a horizontal size compensation of
minus 1 pixel (could also allow + values).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKke-kvzsP5XXi9rBmiJWe0S6xzdTuOvks5u_3C8gaJpZM4Zp0g9>
.
--
Com os melhores cumprimentos,
Vinicius Silva
|
Yes, that would be better. |
@X3msnake @rsilvers129 Not quite sure if I understand: Open a gui to select settings when it detects a new file... or let the use manually open a gui to select a file and its slice settings? |
i think its like having a ini with the folder default and slice the file
that gets dropped there. i may be wrong tho.
No dia sábado, 26 de janeiro de 2019, Nard Janssens <
[email protected]> escreveu:
… @X3msnake <https://github.com/X3msnake> @rsilvers129
<https://github.com/rsilvers129> Not quite sure if I understand: Open a
gui to select settings when it detects a new file... or let the use
manually open a gui to select a file and its slice settings?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKke-oyQ6yO0ujIO9Sn6mmrcXx8aPYMVks5vHJBcgaJpZM4Zp0g9>
.
--
Com os melhores cumprimentos,
Vinicius Silva
|
You have the slicer start with Windows 10 or and it watches a folder. You can use Netfabb, Asura, Meshmixer, B9, or some other program to lay out and add supports. You then save the STL into that folder that the slicer is monitoring. When it sees the file added, it pops up a GUI and you can pick layer height, exposure, and erode parameters. It then slices and makes a photon file, and then asks where to save that photon file with the GUI. This will do two things. One is that it will allow people to use any layout program and make Photon files. The other is that it will do the important erode function that only Formware has. Some nice features would be that the GUI should remember your previous settings at the very least, and even better if it has presets that you can configure and name and then just select one or add new presets. |
@rsilvers129, @X3msnake Usage:
Autoslice can be in CPU mode with progress in console (-g False -f True), CPU mode with progressdialog (-g True -f True) or in GPU mode with OpenGL window (-g True -f False). PNG's as input/output will not work correctly in user interface. Must be fixed. |
I will test it today. This is great. |
$ python PhotonSlicer.py -s ../STLs -g True -f False |
Can you try to install pyximport with ‘pip install pyximport —user’ ? |
First I got this: $ ./pip.exe install pyximport --user Then I tried again but installed cython. Then I got: $ python PhotonSlicer.py -s ../STLs -g True -f False During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Hey @NardJ we need a requirements.txt file that way it is easier for people to install :) Like this one I made for PFE https://github.com/Photonsters/PhotonFileEditor/blob/master/requirements.txt USAGE: pip install -r requirements.txt This does not invalidate the binary release, but it makes life easier for those that want to go the CLI way :) |
Done, requirements.txt is present. (Add ‘—user’ if install returns permissions error.) |
Currently Meshmixer has a way to to work directly with OpenSlicer, but there is a problem - Meshmixer crashes endlessly, and the support seems to be a random-number generator. I cannot do the same operation two times in a row and get the same result. It is sad because it is otherwise so cool.
Netfabb, however, is great, and Autodesk has put all their cards into that and seemingly abandoned Meshmixer, or at least put an intern or two on it. Also, people like B9. So my proposed feature is a way for OpenSlicer to work with ANY layout program automatically. It would work like this:
http://forum.makergear.com/viewtopic.php?t=1324
Set up a folder that is monitored by OpenSlicer, and, when an STL is written to it by B9 Creator, Meshmixer, Netfabb, or other program, it gets sliced automatically. It would parse the file name for layer size and erosion. So, if a file were saved as yoda-lh-50-hsc-1.stl, it would print at a layer height of 50 microns and do a horizontal size compensation of minus 1 pixel (could also allow + values).
The text was updated successfully, but these errors were encountered: