Hi Marco,

At the moment I wrote just a core engine of this node system. First beta version has been released, but most of the functions are still unavailable.
Now we need to write nodes. Karsten already wrote a lot of nodes which we can use with the new version. Wait for a while.

>>So, how generate this kind of object, starting, let's say, from a selection of point objects ?
Right now only three nodes can create a pointarray objects: GenArray, Point and FRotate.

Hi Max,
I notice that we can now zoom in and out which is excellent.
I'm running MoI on a Surface Pro 4 and the Node Editor UI is a bit to small for my old eyes.
Is it possible to enlarge the UI for high definition Monitors.
If not no problem can work with Windows 10 magnifier.
Many thanks for sharing your work it's keeping my old brain active.
Cheers
Barry

Hi Max,

Thank you for your prompt reply.
I will try to use some of Karsten'nodes while waiting of your upgrades.

From a software developer to another one, my congratulations for the results of your efforts.

Marco.

Hi Barry,

Extract litegraph-editor-hd.zip file to nodeedit/css folder (overwrite the old css-file)
Also extract moi-litegraph.0.41.zip to nodeedit/core folder to enable >1 zoom levels.

Hi Max,
many thanks it's great.
Barry

Karsten,

""""""""""""after a quick test - excellent! Everything seems to work. Another Masterpiece!""""""""""""""""""

Apparently all your existing nodes need to be re-written?

They all error out for me on new node system. Just to be clear.

Hello BurrMan,

that's correct. Most of the nodes has to be rewritten or need an update - so I started allready. And yes - everything in the new beta seems to work:-)

At the moment I study Max code - especially the pointarray and the frames. The changes here, are the most important at the moment, to get the nodes work.

Have a nice day
Karsten

I've been gone a long while...so I'm a bit confused...is this the "official" path for parametric in Moi3d?

Waiting the complete rewriting for made the new French Version! ;)

Hi TwinSnakes,

> I've been gone a long while...so I'm a bit confused...is this the "official"
> path for parametric in Moi3d?

In the future I would like to implement history based parametrics in MoI, it would be a little different than this method. But Max's system is something you can use now if you want to build a procedural model. I'm not sure when a deeper history based system will get implemented for MoI, there is still a lot of work I want to do to improve other areas first.

- Michael

v.0.5

- added Get objects nodes (Get objects by name, Get objects by style, Get selected objects)
- added ObjBoolean nodes (thanks to Karsten)
- added few array/construct/transform nodes
- made some enhancements in the core code

I made new version of Karsten's Motor demo. Now it looks much simpler than before.

Elephant the big return!

Hi Max,
I'm using the maths array to get a grid type array.
To get the desired centres I adjust the umax/vmax based on the Unum/vnum inputs.
Is it possible to have the umax/vmax accessible by inputs or is there another way to do
this type of array ?
Thanks
Barry

Hi Barry,
replace /nodes/arrays.js with attached file.

In fact I don't like nodes with large amount of inputs. Later I'll write a new version of this node. I need to find an optimal way to solve this problem.

Hi Max;

Great Job! as usual. As a suggestion may be creating other nodes ( Domain nodes ) will eliminate cluttering the nodes with too many inputs (see attached example from Grasshopper).

Thanks,
-Sharif

Great suggestion Sharif.

A possibly simpler alternative would be to allow range fields to accept variables as shown.

-James

Hello Max,

looks really great! The@'y'@ becomes more and more an powerful and easy to use tool. At the moment, I try to implement the pushFrame-function. Reverse/evaluate the Euler-Angles drives me crazy. RX, RY are working good (after a lot of failures) - and so, every time I think - I got it also with RZ - the axes flips or the angle turns the direction:-( I will post the code next time - maybe someone will have a good idea.

Have a nice day
Karsten

Hi Max,
Thanks for modifying the array.
I understand what you mean about keeping the inputs to a minimum.
I was thinking the same as James ( being able to add a variable into those fields )
That way inputs would only be added when required.
Anyway again many thanks.
Barry

Does the dictionnary multi-languages is running like the old one ?

(because seems not running now ! )
I have changed the "EN" to "FR" and add the French dictionnary with good syntax, run Moi In French but...all stay in English!
Not yet tranlated anything except the core/lang.js --- does this explain that ?
Seems Nodes must be translated !

Motor's animation runs fine!


PS A number of version, and name of the file node used will be fine somewhere in the Node Editor Screen!

I like the idea of optional inputs.
I find the idea of using variables for them okay, but not 100% straight forward.
Grasshopper has it on some nodes that if you zoom in deeper, you can activate additional inputs.
Usine, a node based audio application has three interface states for nodes: "Collapsed" (no inputs visible, all wires go to one visual port, node is as small as possible), "Used Inputs" (only the most important inputs and those actually in use are visible) and "All" (all available inputs are visible). So you can noodle away with all inputs visible and then collapse to one of the two other states later.
I could also imagine that you could "activate" a field as input in the inspector GUI.

Cheers,

Tom