Procedural Stochastic Texturing prototype

This work in the HDRP terrain ?

 

can anyone please update this to the newest, (2020.3.20f1)? Cannot find another free way to do this.

 

https://openupm.com/packages/com.needle.stochastic-texturing/

 

I'm a bit clueless with this kind of thing @rz_0lento please could you give me a step by step on how to use this. I read the instructions from the github link in that article, but they're speaking complete gibberish to me.....

I have an existing HDRP/Lit shader with textures in for albedo, normal map, height. What do I do with these get the stochastic from the link working and assigned into my HDRP/Lit shader?

I can load a custom package from a single git line in paqckage manager. But this here is complete gobbledygoo to me: (not to mention what I do with it when it is installed)


I only have these options:

 

You need to add scoped registry manually if you use OpenUPM. You can also install this package through Needle's git repo here (see the last part of the instructions on their readme):
https://github.com/needle-tools/procedural-stochastic-texturing

 

Thankyou! will try and get it working soon.

 

This might be asking too much, but could you provide some instruction with using openUPM and adding this? All good if you can't. I will just spend another week fumbling through what should be a simple thing... Cheers.

 

@dannyr83 there are step by step instruction already: https://openupm.com/packages/com.needle.stochastic-texturing/#modal-manualinstallation (you may need to refresh the page if the link doesn't open the instructions first)

 

alright, thanks heaps mate. Ill work it out and let you know if it worked.

 

The git link they gave to add in package manager from git url, doesnt work for me:
"https://github.com/needle-tools/procedural-stochastic-texturing.git?path=/package"





Now what?

 

I also tried that:


But then I get this:

 

Ah apologies guys, I forgot a comma (,) after the dependancy.....

 

I really wish somebody can just make a Youtube vid of this. I'm reading the instructions, but its like reading gobbledygook!

This doesnt mean anything to me:


This is so annoyingly frustrating!

 

You need to have commandline git installed for the package manager's git support to work.
As for instructions, they are step by step... I don't know what more one could expect

 

I got as far as that (done all steps in red). Stuck from blue onwards:


now connect the asset node. What Asset are they talking about???


...and then next "connect uv as usual". There's a USUAL??? I've never doen this so please be more specific in the instructions and assume some of us has not used Unity for 50 years.

 

In a way its good I got stuck as I just noticed that:


Seems then I'm stuck with the crappy "simple" version.

More the reason Unity should get on with it and implement proper solutions natively in Shader Graph

 

Ah I give up!
If it's not one thing, then its a"bloody"nother!

 

One of the things about using that editor is the lack of tangible error handling. Personally, this was one of my fave texture things ever.

 

I am having the exact same problem...sigh...

 

Thanks for all your help man, but it doesn't work. shader error undeclared identifier same as new guy above. any ideas how to fix?

 

It's probably some SG change on recent Unity version, haven't tried it myself there.

 

@newguy123 I am jumping ship to Unreal they don't have this problem(and many others), had enough of all the technical problems, and obsolete tutorials.. Just want to make a game...

 

@rz_0lento Hi! First of all thanks to have updated and supported this amazing (dead) project.

I'm trying the package i've pulled from your git with unity 2021.2/URP and, at the beginning, it seemed to work fine despite of some shader errors in the console. I don't know why but, after reeboting unity, the shader broke totally adding the classic pink error color on my meshes.

Do you have any clue about that? Do you have any plans to update it to 2021.2?

Thanks in advance for your reply and best regards!

 

Unity guys, why did you let this thing die?

 

You could always use Microsplat Texture Clusters. It works on all pipelines. A 1-click solution and I'm quite happy with it. Been creating a new scene this weekend. Here's with only 1 terrain texture.

Stochastic Texture Clusters Off:



Stochastic Texture Clusters On:

 

Off-topic, but that's a very beautiful scene. Is that a publicly available water asset?

 

Crest Ocean HDRP. Also available for URP and free for Built-In.

 

As I understand it the argument would be twofold. Performance and the new pipelines.

I used this to death. I feel the same but it is what it is.

 

What if I dont have actual terrain, but my terrain is a large mesh? (or even small mesh). Is that still a 1-click solution @Rowlan ?

 

Omg, it pains me to see so many people having trouble getting this to work.

I implemented this into my games, so you can get it here:

Unity Procedural Stochastic Texturing Node for Shader Graph
Unity Procedural Stochastic Texture Terrain Shader

It's the simple version, without the color correction, because the full one is very difficult to implement, and I saw above that there is a problem with the "Linear" color space. The simple version is also more performant.

I implemented this also in GTA San Andreas, many people with weak PC ran it and no one complained about performance issues, it really is a great solution for texture tiling.

btw, I'm not a shader guy, so don't ask me to do crazy things on top of it.

 

Thank you @Junior_Djjr. Could you please show a Shader Graph capture using your Custom Function? I'd like to know how to configure Inputs and Outputs, cause I cannot make it work in Unity 2022.1.4f1. Thanks!

 

I know this is a bit old, but it comes up in the google search for stochastic texturing and I thought people might appreciate an answer to the above question.

I got @Junior_Djjr stochastic node working in Unity 2022.2.1f1 by doing the following.

1. Open up the hlsl file "StochasticNode.hlsl" in visual studio (or whatever you use for editing scripts)
2. Edit the line that says:

void Stochastic_float(TEXTURE2D_PARAM(tex, samplerTex), float4 UV, out float3 Out)​

and change it to this:

void Stochastic_float(UnityTexture2D tex, UnitySamplerState samplerTex, float4 UV, out float3 Out)​

save and close.

(Don't ask me why these values have to change... I just followed the hint in this thread).

3. Open up shader graph, make a custom node, add the "StochasticNode.hlsl" to the Source input
4. Set up the inputs as follows

Precision Inherit (If you're using the node in a subshader this should be 'Single' not 'Inherit)
Preview Inherit

Inputs
tex Texture2D
samplerTex SampleState
UV Vector4

Outputs
Out Vector3

Type File
Name Stochastic
Source StochasticNode​

The node should be functional and not show an error..

I implemented this here.

 

Comment utiliser StandardStochastic sur Unity LWRP ?

 

Can't this be added to the Shader Graph as an official node? I mean, it seems very useful so far. And it works.

 

La solution ci-dessus est pour URP (LWRP). Essayez la dernière version.

 

Hi, I'm completely new to the shader graph, I did everything you mentioned here. The errors are gone however the node just outputs a solid color (I connected a texture). That's probably though because I don't know how to implement it. I would use your terrain shader however I'm working with spherical planets so that's not an option.

Can you please go more into detail with shader graph implementation and how to connect everything so it gets the desired output?

 

Not sure. What you said should work. Are you inputting UVs or not. If not you can try to input the world position or similar.

Also, something like this may be what you're looking for: https://forum.unity.com/threads/simple-stochastic-planet-shader-free-on-github.1413297/ It's a planet shader I made that uses the stochastic shader.

 

I've seen your planet shader and while it's great, I'm currently trying to texture the planet upclose, so the ground looks interesting when you land. Anyways, I've got the stochastic shader to work, I just deleted it and did everything again, so I must have made a mistake the first time. Interestingly, when I disconnect the UVs I get the same dubious result from before so that must have been the issue, as you said. Thank you so much anyway!

 

please add this back to Shader Graph for newer version.