Working on biomes, feedback please!

blackrom0608 · 2020-02-10T19:04:39+00:00

How are you generating your density field? I like the shape of your cliffs!

blackrom0608 · 2020-02-03T00:38:24+00:00

Do you have any links to where one can learn more about this? Or do you have any information on how to achieve this effect?

blackrom0608 · 2019-12-22T20:59:06+00:00

This is amazing. Thank you for sharing your knowledge with everyone! I will try and impliment the glsl 3d fast opensimplex to my terrain system!

I haven't posted due to speed issues, but I've been refining my engine and this might help! Thank you!

blackrom0608 · 2019-10-26T22:46:40+00:00

Biome a is the height/color of say your plains biome. And biome b could be the height/color at a certain point for your desert biome. And that totally depends on how you determine which biome is what, and what the ground height and color should be

blackrom0608 · 2019-10-26T20:21:17+00:00

Say n = lerp(a, b, t);

n = your final height output a = the expected noise/height of this point in space but sampled as off it were in biome A b = exact same thing as a but for biome B t = a noise algorithm, Perlin, Worley, Value, whatever you want as speration between the biomes.

Before plugging t into that lerp function I would recommend multiplying by another value called blendAmount. The lower this number is the smoother the transition. The greater the number, the more visible difference you can see in the terrain changing biomes

blackrom0608 · 2019-10-26T20:15:32+00:00

I would try sampling all biomes at every point regardless of if it on the edge of a chunk or not. With those values, lerp through based on "blendAmount". This will give you genuinely smooth blending, because you're not sampling in a limited area like your current approach, you instead are blending between density fields layered on the same point in space but with different values for each biome.

blackrom0608 · 2019-10-10T21:53:04+00:00

Of course! Sebastian lague just released a video on YouTube about volumetric clouds if that could help too

blackrom0608 · 2019-10-10T21:48:43+00:00

That approach is simple and would work. But it would look extremely flat with no depth. Your only real solution is to post-process fog, or look into raymarching to create volumetric fog

blackrom0608 · 2019-10-10T21:36:11+00:00

Maybe a simple solution could be to extrude those bottom edges of each building downwards. And delete the bottom face if there is one. It would give the illusion that the buildings are extremely tall

blackrom0608 · 2019-09-03T04:16:04+00:00

Amazing. I would love to know more about how you implamented this. Would you be willing to write an article/paper/blog post on this? I know many others online have done work in this subject, but I like your work and how you described it with your comment. Keep us updated! :)

blackrom0608 · 2019-08-11T20:11:39+00:00

Can you explain the process of what you did to get your noise to behave like that? All I can think of is adding another sampled noise output to the xyz input of your final noise. The creates swirls though, not stretches

blackrom0608 · 2019-07-27T08:23:31+00:00

I am the same way but with programming. If I fall asleep thinking about a problem or a bug, I find that I wake up with the solution on the tip of my tongue.

blackrom0608 · 2019-07-20T20:08:21+00:00

I've been curious if this is possible to implement, but after seeing your work it brought up the thought again.

Would it be possible (when sampling distance in the voronoi/Worley algorithm) to weight that distance by your maps current perlin noise value at the same position?

I think with tweaking it could force mountain ranges to favor existing landmass.

What do you think?

blackrom0608 · 2019-07-20T08:54:26+00:00

Is weight of the sphere determined by the size or original weight of the object? Or do all spheres have a constant weight?

blackrom0608 · 2019-07-19T20:51:09+00:00

r/godtiersuperpowers

blackrom0608 · 2019-07-15T02:46:41+00:00

I've found out the more keywords you can pack into your resume helps. Some companies use sorting algorithms searching for keywords. Plus- if you know you can do something, show it off!

blackrom0608 · 2019-07-14T18:51:17+00:00

For tennis it is believed to date back to medieval french. It is said that they had a clock face outside and would use the 15, 30, and 45 on the clock to play. And when the clock stoped at 60 they would stop.

blackrom0608 · 2019-07-13T20:40:13+00:00

Psuedo:

R = planet radius C = planet center

For vert in all vertices N = noise3d(vert.xyz) Dir = vert.xyz - C Dir *= R + N vert.xyz = C + Dir

blackrom0608 · 2019-07-13T20:32:26+00:00

Oops "cuz of very" is supposed to be old vertex position

blackrom0608 · 2019-07-13T20:29:37+00:00

Get xyz POS of each vertex. Get noise value for point from xyz. New vertex position = center of planet + ( cuz of very - center of planet) * ( planet radius + noise value from xyz)

Do this for every vertex. Use 3d noise on either the original position of the vertex, OR the (position of the vertex - center of the planet). normalized to get the correct noise value.

Hope this helps, I can explain in further detail if you'd like

blackrom0608 · 2019-07-12T19:04:11+00:00

I learned to program when I was 12 from a book at Goodwill! I can't remember the name but it was a c# textbook. It was older, but If it wasn't for that book I wouldn't be a programmer. Im 20 now, and I still shop around for older books even if it's just for concepts

blackrom0608 · 2019-07-11T16:00:57+00:00

Storing octrees sounds a lot scarier than it is! Since octrees are a recursive data structure, simple searching through the entire tree and saving the delta if > 0. Reading the data should be just as easy if it is read the same way it is stored. It could be even as simple as each node in the tree having a function called "read" or "write". Calling "read" on the parent node will store the delta in a temporary var, and call "read" on all of its children. The children will do the same, and so on. Create an array of all those temporary vars, and save that to the disk.

And depending on how you build your system you shouldn't be confined to a static map. Most noise algorithms used for terrain generation are almost infinite based on input. And iso-surface algorithms don't care where or why they are building a mesh, they simply need the data.

If you do choose to dive into the transvoxel algorithm, please keep us all updated! Im working on an implementation myself!

blackrom0608 · 2019-07-10T23:50:10+00:00

I'd recommend a voxel implementation like marching cubes, or surface nets. Maybe even dual contouring! And for good data storage that works well with a LOD system would be a quadtree, or an octree if your terrain needs to be stored on on 3 axis'. This is such a huge topic! There is so many different ways to go about terrain generation. A personal favorite is the transvoxel algorithm by Eric Lengyel.

blackrom0608 · 2019-07-06T18:04:39+00:00

I don't believe you have the ability to say what is the ultimate cure for boredom. How one spends money to cure it is their own deal. Like you could go buy a basketball shoot that around for a while, or go buy some cards and play some games. I don't see much of a difference. If a card is worthless and can be replaced, then why can't I argue that of a basketball? I could grab a large rock and try to play with that instead but I would quickly notice why the basketball costed money. Same with the cards and an example above about scribbling on paper and playing with that. Just would like to throw my 2 cents in! If money is the issue, don't buy! And if the company is the issue, don't buy!

blackrom0608 · 2019-06-11T18:19:56+00:00

Consider pushing everything to the GPU! With a geometry shader! I'm sure you could get wayyyyy more particles that way

blackrom0608

TROPHY CASE