Had to put "JavaScript" into the title - typical HN... It was about algorithm rather than a language.
Realistic terrain in 130 lines of JavaScript
41–50 of 57 posts
Re: Realistic terrain in 130 lines of JavaScript
#42I remember implementing this on a Sam Coupe from the description in (either BYTE or Dr Dobbs, I forget) back in ~1987. Somewhat slower and lower resolution, of course...
Re: Realistic terrain in 130 lines of JavaScript
#43after thinking about this one for a while, it occurred to me that this really helps illustrate the point of 'Life May Be A Computer Simulation'. Take this world creation a step further, and rather than teaching a computer how to create rocks, each one slightly different, imagine creating humans, each one slightly different. If you think about 'God' as just some alien programmer dude, it helps make so much sense of the world. How can a caring God let so many terrible things happen to us humans? Well, how much empathy do you feel about each rock in this program? When you click refresh, and create a whole new world, do you stop and think about all the exist rocks you are 'killing'? If we are living in a computer simulation, perhaps our creator doesn't even realize we are sentient?
Re: Realistic terrain in 130 lines of JavaScript
#44Reminds me of the results easy to achieve with Bryce3D back in the mid 90's. They had a pretty great terrain engine. I don't think they're making Bryce any more. It would be great if they could release some of that code.
I remember that one, apparently it is still being sold, but development seems to have stalled: http://www.daz3d.com/bryce-7-pro/
Re: Realistic terrain in 130 lines of JavaScript
#45Brings me back to a ray casting experiment I did a while ago [1]. I always wanted to revisit it to include a terrain generation step (it uses a pregenerated height map). Now I have an excuse! ;)
Re: Realistic terrain in 130 lines of JavaScript
#46For those who only want to look at the result(s)
http://www.playfuljs.com/demos/terrain/
Refreshing the page will generate a new terrain
Re: Realistic terrain in 130 lines of JavaScript
#47A friend worked on something similar: http://dcc.fceia.unr.edu.ar/~rbaravalle/fractales/brownGL.ht...
Re: Realistic terrain in 130 lines of JavaScript
#48Just a small note, not to sound snooty, just to educate people on what realistic terrain looks like... This is what midpoint displacement looks like as a heightmap: http://imgur.com/ksETpO0,7gykFEV#0 This is what realistic terrain looks like (this is based on real-world heightmap data): http://imgur.com/ksETpO0,7gykFEV#1 That said, midpoint displacement, perlin/simplex noise, etc are good for modeling terrain at a le…
Thank you... What people don't realize is that "Random Noise" doesn't actually occur that often in real terrain. The bump tool in game engines is the bain of realistic terrain everywhere.
This: http://i.imgur.com/DFXMmY8.jpg doesn't generally happen in nature.
Re: Realistic terrain in 130 lines of JavaScript
#49Reminds me of the results easy to achieve with Bryce3D back in the mid 90's. They had a pretty great terrain engine. I don't think they're making Bryce any more. It would be great if they could release some of that code.
I remember that one, apparently it is still being sold, but development seems to have stalled: http://www.daz3d.com/bryce-7-pro/
I guess Maya ate their lunch. Funny, from the screenshots, they've not changed the interface in a decade and a half. The much lower price is nice, though.
Re: Realistic terrain in 130 lines of JavaScript
#50I think implementing parallel computing using webworkers would be a good item for the "What's Next" list of suggestions.