This is a script that generates so called “lorenz attractors” [1]
I adapted the formula from levitated.net[2] almost two years ago.
Today I added the interface.
You can generate a system and modify it with the spinners[3].
If you move the start point in the szene ($LorenzStartPoint) you need to press ‘update system’ – as my callbacks dont act like I want them to.
** edit **
a: I removed the callbacks as they crashed max
b: I added a redrawViewportsCallback and now it seems to work
** edit **
The next release should create a object with animatable customAttributes.
[estimated release date 2012]
This script is written for MAX8.
Georg
[1] http://en.wikipedia.org/wiki/Lorenz_attractor
[2] http://www.levitated.net/
[3] http://www.preset.de/3dsMAX/lorenz/
hello from munich!
as usual you rock saw that script on your websire www.preset.com allready. i will give it a try in production.
PS: your dashed lines script allready savend my ass here while drawing street details…
PPS: hopefully i get iternet going at my notebook til the end of the week. i´m lost in writing the help for our sideproject right now allready compiled a windows installer for it
regards
anselm
Anselm!
I just added a “bake system” – button for the rdg::lorenzAtrraktor[2] release.
Will upload it later.
PS: me too compiled a windows installer (ddl @ timeless::preset)
Wibke is going to take care of the overall look&feel/icons for the project – so just concentrate on the writings in your spare time
Georg
good job! gotta play around with this one :))
Updated version:
rdg-lorenzAttraktor-2.mzp
Now with lesser ** system exeptions ** – I hope.
There is also a bake button, you can now bake a system without closing the dialog.
Very cool and very fun. I just had a poke around your code and it is nice and clean and that prombted question that really isn’t related to the tool itself. Why have you used rolloutCreator and what advantages to you see in using it as apposed to using stright rollouts.
Why have you used rolloutCreator and what advantages to you see in using it as apposed to using stright rollouts.
In this case it is not so obvoius but ‘complex’ layouts are much better to handle with rolloutCreator[+RDG], especially when you are dealing with dynamic content like buttonnames.
To me it was annoying to handle rollout creation either with “rollOutSrc +=” or formats and executing them. The rolloutCreator – approach looks more/better readable to me.
I even think about writing/adapting something like this for menus and customAttributes.
But I can be improved, ie it is not possible to add controls and handler in the same loop if I use groups. (because handlers cannot be inside of groups). As rolloutCreator is just a struct that combines strings, it can be easily modified.
Usually I call a beautifyMe() with onOpen handler, to compensate layout glitches.
Another future expansion could be a rcML, where you can define your rollouts/handlers with xml and the mkRollout parses them … but maybe this already exists.
Georg
I should start to use it I guess. Thanks for the explanation when you would, I guess you just get used to writting it that way and that is why you use it.
I should start to use it I guess.
definitvely! I always thought you pro’s use it day in day out – that’s why I introduced it two weeks ago into my coding-style. I know and like this runtime generated stuff from actionscript/flash – and missed it in maxScript.
I guess with all this .net/max9 things comming – runtime generation of code will become more and more important. who really wants to layout interfaces by hand?
Georg