What's funny is Notch ripped off infiniminer.

@@getgle i though it was called spacecraft

me: makes a pixelated adventure game MC 6 year olds: hey you copied Minecraft eeeeeee

Gta clones?

@@getgle By ripped off, you mean copied. Or your view of rip off is different to mine. I view rip off as an awful copy of a good game.

This is making hiring competent gameplay/engine engineers very difficult, sadly.

@@konstantinkh My guy, you know anything about programming? Guys with 20+ years of experience still google how to do basic stuff in most languages

@@arzr_er There's a difference between not memorizing every API out there and not knowing how to do things. If you are implementing something that requires vector math, it's ok to look up what function/operator performs cross products in your engine/library of choice. In fact, that's expected. What's not alright is not knowing how to compute a cross product if you are writing code that uses them. Same goes for just about every algorithm, no matter how complex - within realm of game development, at least. You don't have to know all the intricate details involved in optimization - though, a good senior engineer will have a domain where they are an expert in these. But you have to understand how an algorithm works well enough to write a simple implementation. Naturally, I don't actually expect this to be the case for a junior engineer, but that should be the goal. That is something you strive towards throughout your career. That means taking an interest in things you are working with and not treating every API call as a black box. Digging into things, figuring out how they work, trying to write our own implementation, even if you know it won't ever be as good as what's already in the library - that's how we get better as engineers. People who don't do that don't get better. And since nobody gets born a good engineer, I can confidently say they never became a good engineer. There is, of course, a flip side to this. Engineers who re-write absolutely everything, because they never learned to search through documentation, the code base, or open source projects as applicable. In my experience, however, that's easier to fix, so it's not a deal breaker in new hires for junior or mid level, in my opinion.

*2020

@@konstantinkh It's in fact okay to look up how to do cross products too. Stop being a gatekeeper. It's much more about how workable the code becomes as it grows, if it scales, if it is readable, if it is modular. You are very right in that doing an implementation is good for learning. But then you misinterpret why. That is because you see how battle tested formulas were written. How they have been perfected on, and the structures that exists in the code, the polished optimization that mathematicians have evolved and then you get to imitate that. It has nothing to do with actually memorizing those implementations. You may look at google for even the simplest of things. It is okay. If you get stuck in the thought loop "Do you know how atan2 works?" "Can you write your own ik solver?" trying to just compare knowledge. Nothing like that is actually useful unless you take away how the structures and flow works. You rarely have to re-write any solved formula or tech. You do however need to study it to learn code structures and flow. You arrive at the conclusion that you need to balance rewriting stuff and not rewriting stuff. But that is actually not that useful, just like @ARZRer mentioned. Every function is already at your fingertips. Being competent is not in knowing the science that went into them. Just how to utilize them. How to structure the code so it builds a good architecture.

Сейм

@@user-ne3sj5xf3j same

I thought it was custom terrain generation in Minecraft.

@@user-ne3sj5xf3j почему мы говорим по русски?

@@martinananas7894 идк бро

Same

Same

Either you stole my comment or i stole yours or it is a total coincidence. I didnt see yours until I posted mine and I don't want to wrongfully accuse you of theft so its most likely a total coincidence.

same

Thank you! Glad you liked it!

@@nova84d Curious to see if you got any further on this? It was nice to watch and I'll be checking out your channel for more interesting content soon!

I was actually in the same boat as you.

So basically "blabla i watched this video now give me likes"

@@gen157 yeah yeah there's like million of you lmao "i DİDnT İnTeaNd To GeT LiKeS" just reading the comment and seeing how made up it is already blows it ya know

I smell letters

I smell letters

Sanpuru tekisuto that’s amazing😂😂😂

@@sanpurutekisuto6709 sixty-nine four-twenty

69420

Mmmmmm tasty things, they are.

Huh.

@@privateger hey

@@henryambrose8607 huhhellow

@@henryambrose8607 I didn't expect you under a video about perlin noise ^^

Lol thanks!

Same for me

I haven't seen my family in years

tuxutku astroneer

its astroneer wtf

and? their job isnt to explain how they made something...

Cool

But how do you get a surface? That just makes holes in your 2d terrain, but no caves.

didnt realize thats how it was done until now, good explanation

@@ducky4303 That is one possibility, another one (Which Minecraft used before 1.18, and still partially uses) is an algorithm called Perlin worms. Basically, you sample 1D Perlin noise (Input is time) 3 times to get a value for x, y and z. Then use this vector for the direction the cave will move. Now you have the path a cave takes, and you can remove blocks around this path to remove volume.

same

Same

same

Technically, marching cubes work off a function defined over some space that you draw an approximate isobar for. But there are several good ways to convert points into such functions suitable for particular uses. E.g. in 3d reconstruction, point clouds, typically with an approximate normal defined for each point, can be converted into a gradient function using something called Poisson reconstruction. You then draw a surface using marching cubes where that gradient function is approximately zero. The resulting mesh then passes close to the original points and has roughly correct orientation. The reason you don't care about it being exact is usually because points you start from tend to have a lot of error and simply joining them together would result in a very bad mesh.

Hopefully I'll have more soon. Procrastinating is very time consuming.

Glad you liked it! And yeah I know what you mean.

But it seems like this channel is dead

Thanks!

Well I'm glad I could help :)

I'm glad you liked it

That's probably how he feels talking about the math involved in his project.

Tbh, It's not that hard. As he did point out many times, He couldn't be asked to do the "Hard" stuff as you need to understand a ton of things but most things he's talking about can be learned by wiki, School, Collage.

Cool. I'll look into it.

you are indeed mistaken. (don't worry, i've been there) they're actually just custom generated worms. (spheres travelling in some randomly changing direction while changing radius) think back to when minecraft was just a small world size. after generating the general terrain, tons of these worms are generated to carve out the terrain. ores/trees are custom generations that populate the world too. in the "infinite" generation model, a single chunk generates all the worms in some radius to carve out that individual chunk. the ores/trees are only generated when adj chunks are present. (so they can generate over the boundaries to make it seamless. otherwise it'd all have to fit inside the chunk generating it. meaning we wouldn't have room for larger oak trees either) along with caves there's also ravines. it's just another type of cave generation. (obviously less common) then there's stuff like villages. they're simply a load of pre-made structures being randomly arranged. obviously they aren't generated chunk by chunk like caves are. (since they're obviously a lot less common too) they just generate out entirely into the world and those chunks are saved. like as if we just used some command to spawn a village that goes out of bounds.

@@nova84d did you actually believe him? or is it real..

didnt they massively change the cave generation in the cave update unless that hasnt happened yet

damn its the man tyridge

Those are such great videos. I love them.

Hopefully soon ;)

Haskell > C#

Its one year old soo...

Explain it to me

Explain it to me pls

Im interested also

For some reason this was marked as spam :/ I still plan on trying to get marching cubes to work but I haven't gotten the chance to look into it yet. Glad you liked this!

KZfaq can be a little... Broken sometimes. XD I hope your able to get it working, and anymore algorithms you find to improve the terrain generation.

Or... today?

But isn't there a saying that "The algorithm never strikes the same video twice"?

Well I'm glad I could help :)

It showed up in my recommended feed too!

Thanks!

Sounds cool.

bitter nope... me too

@@thesadgamer1184 good times

Cool. Good luck!

Thanks!