Adding marks or signs to models?  

Yes in PS 2.4 (currently in alpha). 

As well as the simple shapes built into PS in 2.4 you can add extra shapes of your own design into the library.  That combined with the new add negative volume allows your shapes to act as a 'stamp' so you can mark your parts.  The examples in the gallery contain a recyclable symbol (as that was one of the original use cases that drove the request).  However as you can load any shape of your own design into the gallery and use it you could add letters and numbers and then use as you want.

Another simple thing I've done is to add one, two, three etc small mouse ears to the model in PrusaSlicer. Basically a small single layer circle. Of course you have to remember what one, two or more ears mean in terms of variants you created. 

Adding marks or signs to models?

Right, I am waiting for 2.4 to get out of alpha for other options too 🙂

In meanwhile I found about negative volume option on my own but not in actual version. That will be cool feature.

RE: Alpha3 just for this

FWIW You can have both 2.4 Alpha3 and whatever version your're running installed at the same time. Why not try the Alpha3 just for this slice?

No Need to use an alpha for this

@pedja

This is not a new feature, and has been possible (and very simple to do) in slicer at least as far back as Slic3r PE 1.41.0.

It's as easy as loading your project, select the object you want to mark, then add a modifier, choose to load the marking you want, choose the property to modify "infill" and set it to ZERO and it will deboss / stamp wherever it intersects the model.

Before slicing it looks like this.

This example was produced in Prusa Slicer 2.3

the feature added to alpha 2.4 simply added a button for it and a slightly improved math function, you still have to create your texts/Markings whatever they may be and load them, exact same result. it's not worth moving to an alpha software for this. as well, you can still use the other versions of slicer to Emboss and there is no button for it in. super simple process.

Good Luck

Swiss_Cheese

Correction

I forgot a setting in my example, the modifier will look like this.

I realized after posting that the example I was using already had these settings changed.

I was in a hurry and missed mentioning them.

Regards

Swiss_Cheese

Marvelous!

This is great! Will try it as soon as possible! Thanks!

Posted by: @swiss_cheese

It's as easy as loading your project, select the object you want to mark, then add a modifier, choose to load the marking you want, choose the property to modify "infill" and set it to ZERO and it will deboss / stamp wherever it intersects the model.

True but, it's not obvious whereas add negative volume just seems "right".

@towlerg

It's not my intention to chastise.

I will agree that Negative Volumes are a welcome improvement, and a superior tool to the method described above. However if we're going to use words like obvious and phrases like Just seems "right".

I'm going to have to answer that with, the method described above got me through years of doing what the OP asked for, without much fuss, and it's "obvious" to me that we shouldn't be pushing an "alpha software", or even a beta, at users when we have no idea of their experience level and frankly the problems that still exist in the software. If they are using it professionally we might expect that they understand the risks, it just seems "right" that we use caution and not just recommend the alpha, or the up coming beta, because we are all excited about it. Maybe it would be better, if we saw that there was no other reasonable way to do the thing being asked, and Use discretion when making suggestions. especially if there is already a known way to accomplish the goal.

just my opinion.

Regards

Swiss_Cheese

Some interesting ideas, but marking after printing is foolproof

Posted by: @pedja

[...] But then issue is, if changes are subtle or hard to notice visually, it is hard to distinguish which print is which.

I've encountered this frequently. I did futz around with modeling in markings (dots or holes) but over time, a sharpie applied before removing from the plate has proven to be the simplest solution. 

Is there way to add some mark on each part in slicer to make them easy to recognize?

Embossing is a neat idea, but then it may interfere with the very thing you're trying to test. I suspect an OctoPrint solution might work. If the bottom is not important, simply printing a letter, digit, or other marking in each print position would work and not be dependent on proper arrangement in the slicer.

...

I've encountered this frequently. I did futz around with modeling in markings (dots or holes) but over time, a sharpie applied before removing from the plate has proven to be the simplest solution. 

I used white covering pen. But, as I was unable to write on top of the part, I had to be careful when removing, to remove one by one and instantly mark it.

it's "obvious" to me that we shouldn't be pushing an "alpha software"

Point taken. Especially where the Alpha/Beta would circumvent the release version.

Just so long as you're willing to let others do all the hard work

Posted by: @towlerg

it's "obvious" to me that we shouldn't be pushing an "alpha software"

