@csherratt sure, we can match the input-outputs and store just indices, but this caching spawns more questions than it solves
That's half-truth. In fact, we don't want (of course) to match these strings at runtime, even if the comparison cost is low, because we'd still need to walk those mesh attributes for each shader attribute. instead, we just need to have that target index baked in somewhere. Perhaps, a single HashMap<(ProgramHandle,MeshHandle), IndexSequence> will suffice.
kvark @kvark is off for today
@csherratt ^
the last one is a mockup over an old screenshot
like, this is all my little thing could do: http://38.media.tumblr.com/tumblr_lxm7q4mHQi1qgurm4o1_1280.png
I am heavily pushing 'ambiance' though, so it would be awesome if big mountains cast shadows that moved during the day
I mean, fields of grass waving around would be amazing
this is not the quality of render I want, but it gives a rough idea of a village http://38.media.tumblr.com/tumblr_lvelb6mVgz1qgurm4o1_500.png
not sure - I think I have seen similar in miyazaki films
I just want a beautiful place to explore, would be awesome in VR
to transform my art into generative systems that take on a life of their own
perhaps snowmew could be useful - I dunno
but definitely we would need to figure out a way to handle content generation - how top-down/bottom-up we wanted to be
not sure if you have any ideas regarding that
So what is needed for fast procedural generation?
I imagine it is trying to work just a few objects ahead of what is being drawn, but that is a wild guess.
yeah, I have yet to get my head around that
I was going to try for this first, but I don't know beyond that