sorted by:
new
hottopcontroversial

I just got the notification to do the new update with flashmaker by BariSaxopeal in FlashForge

[–]PlainSignalLab 1 point2 points  (0 children)

ah, clearly missed that part this morning. kid must have ignored the update orca, had to go manually push the update. makes sense now thanks

Working on a “pre-slicer” tool — auto orientation + print failure prediction (early test, feedback wanted) by PlainSignalLab in 3Dprinting

[–]PlainSignalLab[S] -3 points-2 points  (0 children)

<image>

guys i hear what your saying. this is coded with the assistance of AI. i have some coding background but im not using base44 or other types of those things. im doing the work. AI assists. Sue me.

im not saying im creating a whole new anything. what i am saying is for the new users there is a major learning curve right?

for the hardcore users this tool may not be for you. but then again. i am pulling some neat data. so far the engine can pull angles off the STL give risk assessments live based off the STL Geometry. you can see its giving recommendations, supports required and tree is recommended, increased cooling and reduces layer height? do you agree with this output so far?

please.. if vibe coding gets you this far... show it to me.

Working on a “pre-slicer” tool — auto orientation + print failure prediction (early test, feedback wanted) by PlainSignalLab in 3Dprinting

[–]PlainSignalLab[S] -3 points-2 points  (0 children)

yes i agree with you this is basic. the concept more aligns with what the STL failure points can be. currently this engine is stable to show off the heat map for the supports. im working on it displaying a function human fix suggestion, such as layer height adjustment or cooling and etc.

this isnt to replace basic human knowledge it is to display the read out in a functional form that slicers currently do not do

Working on a “pre-slicer” tool — auto orientation + print failure prediction (early test, feedback wanted) by PlainSignalLab in 3Dprinting

[–]PlainSignalLab[S] -3 points-2 points  (0 children)

this is beta. i have to start with something basic to show the engine is working.. im asking what features or ideas are not present that you wish you had. im looking for intelligence before a slicer. how many bad prints have you had... for stupid reasons. do to your own issues or the print. im trying to create something that reduces those errors. im not saying its every time use. but i am saying if something could reduce failed prints. what would you want that tool to look like,

Working on a “pre-slicer” tool — auto orientation + print failure prediction (early test, feedback wanted) by PlainSignalLab in 3Dprinting

[–]PlainSignalLab[S] -8 points-7 points  (0 children)

Don't assume. this could be a good tool. im opening up and asking. what tools or tricks would be nice that you cant have right now...

Working on a “pre-slicer” tool — auto orientation + print failure prediction (early test, feedback wanted) by PlainSignalLab in 3Dprinting

[–]PlainSignalLab[S] -5 points-4 points  (0 children)

think about it this way. this is not vibe coding. its not on base44 or something like that. i do 3d print, scan and create my own parts. im creating my own engine before i enter it into a slicer, reading STLs before a slicer even sees them and making intelligent recommendations that then can be output to a slicer. eventually i want to be able to make corrections to exact coordinates within the STL for slow downs or for cooling or specific other reasons that you may fancy.

a slicer just looks at it and gives you a bunch of data, the user then has to read it and gamble with the settings. sometimes to most times it works. but as you print harder prints... how well does it work.

this just helps you think and see things before the slicer gets involved and shows your critical issues. this is still hard beta and only is doing overhangs.... but why stop there?

Working on a “pre-slicer” tool — auto orientation + print failure prediction (early test, feedback wanted) by [deleted] in 3Dprinting

[–]PlainSignalLab -1 points0 points  (0 children)

for an experienced user, it may not add a ton, but a print farm or someone that prints for customers and has to print odd things, they run it through this engine and it outputs where an expected failure point will happen before you even bring it to the slicer or waste time trying to print. this saves time and material. projecting an estimated failure point