Somewhat…. but not in a straight forward way, unfortunately. I'd say you can bake two different types of things from this shader in order to use it on a different 3d software. A. You can bake the final texture itself, which would mean that it wouldn’t be able to dynamically interact with lights. B. You can bake the normal, which would mean that it could interact dynamically with lights, but you essentially need to rebuilt half of the shader in said software (in this case unreal) Here’s how you do it (partly copied from another reply, based on the PseudoPainter v2, but can be applied to v1 as well): The simplest way to do it is to bake the texture using the ‘pseudoShader (Cycles)’ , though it won’t give you the same amount of control that the eevee version have. A more elaborate way do it, probably, is by baking the BSDF shader that is connected to the ‘Shader to RGB’ node inside the ‘pseudoShader (Eevee)’ node group, and then replacing the ‘Shader to RGB’ with an 'Image Texture' node of the baked texture. That way, you can render the shader in Cycles and then bake it and export it. If you want to use the ‘B’ method mentioned above, you could also bake the normal from said BSDF.

Hello… If you’re talking about timestamp 11:45 , you just need to add an [Image Texture] node, and then click on the [+New] button. Choose the name and resolution, and choose [Blank] for the [Generated Type]. Click OK. Switch mode from [Object Mode] to [Texture Paint]. Click on the [Image Texture] node that you created and you should be able to paint right away. (Don’t forget to connect the [Color] output of the [Image Texture] node to actually see your painting) What I did to make it look like a ‘painting’ was to connect the [Vector] input of the [Image Texture] with the [Texture Displacement Mapping] output from the [PseudoPainter Pattern] node. if still unclear pls don't feel hesitant to ask more so sorry that my video is really bad and unclear. I learned a lot in this past year and I’ll be sure to try my best to make better stuff

@@barely_art No worries, thank you so much!

If you could upload a video on how to paint the texture just like you did it on 11:45 that would be amazing, again thanks!

here ya go : kzbin.info/www/bejne/fqbLk2h6pq2NeZosi=gjt1WzoNxBzxp6Ty

It might be…? I’m gonna be honest, I didn’t think much about optimization when I made this. Heck, I probably didn’t even understand half the things that I did. So yeah, I also found it can get slow somewhat quickly. From my experience though, I think it mostly came from the ‘pseudoLayer’ node. Since the ‘pseudoPainter’ node already got a heck ton of nodes inside of it, combining two or more of them probably resulted in quite a heavy computation*. I also found that using alpha blending (instead of opaque) makes things quite slow as well. Being aware of that, I’ve been tinkering some more with this shader and have been trying to make it …lighter? Having a better understanding of how the shader nodes work, I can see ways to use less and less nodes in each of the ‘pseudo’ nodes. I hope, in the next version of pseudo painter-which I am currently working on-I can make it even more practical with more features as well. * I also found that things can get slow when I add a lot of nodes in a single material EVEN when those nodes aren’t actually connected to anything.

hmmm…. If it works on default/primitives shapes, but it only shows a single shade of color (not black or grey) on other models, then the first thing I would check is the uv map, since this shader relies on uv map to work

I think all I did was just connecting the 'pDisplacement' into the 'Vector' input of the 'Image Texture'. I only trimmed the video to cut the part when the texture was loading so that people don't have to wait for it. But.... hmmm.... if I were to guess though, the image texture might not work because of the UV map that's being used, since (assuming you use UV for the 'Mapping(1)' input like in 2:00 ) how the image texture is mapped (still) depends on the UV map. Something that I would try to check in order to troubleshoot is to connect the ‘UV’ from the ‘Texture Coordinate’ node straight into the ‘Vector’ of ‘Image Texture’ and see if the image is properly mapped the way I wanted. If not, then I will try to fix the UV map, or even use a ‘Mapping(2)’ node to fix it. After that, I would just connect the ‘Mapping(2)’ node into the ‘Mapping(1)’ input of the ‘pseudoPainter’ node. do let me know if that works (or not) Mapping(1) : an input on the ‘pseudoPainter’ node Mapping(2) : an actual node called “Mapping”

you should be able to just right-click on any parameters and add a keyframe

