The texture planets, skies and outer space seem to be easiest to find at the intersection of the layered approach1 with various mappings for texture and colour domain. The stereo mapping of the texture domain provides as usual the way to zoom in and out, so that you can admire the newly found texture planet and its surrounding galaxy, all obtained through 2 rounds of perlin-based fbm (with incremental addition of results) and using otherwise the most basic of colour mappings (simply interpreting the x,y,z values as percentages of red, green and blue, respectively):
With a triangle-based domain mapping (z is considered the hypothenuse of a right angled triangle with given x and y as sides) and turning the knobs on the layered approach and/or the noisiness level of the fractal used, the results make rather atmospheric skies of sorts:
To tone down a bit all that clash of bright colours, an initial approach was to actually combine the final values for red, green and blue since that brings them basically again into a closer area and "closer" in the r,g,b space means closer colours & shades:
Given the success with the public of that unitsphere mapping in the r,g,b space, I applied it today to a few of those textures as well and it turned out perhaps not all that bad, as a sort of milky-rivers in the sky for instance:
Keeping this short but using the pics for all they can give, I went ahead and set two of them as skies as well when taking the shots at the hopefuls' latest fashion parade - you'll surely notice the milky one, though both are quite the departure from those tame clouds that are currently stuck to the euloran sky. The thing with making the sky more interesting seems to be that now one *really* wants those things in the sky to also ...move about!
Calculate the new x,y,z coordinates in turn as the result of fractal brownian motion with perlin noise at the given point, always adding the previously calculated value as offset to the corresponding coordinate; possibly iterate this a couple of times. ↩
Comments feed: RSS 2.0
tex_33_512.jpg, tex_37_512.jpg, tex_40_512.jpg, tex_46_512.jpg, tex_38_512.jpg should go on the list for the hopeful gen5 dressings. Which, when's it scheduled, next Fri or something ?
I'll add those textures to the list then. How /why did you pick those specifically? Rather, more to the point: what are you looking for, in a texture? I'm asking mainly because there's a seemingly widening gap between expected and actual picks.
Re gen5, it's not yet scheduled because there's still to do first: another thorough check of the mirroring in both planes; the various writings; the different mesh fitting; potential further adapting the script for efficiency with all the various options because for the last run the number of points increased significantly and as they get *4, the whole thing goes to > 1.5k bones which is quite a jump from the original "why do they have that many bones", huh. While it wouldn't be a problem to run it even as it is now, any overhead starts showing and slowing the whole generation down to the point that I'll need to schedule probably a couple days just for the churning (or dunno, get a more powerful computer just for this, I suppose; can't even run it on a server since I need to render the images and all that).
So given the above, my current estimate for it would be the end of next week but it's a premature estimate really given the amount of stuff still pending - and that might therefore throw up potentially significant surprises.
Gosh golly...
I don't mean to be impossible ; but I also can't help it : when I say
That's precisely the question I'm adressing : how the fuck do I pick, and why (and "how do I know I'm right" etcetera).
If I knew I'd say ; but the question is one of those that don't admit the sort of answer that'd be deemed useful by the inqurier. Nevertheless, the exercise is tending towards clarification & systematization in my own head, which is bound to produce something sooner or later ; yet trust me when I say that if I had iota one of a glimmer of a glimpse of a fragment of a notion it'd be on Trilema already. But so far, all I got is dark molasses with a vector somewhere within in.
This is deliberate on my part ; I'm pushing the whole assemblage until it breaks to find out where that is. From my pov receiving at some point a response in the vein of "MP, this just can't be done on extant machinery" is not perfectly acceptable but actually expected and necessary. Gotta find the bounds, if 1k won't do it I'm fully going to send you 65k counts at some future point. Recall how that whole "MP learns lisp" show went ?
Alright.
Alright. For the record though - I have yet to get an answer that I fail to deem useful. And I mean this in general, to any and all questions I ever asked - perhaps I'm just too used to make use of everything and anything but in any case, every answer I ever got still turned out useful (at times later on, but I have quite a good memory and doubly so for things that don't fully make sense on the spot).
And this makes more sense to me than you perhaps expect. Though indeed, I'd be hard pressed to *explain* how it makes sense *exactly*.
Hm, not sure I quite get this. For one thing "extant machinery" has quite a wide range so what (and why?) is the actual spec you have in mind as to that: the most powerful setup one can build? the most powerful machine I'm willing to make especially for this? just the run of a mill "client machine"? something else? what's even the gain in it anyway?
Fwiw, if it's "what's the limit" you are after, I'd rather expect it to be one of size ultimately - as it's a unit sphere, the more bones you pack in it, the smaller they will be and as a result the less detail you see and therefore I can just as well paint it with dots directly, no reason for generating mesh and stretching it on bone and all that jazz.
I don't seem to recall the "MP learns lisp", no.
> For one thing "extant machinery" has quite a wide range so what
Whatever you happen to be running is fine :)
> Fwiw, if it's "what's the limit" you are after, I'd rather expect it to be one of size ultimately
Yes, well, ultimately. Hang on, we're not ultimately yet.
> the smaller they will be and as a result the less detail you see and therefore I can just as well paint it with dots directly
Indeed lol.
> I don't seem to recall the "MP learns lisp", no.
I ended up casually allocating more memory than will ever be produced to try and process natural language systematically.
Anyways, we see gen5 and consider it then
Heh, I guess it's good at least I know now that you want that limit specifically, as otherwise and by default, I would... look to run it on a better machine if hitting such limit rather than complain about it, lol.
In ulterior good news : on one hand meanwhile I found that lisp discussion, it's ove at http://trilema.com/2017/my-three-days-of-ai/ ; on the other hand meanwhile you found the limit I was looking for, I guess. So what we want, at least for now, would be no more than 65536 faces, I suppose ?
Yes, that seems to be a fitting upper limit at least for now.
[...] this is anyway the second article for today and one coming after going out into the space, no less, let us start with the side for once - aka the turbulence: this is yet another use of the [...]
[...] I left the generator code alone for a few days and did instead all the writing of textures and then some more writing and different code and new textures and even various other [...]