kmanstudios 1,120
1 hour ago, ahoeben said:
Though that makes things easier to implement, the main reason why I am hesitant to do that is that the support blocker acts on the surface of the model. It would be confusing to have two tools, where one would act on the buildplate and one would act on the model. Marking areas on the buildplate alone does not cover cases where you need support that does not "touch the buildplate".
I think this is where having that little 'ahoeben continent' of features explained or demonstrated would be helpful. It may answer the question others have as well as myself.
And, why a continent? Because 'No man (or woman) is an island!'
- 1
Recommended Posts
Top Posters In This Topic
23
19
13
10
Popular Days
Mar 27
23
Mar 28
15
Mar 29
15
Apr 4
15
Top Posters In This Topic
kmanstudios 23 posts
ahoeben 19 posts
SandervG 13 posts
rebekah_harper 10 posts
Popular Days
Mar 27 2018
23 posts
Mar 28 2018
15 posts
Mar 29 2018
15 posts
Apr 4 2018
15 posts
Popular Posts
SandervG
After another period of continuous research and development, we're proud to share the latest Ultimaker Cura Beta with you. We're excited to hear what you think of the new and improved features. With y
burtoogle
Thanks for the mention @SandervG, I will put together a topic that describes the new bridging features and the associated settings.
ahoeben
A rather big and often-requested change that is not mentioned in the blog post is that Post processing scripts are now persistent between sessions. (Not my feature, @ghostkeeper deserves the credit)
Posted Images
ahoeben 1,986
Though that makes things easier to implement, the main reason why I am hesitant to do that is that the support blocker acts on the surface of the model. It would be confusing to have two tools, where one would act on the buildplate and one would act on the model. Marking areas on the buildplate alone does not cover cases where you need support that does not "touch the buildplate".
Link to post
Share on other sites
ahoeben 1,986
The Cura logs (cura.log) are found in the "Configuration Folder". Normally, when Cura is not crashing, you can access the configuration folder through the Help menu (Help -> Show configuration folder). Since Cura crashes on startup for you, you will have to locate the folder directly:
%APPDATA%\cura\<Cura version>\cura.log
which is usuallyC:\Users\<your username>\AppData\Roaming\cura\<Cura version>\cura.log
~/Library/Application Support/cura/<Cura version>/cura.log
~/.local/share/cura/<Cura version>/cura.log
Link to post
Share on other sites