@zemso You can choose the new "Snug" support type style to shave a fair bit of time (slicing takes a lot longer), but you won't get down to the time with version 2.3.
.
thx, but to be honest. i never had issues with the support of any prints. With 2.4 i just pay 1,4€ more for the same Print + Time/Energy.
For that big print maybe not that hard but i would expect "improvements" also in cost efficiency.
The supports are more stable now, they require a bit more material.
.
indeed. with this print it saved 2,5h. Thats pretty cool. noticed also the slicing time but who cares. 😛
it saved also 50% Money and Filament compared to Grid/2.3
that something i can live with. thank you 🙂
@zemso You can choose the new "Snug" support type style to shave a fair bit of time (slicing takes a lot longer), but you won't get down to the time with version 2.3.
Snug vs Grid
I know it's me being dim but can somebody explain the difference between snug and grid supports?
Snug
We are still fine tuning our print profiles for the new "snug" supports. The "snug" supports behave differently than the old "grid" supports. You may want to experiment with different gaps between object and support interfaces, also the "snug" supports may require more interface layers than the "grid" supports to produce wide enough regions to be printable FDM technology.
--------------------
Chuck H
3D Printer Review Blog
@towlerg
Snug and Grid
Regards
Swiss_Cheese
The Filament Whisperer
Thanks swiss, a picture is worth a thousand words. I take it the structure of both support styles is the same?
Snug and grid
I need to test these. I need to see how it changes things on my prints.
--------------------
Chuck H
3D Printer Review Blog
@towlerg
Thanks swiss, a picture is worth a thousand words. I take it the structure of both support styles is the same?
It's funny you say it like that, that's exactly what I was thinking when I posted them. yes they are the same I copied and pasted the first one and then just changed ones support properties to Snug and the others to Grid, they can be done nicer I spent 1min making them, I don't want to deal the supports a bad hand, they are defiantly better then they were. I've I identified a couple of bugs with regard to them, but I'm waiting till they are finished to bring them up since they keep telling everyone they aren't finished yet.
Happy Halloween
Swiss_Cheese
The Filament Whisperer
I must admit I'm very happy with what they've done with snug supports. So far I haven't run into any issues with it. It may use a bit more material, but on the other hand, it doesn't produce all those extraneous support pillars all over the place. Two thumbs up from me.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: PrusaSlicer 2.4.0-beta1 is OUT!
I installed the beta version about a week or so ago. I'm running Linux Mint. I copied my original configuration directory (~/.config/PrusaSlicer) to the new config directory (~/.config/PrusaSlicer-beta). I'm experiencing a crash every second time I send the sliced g-code to OctoPrint. The g-code does appear to transfer properly though. Might this be related to copying the configuration directory instead of performing a setup from scratch?
RE: PrusaSlicer 2.4.0-beta1 is OUT!
I am still unable to send gcode direct to an octoprint printer. The 'test' button works but it is then throwing an error where it cannot find the printer when I try to send the file. And then it crashes on the second attempt (as above).
RE: PrusaSlicer 2.4.0-beta1 is OUT!
I don't have a problem sending jobs with the 2.4 beta but I've always found PS to be a bit quirky about it. Sometimes the test button shows everything is okay but then it can't find the printer. IIRC that was when I used a hostname (ee.g., xyz.local). The syntax that works for me is http://192.168.40.195/. After figuring this out, I never bothered to look more deeply into this inconsistent behavior.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: PrusaSlicer 2.4.0-beta1 is OUT!
yes, I should have specified that it happens when I try to use 'host.local' rather than an IP address (as that is dynamic on my local network).
RE: PrusaSlicer 2.4.0-beta1 is OUT!
I thought so. Not new to 2.4 but not fixed either. I use static IP addresses for my raspis.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: PrusaSlicer 2.4.0-beta1 is OUT!
Are either of you using a VPN? I found that behavior happened if my VPN was active. Once or twice, I was able to drop to a terminal and 'ping octoprint.local' and it would start working, but that was rare. Like fuchsr, I switched to using an IP address and reserved it in my DHCP server so it wouldn't change.
RE: PrusaSlicer 2.4.0-beta1 is OUT!
No VPN
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
Has anyone else experienced this?
Windows 7 Professional
PrusaSlicer-2.4.0-beta2+win64-202111261611 is giving me this when I try to run it.
I get the same from the PrusaSlicer-2.4.0-beta2+win32-202111261557.
Regards
Swiss_Cheese
The Filament Whisperer
RE: PrusaSlicer 2.4.0-beta1 is OUT!
@Swiss_Cheese
Thanks for heads up. It is a HiDPI (display high resolution API) call that is seemingly not available on Windows 7. We did not test on Windows 7. We will try to fix it.