Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3D Noise functions only make use of two coordinates. How to make them actually 3D? #16

Open
bluegreen1024 opened this issue Apr 30, 2023 · 6 comments

Comments

@bluegreen1024
Copy link

The 3D noise functions, such as the 3D simplex noise, 3D fractal simplex noise, etc. seem to only use the first two channels of the uv, period, and offset/shift vectors. I thought the purpose of a 3D noise function was to take 3D position input and give smoothly varying scalar output. Am I misunderstanding how these are used or is this a bug?

@bluegreen1024
Copy link
Author

I just saw in another thread that this plugin is meant to be 2D only. Thus I am now very confused by how the 3D and 4D functions are meant to work, and what their use case is. Apologies if this led to an off-topic issue report.

@arkology
Copy link
Owner

arkology commented May 3, 2023

@bluegreen1024 I think you could provide (x, y) vector to "uv" input and z scalar to "z" input and it will work as expected.

@eobet
Copy link

eobet commented Jul 28, 2024

I think you could provide (x, y) vector to "uv" input and z scalar to "z" input and it will work as expected.

Sorry, but since I see a "time" input even on the 3D noise, I also find myself in a bit of a confused situation for when to use 3D and 4D. What's the difference between time and offset?

(And for the record, I also want to use this for a 3D game and I'm hoping this can provide non-repeating variation in vertex shaded meshes on outdoors locations all the way to the horizon.)

@eobet
Copy link

eobet commented Jul 29, 2024

@arkology could you please see if you can tell what I'm doing wrong from this screenshot here?

Screenshot 2024-07-30 191234

screencast-gnome.mp4

I'm using local vertex coords, but still feeding node world pos into offset should get me a new "seed" per instance, but it only works for X and Y, not in the Z axis...

@eobet
Copy link

eobet commented Aug 10, 2024

Damn... I just noticed that if I use world vertex coordinates, and then rotate the tiles, the vertices no longer line up, which seems to imply that there's still some local calculations going on somewhere... but where?

image

I'm willing to pay to have this fixed, btw.

@arkology
Copy link
Owner

arkology commented Aug 11, 2024

@eobet sorry, actually I know nothing about 3d stuff so can't help you. Last time I checked it worked fine in 2d. I literally don't have enough free time and knowledge.
But if you find proper fix (or find someone who can fix it), I would appreciate any PR☺️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants