PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?  

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

This happens occasionally (not only on Plicer but other Github projects). This allows the development team to tag a release level internally for various reasons. Or it is there for external developers/testers to access and have a reference point for communication back to the internal development team.

BTW, you can download it, but it is only available as source code (the .zip and .tar.gz icons are links to download the source code with either of the two archiving formats). But it would be up to you to compile it. If you aren't up to compiling it then trust that you aren't the intended audience for that release level. 😉 (I know that I'm not.)

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

@sembazuru

I have been developing SW for more than 30 years - I'm sure I could compile the source, have done that before.

What I was interested in, is, if anybody else had done that and found it to be worth the effort. There is no description of the release and not much in the log.

I will properly wait for the next compiled test release...

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

I'd recommend waiting. I've done it a few times and while it's not hard, it can be tedious and depending on your system can by annoying to get the dependencies set up. 

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

Thank you. I think I will be waiting...

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

A lot of work is going on the master branch of the PrusaSlicer Github, there has been many commits of modifications and Gyroid infill is broken at this moment, I'm sure that there wil be a new full alpha release soon.

By the way the change of alpha from 2-3 seems to be due to a change in the congfiguration structure which has a new form in Alpha 3.

It does build at the moment but I would wait a while.

-- 

Peter Hull G4DCP

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

Posted by: @peter-h16

A lot of work is going on the master branch of the PrusaSlicer Github, there has been many commits of modifications and Gyroid infill is broken at this moment, I'm sure that there wil be a new full alpha release soon.

By the way the change of alpha from 2-3 seems to be due to a change in the congfiguration structure which has a new form in Alpha 3.

It does build at the moment but I would wait a while.

-- 

Peter Hull G4DCP

 

Is that after alpha2 was cut? Gyroid works fine for me and I've been using alpha2.

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

@vintagepc

Yes I used alpha2 succesfully with gyroid.

So whatever causes the issue is post alpha2.

Interesting that it currently appears to generate zero infill when set to gyroid but other fills seem Ok.

Peter

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

I think there's a more general infill issue; I filed a bug where I observed it attempting to infill on top of a gap fill extrusion in 2.2.0-A2. 

Curiosity- are you sure it's actually not generating any infill in the gcode, or is it just failing to render it in the layer preview?

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

@vintagepc

To be honest I am NOT sure, what I observe was a lack of infill on the layer preview, rather than actually going as far as printing it.

Sorry if I was making an invalid assumption!

-- 

Peter

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

I have now repulled the latest from master and gyroid seems to be working again, as I said earlier there is a lot of activity by several developers on the master branch at the moment.

-- 

Peter

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

Supports need looking at badly. The very thin layer sticks out far too much, support blocker doesn't remove them either. 

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

Is hollowing out models (for SL1) part of alpha 3?

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

Posted by: @area51

Is hollowing out models (for SL1) part of alpha 3?

There is alot of work on hollowing out models visible in the changes appearing in alpha-3. The prereqs are being extended by the modules needed to compute hollowing and also for drainage holes

-- 

Peter

RE: PrusaSlicer 2.2.0-alpha3 tagged on GitHub, but no compilation?

Currently building OK but isn't a requirement for CGAL 5.0.1 a bit bleading edge?

-- 

Peter G4DCP