Hi Peter,

> A construction history that lets you adjust the final
> mesh by tweaking a few steps back..

Yup, it's definitely been requested quite a few times.

You can actually do it to a certain extent in MoI already, like for example if you do a sweep, after the sweep is completed you can go back and edit the profile curves or rails and the sweep will update - that's construction history working right there.

But there are several operations that will currently break history, for example booleans or trimming.

So it is somewhat limited right now, but will still work for tweaking things soon after you have created them.

But it would be good to extend it to be deeper and continue to work through the kinds of operations that currently stop it.

- Michael

Hi Dave,

> Sort of an "object" versus "session" history?

Yeah, but I think there needs to be both of these kinds available.

A session history is what is used for basic undo/redo, which is certainly a very useful kind of history all by itself.


But for tweaking objects, you would probably not want to be forced to scroll through the entire session history to find the part that addressed one particular object.

- Michael

This is wonderful, and something I've been meaning to dig into for a while now. I can't wait to dig through the docs.

cool you will be make this inside Moi !
http://paraclouding.com/WP/?page_id=460&album=1&gallery=16

PS This guy (Jotero) has yet made some astonished forms inside Moi Forum !

Here's another example:



BTW, these images are simply the results of tests I'm running while building up the procedural library. This is one that looked interesting, so I'm posting it...

Man...that is just too neat. Really nice functionality there.

That's another cool one Dave, this method will be really great for making fractal shapes!

- Michael

A couple more tests...

Cubic Fur:



Stars and Stripes Forever:

This one's a torture test, a 100 x 100 x 100 grid of points (1,000,000 total). MoI working set size of 662MB...



And here we go, diving into the matrix...

Now that is "VOXELS" ;)

Procedural seaweed?

RE: Hammered Finish

> It would, but it might require a lot of analytic math to correctly position the "hammer" before each "blow". I haven't delved into every nook and cranny of the Javascript API yet enough to know if those kinds of interfaces are being exposed in the API. If not, then a PhD in Math is going to come in might handy in addition to some Javascript programming chops ;-)

Because the indentation is very slight, the hammer (for all practical purposes) is a large sphere. So orientation is not an issue. If you can randomly intersect a small portion of a sphere with a solid (the ring) and boolean diff, it may give the desired result.

If you want to experiment, try making a hammered finish on a flat solid. As long as there is some overlap in the random pattern, it may work.

I enjoy seeing the results of your experiments.

Ed

Maybe you must see at this ;)
a very cool free procedural prog
http://k3dsurf.sourceforge.net/index.html
for take formula ;)

Dave, that is very interesting and impressive!

Please take a look, maybe a suggestion:
http://web.njit.edu/~jcl7/pastimes/pendulum/index.html

(I started here in the office recreate the "Hardware",
but my wife wanted to call the ambulance before...:lol:)

Add: fractal shapes

I am really impressed how quickly MoI handles this script. It can't compare with RhinoScript at all. -Petr

edit: aha... I see it now. MoI seems not to redraw viewport until finishing the script when loading script from "scripts" directory. When I put the script into the "commands" one it starts being slow as well as RhinoScript because it redraws screen immediately after adding each point...

How do you use this script inside Moi ?

Hi Pilou, it is regular MoI's script - just close MoI, put the script into the scripts or commands directory, run MoI and type <Tab>fern<Enter>.... and wait :) -Petr

Thx! Super! I willl try that!
But now use the points? ;)

Hi Petr, that's a cool one!

You might be able to get some better behavior when run as a command if you kind of batch up the points in an array and then have a tighter loop at the end that just pumps out points.

The main difference between running as a command versus an instant script, is that the command version runs in a separate thread and so does not block the main program thread while it is running. So that allows for things like the window to redraw while the script is running instead of making the window appear to be locked up until the script is finished.

In v3 I think I'll probably try to set up some alternate geometry creation methods for simple objects, stuff like geometryDatabase.addPoints(); , stuff like that so you won't have to go through factories for creating some basic types of things.

- Michael

Yes you can rotate the model during the process! :)