Yeaaa… this is definitely something that I want to tackle for the next version of pseudopainter. But, as for now, I can think of two ways of baking. First, the simplest way is to use ‘pseudoShader (Cycles)’ so that cycles can render it. Of course, this way you would be limited to the settings on the cycles version of the shader. Second method, a bit more complicated. You need to open the ‘pseudoShader (Eevee)’ node and look for the ‘ShadertoRGB’ section. Despite the mess, it is located on the left side and framed inside a brown-ish/orange frame; so it should be easy enough to find. Connect the ‘Principled BSDF’ straight to the ‘Surface’ input of the ‘Material Output’ node (If you use node wrangler add-on you can just [Ctrl+Shift+Left Click] the ‘Principled BSDF’ to connect it). Bake* that BSDF, and then replace the ‘Shader to RGB’ node with an ‘Image Texture’ node of the texture that you just baked. After that, the ‘pseudoShader (Eevee)’ should be able to be rendered using Cycles, thus, you can bake. Taking things a step further, you can also connect the 'pDisplacement' output into the 'Vector' input of the 'Image Texture' node. It should make the shader looks better, assuming it didn't give out problems instead. You wouldn’t be able to change some of the settings on the ‘pseudoShader (Eevee)’ after you bake the ‘Principled BSDF’, so I recommend to get the look you want first, before doing any kind of baking. And of course, the baking process would bake the lighting into the texture so you won’t be able to change the lighting of your scene. *I use the 32-bit setting on when creating the blank texture. Not sure if that would make any difference ps. don’t forget to check out the ‘v2.07b (Preview)’ . It has additional setting for the ‘pseudoShader (Eevee)’ , though might have some unexpected behaviour.

Yeaaa… this is definitely something that I want to tackle for the next version of pseudopainter. But, as for now, I can think of two ways of baking. First, the simplest way is to use ‘pseudoShader (Cycles)’ so that cycles can render it. Of course, this way you would be limited to the settings on the cycles version of the shader. Second method, a bit more complicated. You need to open the ‘pseudoShader (Eevee)’ node and look for the ‘ShadertoRGB’ section. Despite the mess, it is located on the left side and framed inside a brown-ish/orange frame; so it should be easy enough to find. Connect the ‘Principled BSDF’ straight to the ‘Surface’ input of the ‘Material Output’ node (If you use node wrangler add-on you can just [Ctrl+Shift+Left Click] the ‘Principled BSDF’ to connect it). Bake* that BSDF, and then replace the ‘Shader to RGB’ node with an ‘Image Texture’ node of the texture that you just baked. After that, the ‘pseudoShader (Eevee)’ should be able to be rendered using Cycles, thus, you can bake. Taking things a step further, you can also connect the 'pDisplacement' output into the 'Vector' input of the 'Image Texture' node. It should make the shader looks better, assuming it didn't give out problems instead. You wouldn’t be able to change some of the settings on the ‘pseudoShader (Eevee)’ after you bake the ‘Principled BSDF’, so I recommend to get the look you want first, before doing any kind of baking. And of course, the baking process would bake the lighting into the texture so you won’t be able to change the lighting of your scene. *I use the 32-bit setting on when creating the blank texture. Not sure if that would make any difference ps. don’t forget to check out the ‘v2.07b (Preview)’ . It has additional setting for the ‘pseudoShader (Eevee)’ , though might have some unexpected behaviour.

@@barely_art Thanks a lot. I'll try your methods

i use blender 3.4.1

kalau warnanya bukan hitam/abu-abu tapi jadi polos, kemungkinan masalahnya di UV. Apa boleh minta penjelasan lebih lanjut soal setup dan problem nya?

Of course

Currently, the closest thing to a solution is probably to use ‘pseudoScatter’ . Although, having a custom brush is definitely on my future feature list and I’m hoping to tackle it on the next version of pseudo painter. ps. really sorry for taking a long while to reply

Well.. the simplest way to do it is probably to bake the texture using the ‘pseudoShader (Cycles)’ , though it won’t give you the same amount of control the eevee version have. A more elaborate way do it, probably, is by baking the BSDF shader that is connected to the ‘Shader to RGB’ node inside the ‘pseudoShader (Eevee)’ node group, and then replacing the ‘Shader to RGB’ with the baked texture. That way, you can render the shader in Cycles and then bake it and export it. I’m planning to tackle this problem in the next version of pseudo painter, but for now, that’s some of the only ways I can think of doing it. ps. sorry that it took me this long to reply

Hello! I’ve just added some kind of preview version in the download link (v2.07b). It will have some additional settings regarding color variation. It might not be exactly the same, but it should give you more control over the color variety. Do keep in mind though that this is a preview version and might have some unexpected behavior. ps. very sorry for only been able to reply just now

