And so no we go back to mr. perlin’s work, and I always seem to have come here, in my travels backwards: http://mrl.nyu.edu/~perlin/noise/
( I would also add as a note, that any visits here are good backwards, or downhill climbs )
This is ImprovedNoise.java, which is, well, an improvement of his earlier version ( improvements described here ). But just looking at that page doesn’t really help. While yes, the code is there, I needed to understand how to use it as Perlin did. He shares with us how to do so in one of a few examples here, and I found and studied a few more of them.
In a hurry I brought his original code into my version of processing.js. It worked as I had expected. With experiments I could make it do what I thought it should do. The only problem is that Processing had evolved quite a bit since ImprovedNoise.java, and so porting the original ImprovedNoise.java to javascript was kind of a stupid task for me to have done.
I did it, and enjoyed it, and it was all rather, well, pointless except for the fact that I became more acquainted with perlin noise. But even though I had tried to port some actionscript to javascript and failed, even though I had tried to port Perlin’s original ImprovedNoise.java to javascript and failed, I’m not so sure I have failed.
Having realized that following directions would have been the best method at getting this whole task done, I must admit to having been rather silly. I could’ve so easily looked at PApplet.java, in combination with PGraphics.java ( according to ‘toxi’ ) and just ported that code; it would’ve taken so little time. For some reason I never considered that option.
I do regret the time I have wasted to get back towards the original idea, and my faulty methods getting there. But now I’m much more clear about the task: get Processing’s native Perlin noise code to javascript. Eston Bond has done much of this work, and it is very close to being complete.
The current work looks good with one render, but as z is incremented there are odd squares showing up. I suspect that this has to do with how random numbers are being generated, but I cannot be sure.
The next step, as I see it, is to port the Random object native to Java to javascript. It is my intuition that this may fix the problem, but I’ve been wrong before and no doubt will I be wrong again-
on flickr...
the path towards randomness [pt 3]
And so no we go back to mr. perlin’s work, and I always seem to have come here, in my travels backwards: http://mrl.nyu.edu/~perlin/noise/
( I would also add as a note, that any visits here are good backwards, or downhill climbs )
This is ImprovedNoise.java, which is, well, an improvement of his earlier version ( improvements described here ). But just looking at that page doesn’t really help. While yes, the code is there, I needed to understand how to use it as Perlin did. He shares with us how to do so in one of a few examples here, and I found and studied a few more of them.
In a hurry I brought his original code into my version of processing.js. It worked as I had expected. With experiments I could make it do what I thought it should do. The only problem is that Processing had evolved quite a bit since ImprovedNoise.java, and so porting the original ImprovedNoise.java to javascript was kind of a stupid task for me to have done.
I did it, and enjoyed it, and it was all rather, well, pointless except for the fact that I became more acquainted with perlin noise. But even though I had tried to port some actionscript to javascript and failed, even though I had tried to port Perlin’s original ImprovedNoise.java to javascript and failed, I’m not so sure I have failed.
Having realized that following directions would have been the best method at getting this whole task done, I must admit to having been rather silly. I could’ve so easily looked at PApplet.java, in combination with PGraphics.java ( according to ‘toxi’ ) and just ported that code; it would’ve taken so little time. For some reason I never considered that option.
I do regret the time I have wasted to get back towards the original idea, and my faulty methods getting there. But now I’m much more clear about the task: get Processing’s native Perlin noise code to javascript. Eston Bond has done much of this work, and it is very close to being complete.
The current work looks good with one render, but as z is incremented there are odd squares showing up. I suspect that this has to do with how random numbers are being generated, but I cannot be sure.
The next step, as I see it, is to port the Random object native to Java to javascript. It is my intuition that this may fix the problem, but I’ve been wrong before and no doubt will I be wrong again-