UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Make it easier to have more instances open (%appdata% needs reset)
Posted
· Make it easier to have more instances open (%appdata% needs reset)
That would be wonderful.
Instead I'm going to give you the workaround I use. I have 5 active printers (used almost every week - often all 5 running at once). 3 different types of printers. What I do is I always save the *project*. I don't save profiles. When you save the project it saves the STL file(s) and the rotations and positions and scalings. It saves all the settings and overrides. It saves even machine settings.
It's quite quick to save your current project (even if you aren't quite done modifying all your settings for the current project), quickly open another project, make some change, reslice, save that project again, then go back to the project you were just working on. I do this all the time because like I said - I have 3 printer types.
For example I'm working on slicing something for my S5 but suddenly realize one of my um2go's has a part coming loose from the bed (rare, but it happens). I decide to enable brim so I save the S5 project, load the um2go project, enable brim, save the gcode, save the project, copy the gcode to the um2go's sd card, restart that print, then back to my computer I load the S5 project that I had been working on.
If you have a bed of parts - say 25 parts all rotated and positioned just the way you want - if you save that project and load it at a later time it will remember all the positions and rotations of all the parts.
Posted
· Make it easier to have more instances open (%appdata% needs reset)
14 hours ago, DDDPrintno said:
This commonly leads to what I guess is de-sync within the settings of Cura. It messes up the files, and the easiest way I've found to get things working again is to delete all %appdata% and manually adjust and insert settings everytime this happens, which can occur many times a month.
Cura simply checks what files are different from how you originally loaded them. So the last instance of Cura that you shut down is the version that is saved to disk.
14 hours ago, DDDPrintno said:
My suggestion? Implement tabs like photoshop or every web browser and figure a way to sync while having multiple projects open. This makes it possible for users to work on multiple projects without having 5 cura.exe open.
Good suggestion, but unfortunately, it's easier said that done. Implementing this would take months of work from the entire team.
1
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
A year after the merger of Ultimaker and MakerBotQQ, we have unlocked the ability for users of our Method series printers to slice files using UltiMaker Cura. As of this release, users can find profiles for our Method and Method XL printers, as well as material profiles for ABS-R, ABS-CF, and RapidRinse. Meaning it’s now possible to use either Cura or the existing cloud-slicing software CloudPrint when printing with these printers or materials
Recommended Posts
gr5 2,095
That would be wonderful.
Instead I'm going to give you the workaround I use. I have 5 active printers (used almost every week - often all 5 running at once). 3 different types of printers. What I do is I always save the *project*. I don't save profiles. When you save the project it saves the STL file(s) and the rotations and positions and scalings. It saves all the settings and overrides. It saves even machine settings.
It's quite quick to save your current project (even if you aren't quite done modifying all your settings for the current project), quickly open another project, make some change, reslice, save that project again, then go back to the project you were just working on. I do this all the time because like I said - I have 3 printer types.
For example I'm working on slicing something for my S5 but suddenly realize one of my um2go's has a part coming loose from the bed (rare, but it happens). I decide to enable brim so I save the S5 project, load the um2go project, enable brim, save the gcode, save the project, copy the gcode to the um2go's sd card, restart that print, then back to my computer I load the S5 project that I had been working on.
If you have a bed of parts - say 25 parts all rotated and positioned just the way you want - if you save that project and load it at a later time it will remember all the positions and rotations of all the parts.
Link to post
Share on other sites
nallath 1,118
Cura simply checks what files are different from how you originally loaded them. So the last instance of Cura that you shut down is the version that is saved to disk.
Good suggestion, but unfortunately, it's easier said that done. Implementing this would take months of work from the entire team.
Link to post
Share on other sites