-
Notifications
You must be signed in to change notification settings - Fork 2k
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
1.40.1-rc2 does not retain the filament names/associations while saving AMF file #1036
Comments
This is actually in the testing, implemented in the following branch:
https://github.com/prusa3d/Slic3r/commits/amf_activate_existing_presets
There is a release planned at the end of this month, and the branch above
should be integrated in there.
…On Fri, Jul 6, 2018 at 9:31 AM, kursatu ***@***.***> wrote:
Version
*Version of Slic3r used goes here*
1.40.1.-rc2
*Use About->About Slic3r for release versions*
*For -dev versions, use git describe --tag or get the hash value for the
version you downloaded or git rev-parse HEAD*
Operating system type + version
*What OS are you using, and state any version #s*
Windows 10
Behavior
-
*Describe the problem*
The filament names are not saved and a generic name is displayed in
the filament list after
opening an AMF file.
A simple solution could be show a decorated the name in the filament
list , for example
.
and while saving the name in the AMF file
This makes the subsequent usage of AMF practically impossible, unless
you make a note of
the filament names somewhere.
You wont be able to remember with what filament you have saved the AMF
file with
and load that filament onto the printer.
-
*Steps needed to reproduce the problem*
1- Open an STL and it as an AMF file
2- Open the AMF file, the original filament names are replaced with
generic names you
can't actually know which physical filament to load onto the printer.
If you were to use the solution I recommended above, the n the filament
list would show names like
B3.zip.amf.Prusa PLA
[image: sli3r6]
<https://user-images.githubusercontent.com/1686475/42365595-c9142cf0-80b3-11e8-88ca-95fc162478d0.PNG>
- *If this is a command-line slicing issue, include the options used*
- *Expected Results*
- *Actual Results*
- *Screenshots from Slic3r preview are preferred*
*Is this a new feature request?*
STL/Config (.ZIP) where problem occurs
*Upload a zipped copy of an STL and your config (File -> Export Config)*
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1036>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFj5I8D_zUnAm3o2M31N_jMj0IL9klD3ks5uDxI8gaJpZM4VFAqf>
.
|
This will be part of the 1.41.0-alpha. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Version of Slic3r used goes here
1.40.1.-rc2
Use
About->About Slic3r
for release versionsFor -dev versions, use
git describe --tag
or get the hash value for the version you downloaded orgit rev-parse HEAD
Operating system type + version
What OS are you using, and state any version #s
Windows 10
Behavior
Describe the problem
The filament names are not saved and a generic name is displayed in the filament list after
opening an AMF file.
A simple solution could be show a decorated the name in the filament list , for example
<AMFName>.<FilamentName>
and while saving the name in the AMF file
This makes the subsequent usage of AMF practically impossible, unless you make a note of
the filament names somewhere.
You wont be able to remember with what filament you have saved the AMF file with
and load that filament onto the printer.
Steps needed to reproduce the problem
1- Open an STL and it as an AMF file
2- Open the AMF file, the original filament names are replaced with generic names you
can't actually know which physical filament to load onto the printer.
If you were to use the solution I recommended above, the n the filament list would show names like
B3.zip.amf.Prusa PLA
Is this a new feature request?
STL/Config (.ZIP) where problem occurs
Upload a zipped copy of an STL and your config (
File -> Export Config
)The text was updated successfully, but these errors were encountered: