Suggestions for improvements - PrusaSlicer  

RE: Suggestions for improvements - PrusaSlicer

A couple of years, thanks Prusa forums and word press.

RE: Suggestions for improvements - PrusaSlicer

Posted by: @swiss_cheese

LOL, @ Cura

I did notice cura finally figured out about adjusting extrusion widths, I haven't tried it yet, But I hope they did it right. It's been years in the making that some developer finally figured this out. It would be great if I didn't have to do this manually after all these years. Even if the algorithm did most of the work and I only had to make adjustments to it, that would be game changing, it takes a lot of time to do it manually. I  suspect they will have a couple of tuning to do, before they can do it as well as I can manually though.

 

More power to you Cura, it's about time.

 

Swiss_Cheese

Yes, I saw that announcement a few days ago too, but as you, I have yet to download the Latest And Greatest and try it out.

I have a feeling that it will work great on the Ultimaker, but may produce so-so to totally unusable results on the Prusa.  I remember when they came out with their highly-touted ironing, the results were best described as butt-ugly on prints done on the Prusa.

Overall, I think PS performs better on the Prusa than does Cura, and if I would dork around and get PS working on the Ultimaker (I have been told that it can be convinced to run Marlin style gcode) I have a feeling that the results would be inferior to Cura.

RE: Suggestions for improvements - PrusaSlicer

I've used all of this software, and while I don't have an Ultimaker S5 to play with currently, I don't believe from my experience, that the software locks you into any particular hardware, I've been able to use both with success on several different printers. I prefer and have stuck with Slic3r/ PrusaSlicer  as I have stuck with and helped develop several 3D software packages in my life, now mostly owned by Discreet/Autodesk. that said I have a tendency to stick with one in my life, however I must confess Prusa is seriously, starting to change my mind about this, they seem to be going with the opinions of users that don't know how to to use the software and even more so don't seem to recognize what the software they have can really do. The sad thing about that is this will diminish its capacity.

As I mentioned before I'm already looking for it's successor in the form of some other software, I see this going towards the use of the newbies, and being developed to the point that I wont even be able to use it for professional work anymore.

Regards

Swiss_Cheese

RE: Suggestions for improvements - PrusaSlicer

Have you thought of taking the source code to PS and making your own tweaks?

RE:

Yes I have actually coincided that, unfortunately my life doesn't currently allow for the time to do this, I'm not retired, yet. And I develop product for paying clients for a living and have quite a few employees.  I would even have to keep up with current developments, however that said PS 2.3 still meets my needs for work, I only keep up with the 2.4 series to help out here and, frankly that is becoming less frequent because of the type of user that seems to be attacked to this software.

I'm sad of this.     

RE: Suggestions for improvements - PrusaSlicer

*considered* I really hate the edit time here.

whatever Prusa doesn't care.

But I'm sure you get it.

Swiss_Cheese

RE: Suggestions for improvements - PrusaSlicer

Back before I rebuilt the machine I use mostly (it was Ubuntu 16) I downloaded the PS bundle and gave a quick shot at a build, but there were so many dependency issues and version issues that I just said the heck with it.

It's now Ubuntu 20, fairly recent install, so I may give it another shot when I have some time.

I asked here and on 'another network' if those who successfully built it on Debian/Ubuntu if they would please share the versions of the various packages they use (just something like 'apt list', nothing heroic or difficult) but got crickets.

RE: Suggestions for improvements - PrusaSlicer

I want, almost to badly for an active community here, and I feel let down every time I strive for it, I used to help develop software like this on IRC. I worked with guys like Alan McKay just a kid when I met him, and several others developing software for 3d particle development and fluid development as well as other now considered very basic stuff. I'm no fool, I can show people to this day, how to do things they didn't even know where possible in this software, they think they developed, and frankly it feels so disrespectful how this is viewed, that my take on it is they can go fuck themselves, if they won't listen to what I have to say, it's a long road before the current developers of this software know what I know about it, so fuck you devs. learn it yourself's. I will literally show any body but you what I already Know about the software you developed, I've wasted so much time on GitHub trying to clue you in, piss on you. No time save it for the next version right?

Anyway, to bad so sad, Who cares,  Right?

Swiss_Cheese

RE: Suggestions for improvements - PrusaSlicer

@Swiss_Cheese

On 21/01/2022 2:54 am you posted a similar, however a significantly more civil complaint than the one above:
https://forum.prusa3d.com/forum/prusaslicer/prusaslicer-and-feature-requests/paged/2/#post-567586

I responded on 21/01/2022 7:32 am

> I am sorry for your dissatisfaction with the work of my team. Would you please share your github user name, so we can re-evaluate your gripes that you have reported on github?

You did not respond to my request. Did you miss my request, or are you just not interested in solving your problems?

I strongly believe the world would be a better place if people used their real identities on Internet. I am sharing my name. Would you, Swiss_Cheese?

RE: Suggestions for improvements - PrusaSlicer

For those who care, or would like to try it on a similar system (Ubuntu 20.04.3 LTS), I just downloaded the source for PS 2.5.0 Alpha 0 and it built successfully on this reasonably current Ubuntu install on the first attempt. I'm playing with the executable now, which appears to run fine.

Next time I need to slice something for the Prusa, I'll try it.

For comparison purposes, I may try downloading the latest Slic3r and see if it builds as well.

The last time I tried either/both, which was in the darkest parts of the pandemic, both failed with multiple version issues on the 16.04 Ubuntu.

RE: Suggestions for improvements - PrusaSlicer

Update, I had to re-print a slightly modified test jig, so I figured it's as good a test as any for the new PS 2.5 alpha built on the same machine.

Only difference I noticed is that somehow it detected that my print looked like it may be a sign, and asked if I would like to enable auto color change.  It is not, and I declined.

It printed, as expected, same time as a previous version (19 min) and looked the same, Hatchbox ABS, MK3s.

RE:

@vojtech-bubnik

I will not share my GitHub ID. I have in fact spent a great deal of my personal time making post with regard to my experience with the software, and I am not in a position in life where I can share my ID. I make my living developing product (IP) protected product, for clients and the issues I've been having are based on the specifics of those products in development. I personally have developed methods using the altered states of Slic3r, to get our work done, I made my best attempt to give what I considered to be pertinent information. This is how I make my living and your software is not the most impotent thing to me, I tiptoe on eggshells posting here, I'm not some hobbyist. I made the choice several years ago to use Prusa Printers I3 MK3's to take part of the load we, my engineers were dealing with in our Que, to help reduce the latency in our product development.

It worked, it did that. I have taken it upon myself to help and share that information, with users here, and I even took some of this to GitHub to hopefully help and share, I was not at all pleased with my experience there. I'm sorry you feel bad about that, if you really do, you shouldn't. The  product as it stands is moving along.  Others can do what they want, and once again I will say I was sharing my experience with acquaintance here on the forum, I was in no way looking for your response. Just to be clear I am not looking to fix anything outside of the realms of what Prusa decides they want to, I can make slicer do what I want, and have been. I was trying to help and it didn't.

you have no need to contact me or address me in anyway, I can't help you.

Thanks for reaching out.

Persons such as Bobstro can pick up the slack, if hes able.

RE: Suggestions for improvements - PrusaSlicer

@Swiss_Cheese

Frankly I don't understand your attitude. You claim you described your woes on github, however you don't want to share your github user name. There are 2010 open issues on github. The day has 24 hours, we are not Microsoft with their overstaffing and we have our personal lives as well. We need to prioritize, however we may re-prioritize based on the feedback. It will help if you share your github nick or the list of your github issues.

RE:

If I may jump in here. ...

First of all, I think some of this may be communications issues.  All of us have to remember that the users here (both customers and Prusa staff) have different languages of nurture, and nuances concerning thoughts and feelings are  often times not understood or misunderstood.

Now having said that, one thing I have noticed and will agree with, and will present to Prusa as an 'opportunity for improvement' is the fact that the developers (apparently) keep mostly to themselves and do not regularly participate (or at least post) here.  Yeah, I get it, it's not part of their job and every minute spent here is one less minute for 'real work', but like it or not, this forum is the primary customer-facing tool for Prusa, both in terms of current customers and potential customers.

Lots of the good and bad 'vibes' (for lack of a better term) from the customer base and the company are expressed here.

What I might suggest for Prusa is some more active liaison between the development side of the house and the customer-facing side of the house.  Yes, I know that it would take staff time, which translates to real money, but I think it would be cost-effective at least in terms of existing customer satisfaction as well as good will toward potential customers.

RE: Suggestions for improvements - PrusaSlicer

@jsw    Point taken but on any given day the number of posts relating to Prusaslicer is small. I imagine most engineers would spend more time looking their email than looking at the few nicely compartmentalized Prusaslicer posts.  I'm guessing that Vojtěch Bubník is a Prusa staffer, so maybe that's policy anyway.

RE: Suggestions for improvements - PrusaSlicer

Our team is growing continuously. We started 6 years ago with just me, now we have 8 developers, 3 testers and one 3D printing expert on our team.

I used to do all the communication. Nowadays four people are taking rounds on github issue tracker, which is our main communication platform.

We also hired a project manager, who should join us this summer.

RE:

If it's not possible to make tree-shaped supports, wouldn't it be possible to make them diagonal? Like in the image

RE:

Posted by: @manelto

If it's not possible to make tree-shaped supports, wouldn't it be possible to make them diagonal? Like in the image

Although I have not done it in PS (I have used a similar function in Cura) you could simply design the shape of your support material, any arbitrary shape, using your favorite drafting program, export it as .stl, and then load it as a 'support enforcer' when slicing your model.

RE: Suggestions for improvements - PrusaSlicer

Posted by: @jsw

Posted by: @manelto

If it's not possible to make tree-shaped supports, wouldn't it be possible to make them diagonal? Like in the image

Although I have not done it in PS (I have used a similar function in Cura) you could simply design the shape of your support material, any arbitrary shape, using your favorite drafting program, export it as .stl, and then load it as a 'support enforcer' when slicing your model.

IIRC it's possible to spoof PS into generating tree supports by pretending to be an SLA printer, I've never tried it.

RE: Suggestions for improvements - PrusaSlicer

yes, I know that there are alternative ways to what I ask. But it is not about that, this thread is to suggest improvements or additions to the program. That's what I do, that I don't need to use another program, export what I did with that other program and finally work with PS. I would prefer that in a simple way, the PS itself would allow what I suggest.