Jump to content

PhoToplex

Member
  • Posts

    8
  • Joined

  • Last visited

Personal Information

  • 3D printer
    Other 3D printer

PhoToplex's Achievements

1

Reputation

  1. You were right. Ultimaker added these as a way to prevent newbies from damaging their nozzles by bashing into the clips. However, I long ago removed the clips when I went to a PEI bed sheet. My thinking is I can remove the two rows entirely (top and bottom of the bed sheet) which should open the whole bed back up for printing...
  2. I think you might be onto something... In the def.json for my printer, it has this - think it's related? "machine_disallowed_areas": { "default_value": [ [[-117.5, 117.5], [-117.5, 108], [117.5, 108], [117.5, 117.5]], [[-117.5, -108], [-117.5, -117.5], [117.5, -117.5], [117.5, -108]]
  3. Even weirder... restarted Cura, no margins. Import the STL, margins appear... could it be something in the STL file from Fusion 360? Is it a model setting in Cura?
  4. All those are off already. I'm going crazy here! Been looking at this for a total of 6 hours
  5. Already been through that article and set those. No change. I only have Travel Avoid set, which is the darker 1mm band you see all around. The 2mm band you see at the top refuses to go away, despite going through every single print setting one by one.
  6. What's causing these two grey bands along the far left and right of the bed area? It seems these are the cause, but they shouldn't be there. The top and bottom do not have them, and shows the whole length area.
  7. I am using Cura 4.8 with an Ender3 v2. This printer has a max print area of 220x220. I created an object that prints at 215x215, so well within the bounds of the printer. Yet, Cura refuses to slice it. I have: Disabled bed adhesion options (skirt etc) Double checked the printer settings in Cura (220x 220y 250z) Removed the printers Start G-Code lines that print the first two lines along the y-axis on all prints Does anyone know why? When I import this same object into PrusaSlicer it works. This seems like a bug.
×
×
  • Create New...