New slicer problem  

RE: New slicer problem

Can you post a link to the STL? I'm having a hard time visualizing what's wrong with the small pics.

RE: New slicer problem

https://www.thingiverse.com/thing:1675762

This is the file im using. When I tried the file on the other prusa software ( the more basic one. Can't remember what it's called ) it filled in all the gaps when I set it to supports everywhere. Not sure why this one didn't. 

RE: New slicer problem

It's waiting for a moderater, I'm assuming because I have posted a link. If you go on thingieverse and type in clear ice. It's the box looking thing. The file that this is, is the inner part. 

RE: New slicer problem

Is Support Bridges on or off?

Then there's this bit from the designer on Thingy ...

Supports are only required on the insert. I got the best results printing the insert inverted with the supports inside to hold the floor up. I use Simplify3D and set my supports to only print from the build plate. You might want to set infill to a high number. I used 50%. This is what makes the thin walls more solid to stand up to abuse.

RE: New slicer problem

I think I see what's going on. If you've inverted the part per the Thingiverse instructions, the bottom of the part is at the top of the print. PrusaSlicer is going to try to print that as a bridge between 2 supported walls. If you want to force PS to use supports for a bridged surface, open up Print Settings->Support Material and make sure Don't support bridges is not checked.

Once you've done that, PS should add supports internally:

RE: New slicer problem

Ah i see, thanks guys. I didn't realize it could bridge that much of a gap without support underneath it seeing as its a 90 degree angle. I thought it would have nothing to build on, there for just fall. It's more impressive then i 1st thought i guess lol 😆 

RE: New slicer problem

I have sliced pla items with the new slicer and it stops like I had inserted a filament change and I have to unload and reload the filament. This is really a problem when I am doing a long print (like 20+ hours) and am not awake or around to do the "filament change"

Also the printer will stop printing and my LCD says "heating" when there has been no change in the bed temp. I had a similar problem once before but it cleared up after a software/firmware update. 

I have a Mk2.5 and have not done the 2.5S upgrade so I downloaded the software/firmware under the Mk2.5 but it looks like there is no difference between the two. Just to be clear, both new firmware and software were under the Mk2.5. Also, I have printed this design before, only difference is that I have now sliced it under the new 2.0 slicer and printing using the latest firmware. Items I sliced into 2 colors worked fine except had same problem with printing stooping for a few seconds for "heating".

Any comments?

RE: New slicer problem

I did not delete my Prusa Control as it works easier than the 2.0 update. The slide bar to move up and down and select layer stops is sluggish and doesn't respond consistantly. The first layer stop works fairly well but after that I have to drag and drop the slide bar most of the time. It appears this is a good idea but a work in progress.

RE: New slicer problem

After 12 hours of printing I kept track of the "heating stops" and in about 1 hour I had 10 stops that ranged from 1 minute to 15 minutes apart. I dropped the fan speed to 175, same problem; then to 150, same problem. Printer also stopped for filament unload and load 3 times within about 18mm of layer printing. Woke up this morning and printer sitting there at a filament stop. So then I turned off the filament sensor and wala, all problems stopped, at least for the last 18mm of layers and about 2 plus hours of printing. I will see if the problem has really gone away but as of right now it appears to be a filament sensor problem. I will leave the sensor off until I get some down time and can do the Mk2.5S sensor upgrade.

Comments???

RE: New slicer problem

Posted by: merrill.a

[...] Comments???

You posted about an unrelated issue in a resolved thread, so you're unlikely to get many responses. Try starting a new topic with a meaningful subject line and you'll likely get more responses than with a threadjack.