Full Version: V5 Wish List

Show messages:  1-11  12-31  32-51  52-71  72-91  92-111  112-131  …  512-529

Hi Tim, I'm not necessarily against making it an option. There are some potential complications though since scripts can refer to viewports by name as well and I'm uncertain what the side effects could potentially be if the script API didn't have uniform behavior.

A thin layer that only changed the labels in the UI and not anything else would not be too complicated though.

- Michael

---

Hello Michael.

What about my request for V5?

"For V5 (or I hope in the next builds of the current V4) I have this request:

A TRUE OBJECTS "INSTANCING AND GROUPING/PARENTING"

That's will be a HUGE leap forward!

Thanks."


Are you planning these long awaited things?

Thanks and have a nice day.

---

Hi Marco, I don't have any fixed plans yet, so I can't comment on whether a particular feature will definitely be in v5 or not.

That's an area that I would like to work on, but it is unknown how much work it will take. I will need to do some exploratory work before I will know more about it.

- Michael

---

Ok Michael and always thanks for your frankness.

But, and I hope not to sound too complaining...

Could you tell me, in broad terms, which new (really new) feature are you developing/planning for the next releases of V4/V5
And if you have a rough roadmap.

I ask you these things because, even if the new V4 major release is a great product and compatible with 64 bit, it's been years that Moi3D doesn't get any real new modelling feature.

I hope you understand my point of view...

Have a nice day.

---

Hi Marco,

re:
> Could you tell me, in broad terms, which new (really new) feature are you developing/planning for the next releases of V4/V5
> And if you have a rough roadmap.

I'm sorry Marco, like I wrote previously I don't have any fixed plans or any roadmap set yet. So I do not have any of this information to give you right now.

MoI v4 did introduce SubD model conversion which enables new modeling workflows, I would think that should be considered a modeling feature.

- Michael

---

OK, Michael.

"I'm sorry Marco, like I wrote previously I don't have any fixed plans or any roadmap set yet. So I do not have any of this information to give you right now."

Really, I don't know what to say...

I'm really sorry to hear that.

---

Sorry Marco, unfortunately it's quite difficult for me to know in advance exactly how long any particular feature area will take to implement. I need to do some exploratory work before getting a better understanding of it.

Until I'm able to do some of that I just can't make any promises for exactly what will be in v5.

- Michael

---

I don't have time to provide drawings, but here is a quick summary: There are two systems of projection, for representing a 3D object in 2D; generally called the "British system" and the "American system". They are both "standards". They are both 'logical', in how they work. What is not very 'logical' is this: Assume the "Front view" is the front view of a car. In the British system, the left view will show the left side of the car. In the American system, the left view will show the right side of the car! I was taught the American system and used that until I left aerospace in 1998. So I feel safe in saying that the Brits got it right and the Yanks should have left well enough alone. You can adhere to a standard, but you have to decide which standard! Life is complicated. (For anyone who wants more info on the two systems, I am referring to 'The Motor Vehicle', by Newton, Steeds, and Garrett, tenth edition, 742 pages, Chapter One: 'Engineering Drawings'.)

---

What about creating MatchSrf in MoI3d? Would it be useful for MoI users. I know that is possible same thing with blend but MatchSrf could also be useful.

I`ll keep my finger crossed also for analysis tools (curvature graph, zebra, check continuity on curves and surfaces). I know it`s much but I think it`s a right thread to dream ;)

---

One "fairly basic" thing I would like to see in MoI is converting points on a curve between sharp corners and smooth curve points. Full on spline curves with tangent handles like in 2D drawing softwares would be great too.

---

Don't know if it's a reasonable or sufficiently popular ask; of course it's merely an ask:
SVG output.

Certainly there are a bevy of 2D vector apps, but MOI is exquisite, accurate, and handy.

If, not... I am happy continuing to paste 2D curves into Affinity Designer.

---

Fillets without limits (it`s 123design still available to download and test for free here: https://web.archive.org/web/20170202170834/http://www.123dapp.com/design ):

Image Attachments:
1608162433801.gif 

---

What is the N° version of this 123D ?

---

I have version installed 123D_Design_R2.2_WIN64_2.2.14 and the fillet engine is very robust.

---

Sorry, I`ve repaired my link

---

same number for me :)

---

Same for me too... 2.2.14

Too bad that autodesk stop the 123D products.
They were simple and easy to use.
Now they push Fusion 360, more complex and more technical oriented.
Artistic design is not the target of Autodesk...

123D Design was a good tool to do complex filetting...

---

Would it be possible to have same filleting in MoI3d or it`s too hard to implement. 123D was based on many open source docs. I`ve wondered maybe if that filleting algorithms from 123Design are also published it would be possible to have same in MoI.

---

Hi mdesign, that particular area of 123D was not based on an open source library, it used Autodesk's proprietary Shape Manager geometry kernel. Shape Manager is a fork of the also proprietary ACIS geometry kernel (https://en.wikipedia.org/wiki/ShapeManager).

So no it is not possible for it to be used in MoI. Autodesk does not license Shape Manager for use in non-Autodesk apps. ACIS is available to be licensed but it's pretty expensive, it's more oriented around higher cost "Enterprise" level software. It could be possible that MoI would use ACIS at some point but sort of as a last resort.

Robust filleting does not really come from implementing a single algorithm well, it's about recognizing and handling a lot of different kinds of special cases for different corner juncture conditions. It takes many many man-years of effort to produce a robust one.

- Michael

---

Thanks, Michael. Understood.

---

Show messages:  1-11  12-31  32-51  52-71  72-91  92-111  112-131  …  512-529