Jump to content
Ultimaker Community of 3D Printing Experts

mlitzkow

Member
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

1 Neutral

Personal Information

  • Country
    US
  • Industry
    Education
  1. You got it! That's perfect! It was indeed a stupid mistake on my part. Thank you so much for your help. best regards, -- mike
  2. Many thanks for taking a look at my problem. I'm sorry that you were unable to reproduce the issue. That always makes things so much harder. (I have 35 years experience as a software developer.) Since you did things in a slightly different order than I had, I tried following your procedure exactly to see if that would solve the issue. Unfortunately, no. I was not aware that you can still select the two models separately after merging them. So I had tried to set extruder 2 before merging the models, and you did it after merging the models. Now I have learned that you can still
  3. With some 2-part models, I can bring in both .stl files, assign one to Extruder 1 and the other to Extruder 2, merge, and slice and print. No problem. With other 2-part models, I can bring in both .stl files and assign one to Extruder 1, but the when I assign the other to Extruder 2, immediately one of the models gets "hatched out". A specific one of the models doesn't like Extruder 2 in use, and it will "hatch out" regardless of which model I assign to Extruder 2. Cura immediately objects to this model when extruder 2 is used, regardless of which model is assigned to
  4. When I finished working with Cura yesterday I left it running on my computer (Windows 10). Upon returning to my work this morning I found that cura had exited during the night, which didn't seem like a big deal. However, on startup, I got a nasty surprise. Cura said my machine profile was corrupted and offered to delete all of my profile information. There wasn't a "no - don't do that" button, so I clicked the "X" to close the dialog. After that, all of my profiles from my Ender-4 were missing and I was back to the stock Ender-4 machine settings. I've done a lot of customization of my mac
  5. Wonderful - you just opened my eyes! I have been modeling in Fusion 360 and slicing in Cura. Somehow it never occurred to me that I could design custom supports or adhesion features in the modeling tool. Of course, it makes perfect sense now. Many thanks.
  6. GR5 - thank you for the pointer. Somehow I had the idea that benchy would need a brim. I print on PEI, which I think has a little less adhesion than glass. So far I have not gotten the benchy to stick well enough with glue sticks, but the blue painters tape works well. That eliminates the need for a brim, so the problem goes away. Well - not exactly. There is still a question of how to print letters on the bottom of something that would really need a brim. Anyway, today's problem is solved. Again, thank you for making the video. I found it very helpful.
  7. OK, I now understand why the "D" is a problem and other letters aren't. It's because of the "island" inside the "D". When I set up for either a skirt or a brim, Cura wants to put a tiny skirt (or brim) around that island. I want to be able to put part numbers, version numbers, maker's marks, etc. on the bottoms of my prints. Thus the letters on the bottom of benchy are a good test for me. I tried using a skirt with Skirt Distance set to 0 instead of a brim. That also puts a skirt around the inner part of the "D". I tried support blocking, but it seems that the brim isn
  8. I am slicing a standard 3d benchy with Cura 3.6.0 on Windows 10. Using a brim for bed adhesion and with "Brim Only on Outside" set, I find that Cura is filling in the "D" on the bottom of the boat. Going by the color scheme shown, it appears to be creating a brim inside the "D". This is not a printer issue. I'm just showing the bottom layer of the gcode file Cura creates. If I slice with build plate adhesion set to "None", there is not blue line inside the "D", so I think the blue line is part of the brim that Cura is generating for me. I want the brim, I just don't want it inside the let
×
×
  • Create New...