Hi James,

>> I think it is best with "io_text_highlight" set to "false"
In my opinion it looks better with both "io_text_highlight" and "io_highlight" switched off :)

>> Some thoughts on Remapper widget
I'll try to write this node today evening. Thank you for a good idea!

Hi Max,

>> I'll try to write this node today evening.

Wow, this is exciting, Thank you so much...I can't wait.

>> Some...[MORE]...thoughts on Remapper widget

Grasshopper's Graph mapper has 10+ curve types, however several would have limited application.
Instead of emulating their approach, it would IMHO be better to have an anchor point at each end
and a pulldown menu in info panel for the number of control points (0,1,2,3 or 4). In that way, 0 control
points would give a linear remapping of numArray to new range and 1 or 2 control points provide easing.
3 or 4 control points could be used for defining geometry: say you have a linear progression (0,1,2,3,4,5)
wired into z input of Point node (x=0, y=0), as well as into Remapper node with curve as shown below.
The new series output is wired into radius input of Circle node & the Point node is wired into the Center input.
Loft the circles and you have a parametrically defined lathed form. This is a very simple example, but
imagine if multiple Remapper nodes were used together, say affecting rails and profiles of sweeps & rail-revolves,
or multiple curves Lofted or Networked to surfaces.



I imagine you are too far down the track for taking on suggestions, and if the new node allows num array
remapping by S-curve only, it will still be a huge advance for NE

I look forward to seeing what you have done
James

P.S.
>> In my opinion it looks better with both "io_text_highlight" and "io_highlight" switched off :)

For future releases, then, have them both set to false and I will reset "io_highlight" to true myself.

Max , James and Friend
reconnect to the Graph Mapper or Remapper , or speech in any
another way we want to call it,
I unlike James, I would leave some types of curves by default :
Linear
Bezier
Sine
Cosine
Cubic
CatmulRom
and , add a Free Curve with n ° (to be defined) pt ... that govern the curve;

I believe that this way, I will be a more flexible instrument ..._

In addition, I would also like to explore the possibility of improving the tool
2D Slider, also including the possibility of multi-input
so that it becomes a sort of viewer of the curve to be obtained,
without having to pedanticly add more Slider2d ...
What do you think ?
In any case, however you decide, it will be a substantial improvement
good work
al

Hi Max,

>> I'll try to write this node today evening. Thank you for a good idea!

Did it turn out to be too hard?

I'm worried that I may have asked too much with my latter post and it made the task insurmountable.

If that is the case, please return to the minimum functionality of applying easing to a numArray as per http://moi3d.com/forum/messages.php?webtag=MOI&msg=7713.833

Thank you
James

Hi James!
Sorry, I was in business trip last week :)

>>Did it turn out to be too hard?
I wrote this node two weeks ago, but I need more time to make it work as I planned it.
In fact it's really hard. :)

You can use it, but I certainly will change it later.

Thanks Max,

Remapper node is a brilliant start.

>> In fact it's really hard. :)
Please know that I am eternally grateful.


I'm sure you know full well what needs to be done for it to function correctly,
but by way of helping to clarify things I prepared the attached NE file.

At the moment the node only works within the range of input array.
So it first needs to remap the array to within new range.

The math to do this is very simple, as shown.
Ideally this functionality would be incorporated into the node.

In the event that no new range is input into the node,
the output array would remain within existing range.

I hope this accords with your intentions.

Have a great weekend
& thanks again
James

P.S. I know the remapping does not correlate perfectly with the curve,
(for instance a diagonal straight line does not result with no change to
array as expected), nevertheless it is still workable.
Although perfecting this is desirable, it is less urgent IMHO
than the remapping to new range as outlined above.

Amazing stuff!!!

I said this so long ago but now I repeat it: "I think there's a Moi BEFORE Max's contribution and a Moi after Max's contribution"
Moi is the EXCELLENT, TOP-NOTCH, basement, and Max's stuff is what makes Moi jump to the NEXT level!!!!

Hi James,
can you post the remapper nod I tried to repeat it but something not right.
Also I can't get the fillet node to work so not sure if I'm missing something.
Cheers
Barry

Hi Barry

The reason remapped.nod failed to work may have been due to not updating interface.js
The attached file needs to replace the existing version at:
C:\Users\<user name>\AppData\Roaming\Moi\nodeeditor\nodes\interface.js

Hope this helps
James

Hi James,
works fine I had interp node where yours as progression node.
My Interface.js was Ok.
Ps with regards to my fillet issue can you post a simple example.
Many thanks
Barry.

Hi Barry,

>> I had interp node where yours as progression node.

It will work with both means of creating a num series, but
it is necessary that the input range is identical.

I am hoping that Max's fixes this so any range can be input
thereby deprecating my reMapRange macro.

>> Fillet

Fillet is a bit different from most nodes in that it requires manual
interaction mid-process. Refer to Karsten's instructions here:

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

Hope this helps

James

Is there a way to autocenter the canvas, or have a mini zoomed-out preview of the canvas? Not having a middle mouse button has made canvas interaction a bit difficult, it would also be nice to allow easy remap of those buttons (sorry if that is already a possibility) and using +/- for zoom would be great as well!

Hi FDP

>> Is there a way to autocenter the canvas, or have a mini zoomed-out preview of the canvas? <<

2 finger double tap on trackpad will zoom to mid-range, however it does not center the canvas.
Max is aware of this and says he'll will revise for next version.

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

Hope this helps
James

The editor is a plugin for MoI. MoI has a VERY ACTIVE community, with the owner/programmer answering any questions you have in the forum. It's hugely more easy to use than any other solids modelers and has one of the best if not the best NURBS to POLYS converter I've ever seen.

4 will be beta any day now, but you have to own 3 to be able to download it. It will probably take a year to go golden, so you're best off just purchasing 3 now.

It's a stunning app, perfect for solid design and concepts. IMO, one needs both a poly modeler AND a NURBS modeler (and a topology modeler). I still enjoy using both SketchUp and MoI and go between them often. I also really like 3D Coat for topology.

You won't go wrong trying MoI. It's that good.
https://discord.software/ https://downloader.vip/adobe-reader/ https://downloader.vip/itunes/

Hi Max,

Remapper node: >> but I need more time to make it work ... it's really hard. :) <<

I found this website http://cubic-bezier.com/
& wondered if it might offer you some direction.
(http://cubic-bezier.com/cubic-bezier.js)

All the best

James

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.