Point taken. Especially where the Alpha/Beta would circumvent the release version.

Provided you're willing to pass up on the opportunity to contribute to making the slicer do what you want it to do, sure. Input from the community is vitally important to open source projects like PrusaSlicer. One of the most useful contributions we can make is to flag problems and provide feedback early in each development cycle. 

You don't have to switch over to an alpha or beta release completely to test a few things and provide feedback. If a new feature is doing something you might find useful, providing feedback will help improve the product and catch problems before a release.

Just so long as you're willing to let others do all the hard work (way to lay on the guilt Bob)

Provided you're willing to pass up on the opportunity to contribute to making the slicer do what you want it to do, sure.

It's not one way or the other, and there is no shame not wanting to be such a person. If your willing to experiment with the alpha or the beta that's fine. If your not wanting to deal with the potential of problems in these very early releases or knowing how they may effect your current project, you should be given the opportunity to know that there is another way and that you don't have to subject your projects to other unknown potential failures to achieve the results your looking for.

Input from the community is vitally important to open source projects like PrusaSlicer. One of the most useful contributions we can make is to flag problems and provide feedback early in each development cycle. 

This is very true, and there are many of us doing exactly that. It is my contention that this should not be viewed as and invitation to to throw the suggestion of alpha or beta software at every question posed by a user of this forum, It would be far more responsible as a responder on the forum to offer the known stable method or response to help with an issue then to imply that the fix is to use an incomplete version of the software. Now, if there is no other way known or even just as a suggested alternative to the known method, we might say for example ( you can do this like this. however if your willing to try the alpha/beta it has this feature that makes (whatever the thing is) easier, and if your not apposed to using an alpha you might consider trying it. 

Regards

Swiss_Cheese

No

Posted by: @swiss_cheese

Provided you're willing to pass up on the opportunity to contribute to making the slicer do what you want it to do, sure.

[...] It is my contention that this should not be viewed as and invitation to to throw the suggestion of alpha or beta software at every question posed by a user of this forum

Uhm... what? Mentioning an upcoming feature that is likely to be released within weeks is hardly putting anybody's anything at risk. Just mention something is alpha, beta, or RC. Most people technical enough to be into 3D printing are capable of understanding what pre-release software is and can decide for themselves. You're welcome to your own opinion, but do not go calling out others for mentioning capabilities that are on the way. No gatekeeping is desired. The mods decide what's inappropriate here. 

It would be far more responsible as a responder on the forum to offer the known stable method or response to help with an issue then to imply that the fix is to use an incomplete version of the software.

It is far more responsible to assume that people asking for solutions appreciate seeing all of the available options and choosing for themselves without condescension. If they don't like pre-release versions, they can decide not to use them, even without parental consent. If nothing else, knowing that a feature will be released soon is helpful.

Now, if there is no other way known or even just as a suggested alternative to the known method, we might say for example ( you can do this like this. however if your willing to try the alpha/beta it has this feature that makes (whatever the thing is) easier, and if your not apposed to using an alpha you might consider trying it. 

Considering the degree of complication associated with some of these alternatives -- often not officially supported -- I disagree. Learning a hack which itself may go away or change in functionality can waste a lot of time and effort.

Mention that software is pre-release. No warning labels or disclaimers are required. We all learn from each other.

You'll get over it.

Posted by: @bobstro:

Mentioning an upcoming feature that is likely to be released within weeks is hardly putting anybody's anything at risk.

That's very kind of you to decide for everyone's well being. especially since it pertains to something that's "likely" to be released in within weeks!

Well, that changes everything, here take this pill it's weeks away from clearing testing, you'll be fine, trust me. Yeah, now that you say it that way, it all makes sense.

Clearly you have everyone's well being in mind with that statement. 🤔 

If only it was that easy, not everyone has the ability or desire to use an untested software, even those that are technically savvy. e,g, many companies will not allow the use of alpha software,(there's a reason for that) and yet they need the ability to do things exactly as the OP requested in this thread. many companies, and their employees use this software and, they come here for advice.

Also posted by: @bobstro:

Just mention something is alpha, beta, or RC. Most people technical enough to be into 3D printing are capable of understanding what pre-release software is and can decide for themselves.

and I think it's cute that you feel you can make the statement for most people. Especially those that come here asking questions and don't know.

Another post by: @bobstro:

You're welcome to your own opinion

Thank you Bob for allowing me that, regardless of your desire to dispute, and the "but" following the statement. 🤣 it really helped validate the welcoming 👍 

Yet Another post by: @bobstro:

but do not go calling out others for mentioning capabilities that are on the way. No gatekeeping is desired. The mods decide what's inappropriate here. 

That's good to know Bob, because it sure does seem like your not only "gatekeeping" with these statements, but also like your deciding whats inappropriate for everyone else, again Boss move 😉, I hope this works out for you in the office.

Oh No, Not Another post by: @bobstro:

It is far more responsible to assume that people asking for solutions appreciate seeing all of the available options and choosing for themselves without condescension. If they don't like pre-release versions, they can decide not to use them, even without parental consent. If nothing else, knowing that a feature will be released soon is helpful.

I believe what we have here, is a term you used in a previous post we were both involved in. "violent agreement" 🤪 

Just One more post by: @bobstro: for good measure.

Considering the degree of complication associated with some of these alternatives -- often not officially supported -- I disagree. Learning a hack which itself may go away or change in functionality can waste a lot of time and effort.

Mention that software is pre-release. No warning labels or disclaimers are required. We all learn from each other.

 

Now this is interesting, I know from previous posts that you don't like to push more buttons then you have to, so I understand, (whatever suits you) however, I do not agree with your position on "degree of complication associated with some of these alternatives" in fact sometimes there are no other alternatives. especially if the company you work for won't allow the use of alpha/beta etc,etc, software.

It's also interesting that at this time you choose to use the word "hack" to describe common workarounds used in slicer, I guess it helps make your point sound more authoritative?, if feel you needed that it's fine 👍 . we'll go with hack. The "hack" as you call it in this case has been used, and recognized as the way to get the job done for years, but your right!, it's going away, well it's not going away, but there is an up and coming tool for it.

A quote from the alpha 1 Documentation: ( I assume it was written by someone at Prusa)

"PrusaSlicer newly supports "negative volumes" to subtract pieces of geometry from a model #4920. While there was a way to achieve a similar effect by setting zero number of top / bottom layers, zero perimeters and no infill in earlier versions, the new "negative volumes" are much easier to use and they are processed faster and the old workaround"( <--please replace the word  workaround with "hack" for the sake of this conversation). Clearly they didn't know 🤨 or was it you who didn't know?

Me personally, I'm pragmatic, I do what it takes to get the job done, oh and guess what? I'm one of those guys that can't use alpha, beta, RC's at work so I'm stuck with finals, and finding ways to make them work, and as you mention Bob, "We all learn from each other." Great quote BTW 😎 , and that may just mean having to push a few extra buttons to get what we need.

We all work together to find the answers we need, and we all make mistakes and we call each other on our mistakes for the greater good, and "normally" folks around here are amicable, it's best if it's kept that way.

I feel my statements where fair and reasonable, I didn't here anyone calling for Daddy, but there you were.

Thanks for allowing me my opinion, I still love ya 😘 

Enjoy

Swiss_Cheese

P.s.

True story 🖐️ 

Bob, you might find this funny, I most certainly did, I had dinner guests over tonight, and was introducing then to the printer and the forum.

the first post I clicked on was your,

Just so long as you're willing to let others do all the hard work

post. My friend was leaning over my shoulder reading what you wrote, and he said "Man that guy would give my mother a run for her money, and we're Jewish." 😳 .

RE: Adding marks or signs to models?

Hi @swiss_cheese. My name is Henrique, I live in Brazil, and I started using prusaslicer. I'm new to this. Could you explain step by step how to do this? or point me to something or someone who can explain it to me. I know how to add the modifier, but I don't know how to add the text. Thank you very much!

RE: Adding marks or signs to models?

@henrique-nascimento

You will need to create the text in a 3d modeling program, whatever modeling program you use will be fine. then export the model of the Text out of your 3D modeling program as a .stl or .obj file format, you can Import that file into PrusaSlicer like any other model, then change its type to a modifier, or a  negative volume in slicer.

I hope this helps

Swiss_Cheese

RE: Adding marks or signs to models?

@henrique-nascimento

if you need further information feel free to ask, ill help where I can.

Regards

Swiss_Cheese

P.s. It was  a busy afternoon, so you got the short answer.