Teaser or not teaser ?
-
I cannot see them on my office computer. I can upload and embed them though; what is the size of them pixel wise, Didier?
-
-
chouette!
I've thought for some time this is the way forward to get high density content without superhuman efforts. Its something I proposed at EA some years back. But in some sense you might want to have this functionality bound to materials and not be an interactive thing. I envision ceiling materials that can spawn light fitting that satisfy minimum lighting requirements, floors that can spawn desks, chairs etc (all with clash detection/resolution) , pavements that generate street lamps spaced nicely etc etc etc. The trees you generate might be L-systems that are seeded by position so all trees are unique, the size of your files could be pretty small and only expanded/exploded on-demand as well.
Tons of neat possibilities and with Ruby - how hard can it be!
Go do it!
-
Didier, this is just great, really!
I just keep watching these videos... -
This would be really useful when it come to forest planting!
Great Idea
Would they be a component like the sandbox meshes?
Can't Wait
-
This one of your great tools!
Thanks...
remind me this http://www.thirdpartyplugins.com/stormtracer/, sorry that i put some c4d's info... Sketchup and C4d are my favorite tools
also another greeble-tool too -
-
What do I think?...:`)
Could have used this yesterday...and the day before...and many days before that!
Oboy, bring it on!!!
-
Very creative and useful. Well done! My clients were just saying yesterday that they wanted to see the model populated with trees.
Keep up the amazing work.
-
Combined with Kerkythea instancing.. proxy objects.. I was going to write such a tool but it is great Dider had same idea!
Thanks and looking forward
Tomasz -
Looks lika a great script.
Is there a limit to how many components you can use. If so it would be good if you could use at least five.
Here are my thoughts for improvement:
Please add the possibility for random rotation and mirroring also. (I use a lot of flat "always face camera" trees and mirroring them help cover up that they look alike.)
It would also be great to be able to click where you want to "plant" a component and it would randomly choose one from the list and random scale/rotate/mirror it. (Some times you want a little more control over where trees goes.)
One more addition is to be able to have the components to follow the normal of the surface instead of their initial good for grass, stones and such.
And possibly a setting that controls how steep the angle could be for the trees to be planted.And finally a question; Will it put all the components in a layer of their own?
Anyway, looking forward to try this.
-
Hi Pixero,
@unknownuser said:
Is there a limit to how many components you can use. If so it would be good if you could use at least five.
No, no limit (excepting the size of the dialog box)
Would 6 be good ?@unknownuser said:
Please add the possibility for random rotation and mirroring also.
Random rotation is done yet. Mirroring is also a good idea, unless I figure out how to do it by script...
@unknownuser said:
It would also be great to be able to click where you want to "plant" a component
Very good idea
I'll add a "point" shape in the list to do that.@unknownuser said:
One more addition is to be able to have the components to follow the normal of the surface
I had thought about this but didn't implemented it (yet). if you think it is useful, why not ?
@unknownuser said:
Will it put all the components in a layer of their own
It could.
Due to the number of settings growing, do you think I must add a "settings" dialog box that will be used if you tell the script to do so, and use defaults if not ?
What is already done is an option to allow or prevent component stacking.
regards,
-
Mighty cool feature !
This would be great for placing dummy components of trees around a plot and replace them with medium polysized trees just before rendering with your favorite render app...
And now if Google would make it possible to work with hi-poly files (multicore tech etc...you know), I'd be a happy man.
-
sorry all but .... can someone upload that ruby ? I've already seen the swf video and .... that's so good ! I like it !
-
Huyvu it seems that Didier is still working on it (also collecting ideas for the development) and the plugin is not ready to be shared yet.
(I'm also very excited looking forward to it
) -
Awesome ruby in the making, who needs Google to give us the tools we have enough very skilled (geeks) coders/programmers here to take our favourite app further and better.
-
Hehe... True, solo (though the core engine of SU could be improved a little to handle hi-poly models - especially if we have a tool like this
) -
Good Work Didier, and thanks for the show and tell. The possibilities are quite extensive.
-
definitly a teaser..
awesome script again Didier....
-
I've thought some more about you script and have some more ideas for you.
I think a floating web dialog that stays on top while you work with the tool would be a good idea. Maybe it could have tabs to make the window as small as possible but still have room for lots of settings.
At the top there could be four (or more) icons for the different tools: Click placement, Paint placement, Draw region and Select a predefined region from a curve.
The paint tool should work like a brush or spraygun that you can set the diameter for the brush. Show the brush size in viewport as a ring and while pressing a specified key and dragging mouse right or left you could change the scale of the brush.
As for the amount of different components I belive the more the better. Maybe a possibility to choose a directory and all components in that directory would be used.
How does the script choose component based on randomness? Maybe it would be good if it recoginzed the last used component and removed that from the next "selection round" so that two identical components never was used next to each other.
When it comes to scaling I believe that a way of choosing what axes it should scale would be good. Many times you might just want to scale it in one or two axes or use different min/max values for different axes.
Just my thoughts...
Advertisement