MoI discussion forum
MoI discussion forum

Full Version: V4 Wish List

Show messages:  1-18  …  59-78  79-98  99-118  119-138  139-158  159-178  179-198  …  559-574

From: mkdm
11 Nov 2016   [#119] In reply to [#118]
Ciao Michael.

Thank you very much Michael for your additional clarifications. Much appreciated!

> "..The fundamental problem with a goal like that is that different people will have a different set of 4-5 features and all combined together you're then talking about an awful lot of features to add in."

Aaaaahhhh LOL LOL :)

I apologize...you're totally right!! Customers' desires are almost like the wind....supremely difficult to catch!!

> "It's really more the opposite in fact - because Rhino already has those specific features..."

Ok. So the brutal truth for me it's that I have to surrender to use Rhino for that things :)
(Luckily, the are funny things like Fusion360...)


> "Do you have any examples you could send to me? With G2 reflection lines are already smooth, G3 and G4 are getting into very esoteric properties that are difficult to perceive."

ASAP I will post some example of what I want to say regarding G3 vs G2.

Thanks again and have a nice day.

- Marco (mkdm)
From: MajorGrubert (CARLOSFERREIRAPINTO)
11 Nov 2016   [#120]
Hello,

My whish list:

1. Groups
2. Instancing
3. Dimensions (improve Max's Dimensions)
4. Ghost mode view (semi-transparent objects)
5. Joint mechanism (don't know if this could fit or make sense in Moi's)

Thanks.

Carlos
From: eric (ERICCLOUGH)
11 Nov 2016   [#121]
Hi Michael ...

My priority remains: dimensioning and Text that is not made up of 3d solids.

Yes, I have Rhino and it is not a big chore to switch back and forth but I would rather not have to.

2nd on my list are line types.

Printing would be nice.

Thank you for MoI.

cheers,
eric
From: Son Kim (SONKIM)
12 Nov 2016   [#122]
So my biggest wish is 64-bit, a client sent me a huge data sets(I talking entire buildings...)! Also if the viewport can handle huge data would be nice, being able to move around and work on huge data is a must once you go 64-bit. Fusion360 still struggles in the latter area.
From: Metin Seven (METINSEVEN)
13 Nov 2016   [#123]
Michael, could you please add a "Create cool model" button to MoI V4. I'd appreciate that.

Thanks in advance,
From: Frenchy Pilou (PILOU)
13 Nov 2016   [#124] In reply to [#123]
@ Metin
Try Shift + Ctrl + Alt + Click on the Icon Options (Bottom right screen)
From: Karsten (KMRQUS)
14 Nov 2016   [#125]
Hello,

while playing with the API, I try to use the freehand sketch tool, but using it, allways gives no satisfactory result. It's so final. So I tried to improve the behavior, but its very difficult to implement in JS. Nevertheless I want to make a proposal for maybe v4 or v5. The sketch curve isn't finished until I make a gesture or until a timer runs out.




If not that, a G2-Patch tool for 3-4 sided gaps in joined surfaces.

Have a nice day
Karsten
From: Metin Seven (METINSEVEN)
16 Nov 2016   [#126] In reply to [#124]
Frenchy: :D
From: Metin Seven (METINSEVEN)
16 Nov 2016   [#127] In reply to [#125]
Karsten, good suggestion, to be able to correct parts of a freehand curve. That'd be great.
From: Karsten (KMRQUS)
16 Nov 2016   [#128] In reply to [#127]
Hello Metin,

yes - my problem is, that I have a pen-tablet, but I never use the Sketch, becaus e- after I've made the Sketch, I always make a rebuild, switch on the control points and move them around:-(
I've written a script for sketch/stroke manipulation, but the result is still unsatisfying (as shown)
Anyway it would a cool feature for tablet users and would build a bridge to a more natural workflow on tablets.

Have a nice day
Karsten
From: Michael Gibson
16 Nov 2016   [#129] In reply to [#128]
Hi Karsten, I've thought before about trying to make a curve shaping tool that worked sort of like an airbrush where you could apply multiple airbrush strokes and then I'd work on fitting a curve through the densest region of it. Then maybe you could alter it by erasing the edges of some airbrush areas or applying more airbrush strokes on top of other areas.

Unfortunately it will require a lot of very time consuming experimental work to make that happen so I'm not likely to be able to get to it very soon.

Right now if you want more control than what the current sketch can do, I'd recommend drawing with control points instead.

- Michael
From: Karsten (KMRQUS)
16 Nov 2016   [#130] In reply to [#129]
Hello Michael,
I'm sure you've already thought about it. And I agree with you, that you have to do some more important things at the moment, but I believe it would fit perfectly to Moi's intuitive concept.
Many thanks
and have a nice day
Karsten
From: Mindset (IGNITER)
21 Nov 2016   [#131]
Hello Michael,

Might it be convenient to introduce a feature to manage a user-defined list of observation vantages for the 3D viewport?
It may be useful, between edits, to have the ability to reset the perspective view to that of a prior screenshot.

MOI is the best software experience.
-- Mindset
From: Michael Gibson
22 Nov 2016   [#132] In reply to [#131]
Hi Mindset, yes that's often times called a "named view" or "saved view" and it is something I want to add. I've been thinking about making a new section in the Scene Browser that could hold some "lists of things" like this, such as saved views, cplanes, and maybe background bitmaps should go under there as well.

- Michael
From: Peter S (PETERSAAL)
24 Nov 2016   [#133]
Hi Michael,

My top 3:

1. Support for nested groups, for example to preserve the hierarchy of imported STEP data
2. Support for nested group hierarchy in the skp export
3. Instancing

Thanks for your commitment and excellent work. MoI is an indispensable tool in our workflow.

Happy Thanksgiving!
From: James (JFH)
27 Nov 2016   [#134]
Michael,

No doubt you have been monitoring the development of Project Elephant. I am especially excited by recent embryonic development of paneling functionality made possible by "polyLoft" & "mFlowObj" nodes.

This advancement could be fully unleashed with an extension to the "Flow" option : "Flow Between"

Instead of flowing over a compound nurbs surface, the item would be flowed between an inner and outer planar target surfaces. This functionality incorporated into a version of "mFlowObj" node would bring true paneling tools to MOI3D. (although probably not perceivable in below image: FlowPaneling.jpg, the flowed units all distort in one direction) The outer surface may simply be an offset of the inner surface, however it may also deviate dramatically from it (smooth inside/undulating outside)

I recall you stating in an earlier post that paneling functionality involve complicated mathematics:
http://moi3d.com/forum/index.php?webtag=MOI&msg=1753.4
however one part of the problem has already been solved by node editor (the populating of planar facets of a mesh surface).

I love this software, and would like to see its popularity grow and I do think that this one area for attracting a whole new customer base.

Let me know if any of this is unclear.

Regards
-James




Image Attachments:
FlowBetween.jpg  FlowPaneling.jpg 


From: Michael Gibson
28 Nov 2016   [#135] In reply to [#134]
Hi James, it's probably more likely that kind of deformation would fit in a "Cage edit" command, rather than as a 2 surface to 2 surface flow. For Flow I'm not sure how Flow could incorporate those without negative consequences for the existing workflow, since picking 2 surfaces would likely need additional selection steps.

- Michael
From: James (JFH)
28 Nov 2016   [#136] In reply to [#135]
Hi Michael,

To clarify what I meant I attached a 3 images. The first image shows an attempt to create a woven pattern flowed over a compound surface. The flowing of planar surface or curves with node editor works brilliantly; however flowing solids produces undesirable distortions (as shown).

The second image is taken from a "Paracloud Gem" manual. Their solution is an elegant one: define a bounding zone of deformation by front and back faces. I am proposing something similar.

>>For Flow I'm not sure how Flow could incorporate those without negative consequences for the existing workflow, since picking 2 surfaces would likely need additional selection steps.<<

Selecting the item to flow may be just as it is now.. Only the origin base surface or curve need be selected because the upper could be extrapolated as instantiation of base at the height of the item to be flowed.

There would however be additional step to select second target surface, but this would only be necessary if a checkbox is first clicked prior to selection of first target surface. See third image.

Please let me know if this is at all unclear.

James





Image Attachments:
2ndTarget.gif  ParacloudGEM.jpg  weave.jpg 


From: Michael Gibson
28 Nov 2016   [#137] In reply to [#136]
Hi James, it sounds like just too much special cased behavior to be put in a general purpose command like Flow, especially the part about the size of the objects to be flowed to implicitly select a second surface. There's just no consistency with that type of implicit selection happening in any other existing workflow in MoI currently. And then having it be a special case that only applies to all plane surfaces is another consistency problem.

But it could be possible to add some functionality for doing that elsewhere though that a script could access.

- Michael
From: James (JFH)
30 Nov 2016   [#138] In reply to [#137]
Hi Michael,

I'm not going to keep flogging this dead horse: I just wanted to make a final proposal.

After selection of the item to be flowed, the dialogue box would prompt "select base curve, surface or point cage".

If point cage is selected, the software expects that the flow targets will be an inner point array and outer point array.

I think this approach is consistent with the MOI philosophy of limited suite of tools with multiple functionality based
on input. (why have a specific tool for each of "Flow Along Curve", "Flow Along Surface", & "Paneling Tools", when
they could be folded into a single powerful tool: "Flow").

It is just a thought.
-James

BELOW IMAGE: Rhino 3d Panel & target point arrays

Image Attachments:
PanelingTools_Custom3D.jpg 


Show messages:  1-18  …  59-78  79-98  99-118  119-138  139-158  159-178  179-198  …  559-574