hello! I’m currently working on the next version of this pseudo painter, and this feedback is certainly on my list of things to improve. It seems that it’s going to be some time until I can manage to finish it, so in the meantime I added some kind of a preview release that’s available on the download link. It will have some additional settings regarding highlight/shadow control but keep in mind that it might have some unexpected behavior. ps. really sorry for the super duper late reply

@@barely_art great! I'll check it out

mind to elaborate, good sir?

yes i think it can!

Assuming 10:00 is not what you meant, I think you want to have the paint strokes to be put on top of an image texture? Please do elaborate more if that’s not what you meant-but if it is, a way to do that is: to use ‘Mix’ or ‘Mix Shader’ to combine the image texture and the paint strokes. It can be done by utilizing the ‘Alpha’ output from ‘pseudoLayer’ as the ‘factor’ input in the ‘Mix’ / ‘Mix Shader’. The ‘Alpha’ output basically acts like a mask, so you can set how much paint strokes you want to add on top of the image using the parameters on ‘pseudoLayer’. Despite having A and B input, the ‘Alpha’ output on ‘pseudoLayer’ can actually be used with only B input connected. (you can also put the image texture straight into the 'A | pColor' on the 'pseudoLayer' without using any mix nodes. The 'pColor' output of the 'pseudoLayer' will then output the result) Again, if that’s not what you meant, please do elaborate more. EDIT : just wanna say, your comment made me realize how i can combine different pseudoShader(s) using the 'pseudoLayer' alpha! Thank you very much good sir!

@@barely_art Thank you so much! This is exactly what I want. I'm glad it helped you, would love to see your KZbin journey.

@@barely_art So i tried your 2nd method and it worked but even though your shader is working fine but the pseudo painter is not working with my node setup. I mean i'm not able to play with brush strokes. can you make a video to show how you would use the image texture with your shader. That would be amazing.

here ya go : kzbin.info/www/bejne/e5yymY13ptl2jZI

@@barely_art damn bro This is just amazing. Now i can finally use it in my next project. Thank you so much. can't believe its free.

aaaaaaaaaaa I just realised I cut the part where I connect the 'toSurface' of the 'pseudoShader (Eevee)' to the 'Surface' of the 'Material Output' nodee!!! (which can be seen in 1:30) Im soooo sooorrryyyyy!!!! .... pls tell me if you did that already and it's still black.

looks so awesome!

does it also work as post process effect? with special gbuffers？

As I said in some other comment, I’m not actually a 3D artist of any kind, and (I think) this is the first time I heard the term ‘g buffer’. Upon doing some light reading, I understand it as some kind of render passes? So if I understood you correctly, you want to have the painting effects as a post process instead of actually having it as a shader? Well, I never had that kind of use case in mind when I made the shader, but I suspect it’s possible. This shader works by creating a mask for each of the highlights, midtone and shadow, which is all affected/driven by the ‘pData’. So if you can get hold of them as a render pass / gbuffer, I think you could “recreate” the painting effect using post process (to some extent). All this shader does is doing some color correction using masks after all. There is currently no direct ‘Mask’ output if you want to render it (to use it as a render pass), although I don't think it's difficult to add (since I do have some new features for an upcoming update anyway). But I pretty much don't know anything about render passes and how exactly they are used in post, so I don't know how you would set up those masks to be an actual render pass (in blender) instead of rendering them manually. But hey, that’s all in the assumption that my understanding of gbuffer is correct and I didn’t misunderstand your question either. or maybe....... I should (try) add a post-process version of the shader as well? ps. soooooo soooooorryyy for replying so laaaateeeeeee!!!

So it affects the base color and the normals right?

I suppose you can use the cycles version of the shader. It won't look exactly the same as the eevee one, but you it does enable you to bake it

Not quite? It uses the “data” from ‘shader to RGB’ node to make different masks for highlights/mid/low. Yes indeed the shader that drives the ‘shader to RGB’ has the 'Normal' modified using the ‘pData’ input, but it’s all just for creating masks. Which is why in theory, you can actually have different textures/colors for each of the highlights, midtone and shadow (or any different values on the mask). So what I did is just combining all the different textures/colors that I have tweaked for the high/mid/low and then porting them to the ‘emission’ socket (so technically it doesn’t actually have a ‘Base Color’). though it works somewhat differently for the cycles version

@@barely_art Thanks l lot super helpful