Full Version: Parametric design in MoI?

Show messages:  1-10  …  791-810  811-830  831-850  851-870  871-890  891-910  911-912

Very interesting experiment...

Thanks James!

---

Hi Max,

I have another small suggestion that would be a big improvement for NE.
At the moment all selected geometry, whether byName, byStyle or manually selected, ceases to be responsive to change, which generally is fine.

However there are cases where it would be beneficial if changes to selected geometry was reflected in NE in real time. One example is the use of attractor points: in this way interactivity could be achieved through direct manipulation of point on ground plane rather than abstracting the attractor as x & y slider inputs or to the dot on the Slider2d widget.

I'm proposing that the selection nodes are manually updated as the default setting but have the option of automatic updating at a given frequency (n times per sec) or alternatively if you prefer, at a given interval (in milliseconds).

I recognise that this will greatly increase the computational load, when set to Automatic; but it could be reduced by halting the data stream when there is no change (above a certain threshold), so that when there is no alteration to base geometry the computation load is similar to Manual setting.

Please let me know what you think
James



Image shows selected curve with control points on in red, & post-adjusted cPts & curve in Black. Ideally the 2 would be in accordance: which is to say, that adjustments to original cPts would be reflected in NE and hence the generated curve would correspond to the manually manipulated curve.

UPDATED:
PS Rather than have 2 options (manual & Automatic) it could simply be that the is just a "Freq/sec" field with 0 as the default setting, which would in essence, amount to the same thing.

Image Attachments:
autoUpdating.gif 

---

Message 7713.853 was deleted

---

Hi James!
Sorry, I have no plans (and I have no time) to write any math or geometry nodes for NE this year.
I certainly will continue development of node editor (January or February, I don't know..)

---

Could this be used for guitar curves like arch tops?

---

Hi Neil,

re:
> Could this be used for guitar curves like arch tops?

It's theoretically possible, but it would involve quite a lot of work. Basically the node editor is a different way to build models by building the instructions to do it. It's a form of programming.

- Michael

---

OK - a bit too advanced for me then. Seems the guys who do car modeling use different methods than I do - although some car curves and guitar curves are quite similar. Would like to pick up more of their methods. Any suggestions?

---

Hi Neil, you might look for Rhino tutorials on car modeling. It tends to be a pretty advanced area.

- Michael

---

Take a look at this beautiful nurbs car modeling tutorial ! ;) (there are also 2 cars tutorials at the same site)
https://www.etereaestudios.com/docs_html/nixus_htm/nixus_index.htm

---

It took me almost a year to learn how to make a decent neck - and it's on going. If it's too advanced than maybe whats best is to continue learning basic tool use.

---

In MoI4, with the Dark version of nodeeditor working properly, and failing to get the Light version of nodeeditor to run, after re-reading many posts, the Light version now works, as described below.

Max describes how to install nodeeditor.v.1.rc3, in Windows (AppData directory) or Mac (Application Support directory) here:

http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.767

In MoI4beta, for the above Windows type of install, to run nodeeditor, version 1, rc3, the following script may be utilized in 3 ways:

1. By creating a shortcut key , such as Ctrl+Alt+N (for dark version), or Ctrl+Alt+M (for lite version), with the corresponding one of two scripts shown below.

or 2. By Tab Paste to the MoI command window, of either script.

or 3. By using CustomUI: In the AppData "startup" directory, for example in the file 97 Nodeeditor.js, [A second file would have to be created for the light version, resulting in two icons at the bottom of the MoI screen.] a line entry that begins with: var command = <<<<< copy in either of the following scripts here>>>>>. NOTE, add a " at the beginning of the script, AND add a " before the final semicolon (";), in file 97 (or 98). Rename a copy of file 97 to 98 Nodeeditor.js, and rename the title to for example, var title = "NodeEditLite"; Also substitute the Light script below, with the addition of the two ".


For Max's Light color scheme, the script is as follows:

moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html?scheme=Light', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );

[For the light version, having light">nodeeditor/ added in, as per other posts, did not work on my computer.]

For the standard Dark color scheme, the script is as follows:

moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );

Would someone please try methods 1 and 2 on a Mac, for the Light version?
For the Mac, Michael describes the install folder as:... Library/Application Support/Moi
http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.779


[If a white window comes up, the nodeeditor is not located in the correct AppData/ sub/sub directories. sub/sub = Roaming/Moi but Roaming is not needed in the above scripts.]

- Brian

---

Hi Brian,

re:
> For the Mac, Michael describes the install folder as:... Library/Application Support/Moi
> http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.779

Just a small correction here - it's in the user Library: ~/Library/Application Support/Moi or /Users/[your user name]/Library/Application Support/Moi , not the system one.

- Michael

---

The macro can be "Stored" in two different formats. The SAVEd verson is unfavorable in my opinion.

Regarding storing a macro for later re-use, the macro should be EXPORTed, rather than SAVEd, to the macro folder under nodeeditor
in [.../appdata/.../ (Windows)) or [/Users/[your user name]/Library/Application Support [Mac)]
(Saving saves a sublevel of the macro, which seems to be unfavorable?)

To re-use a macro, a previously Exported copy should be Imported, or selected from the right-click drop-down window,
rather than loaded.

A SAVEd macro can be LOADed just fine, but if a SAVEd macro is selected from the drop down list, it comes in at a sublevel.

If an EXPORTed macro is LOADed, it appears in the nodeeditor screen in expanded form.

- Brian

---

A new, empty Macro may be used to add a title block to a node program. There are no input slots, nor output slots, and
the color may be different.
- Brian

---

Brian,

Thanks for the tip: RE title blocks.

Another useful workflow element that may be introduced in the near future is grouping. The attached image, shows a different node application built upon lightgraph.js, the underpinnings of NE. Similarly, group blocks could be utilised for titling of a group of nodes that perform a particular discreet function, helping to make complex node circuitry more legible.

There have been a number of advances in litegraph: http://tamats.com/projects/litegraph/demo/
It is worth having a look/play around, to see what new features may be part of NE’s development.

Anyway that is tomorrow and this is today,

Happy New Year to everyone here,
James

Image Attachments:
AD6A1D22-6929-428E-82E1-57CE1CA43DCF.png 

---

My Duh moment for today: ConvertPts node comes in 3 modes, Curves U, Curves V, and Points.

-Brian

---

Message 7713.867 was deleted

---

The following minor “bug?” was found for copy/paste of several nodes tried:

Let canvas1 be a canvas with macro detail subscreen1.
Let canvas2 be a canvas created by Alt + NewButton, which may have a macro subscreen2.

Copy/Paste of a Constant node from canvas1 to subscreen1, then the numerical contents of the constant node are copied, and the Information panel is viewable, and editable.

However, if the Constant node is copy/pasted from canvas1 to canvas2, or to subscreen2, then the Information panel is not viewable. But, if the copy in canvas2 is copied a second time, to canvas2, or subcanvas2, then the Information panel contents are viewable and editable.

- Brian

---

Hi Brian,

>>The following minor “bug?” was found for copy/paste of several nodes
Yes, it's a bug, and I can reproduce it. I'll try to fix it today.

P.S. fixed
http://moi3d.com/forum/index.php?webtag=MOI&msg=9189.7

---

Hi James,

I've updated Remapper node. Now it works much better.

Replace nodes/interface.js file with this one
http://moi.maxsm.net/files/nodeeditor/interface.js

P.S. Hold Alt-key to turn on snapping

---

Show messages:  1-10  …  791-810  811-830  831-850  851-870  871-890  891-910  911-912