Hello Michael.

I repeated the test with the huge "engine" model, on my Desktop PC.

Windows 10 64Bit Pro Eng
i7-7700K 4 cores/8 Threads 4.5 Ghz (running at constant 4.45 Ghz)
32 GB DDR4 at 3000 Mhz (dual channel)
SDD NVME M2 Samsung Evo 500 GB
Overclocked Nvidia Gtx 1080 Ti (11 TFLOPS in FP32 and 11 GB GDDR5X RAM)

First of all i want to tell you that your overall job for this v4 is amazing!! Thanks a lot for your constant efforts.
And I'm aware that this in only the very first beta :)

With that said, Michael please consider these following considerations only from the point of view of someone who wants help you in developing an even better Moi.

These tests took me a long time to be completed so please Michael check this summary report and its detailed part :)

At the end of the day these are my final considerations :

1) Load time can be acceptable although I still consider it a bit too long
(Same model in Rhino V6 WIP is loaded and displayed in 1 min and 20 secs!!)
2) Exporting time is good
3) Memory usage is good
4) Memory releasing on exit is excellent
5) Viewport performance : I have to be honest. Actually I'm a little bit disappointed by the viewport performance of this V4 beta.
It's really too slow, above all if I consider that I'm running Moi on an overclocked Gtx 1080 Ti equipped with 11 (!!) Gb of super fast VRam,
that although is not a high-end Quadro P6000, it still the most powerful Graphic Card on the market.
Moi's viewport performance are very weak when compared to the smoothness of the viewport of Rhino V6.

And this is the detailed report :

---------------------------
Loading
---------------------------

Mesh Angle 5 + Add Detail:
Memory occupied : 5.453 GB
Complete loading : 3 min and 55 secs (My laptop with i7-4790K + 32Gb DDR4 1600 mhz scored 4 min and 50 secs)
Complete loading + displaying all the geometry (until task manager cpu% value returned to zero) : in 4 min and 07 secs

3D Viewport performance : about 640 millisecs

Brief video to show viewport performance : http://take.ms/jwXbd


Mesh Angle 10 + Add Detail:
Memory occupied : 2.685 GB
Complete loading : 3 min and 22 secs (My laptop with i7-4790K + 32Gb DDR4 1600 mhz scored 3 min and 55 secs)
Complete loading + displaying all the geometry (until task manager cpu% value returned to zero) : in 3 min and 28 secs

3D Viewport performance : about 200 millisecs

Brief video to show viewport performance : http://take.ms/RuDbj

Mesh Angle 15 + Add Detail:
Memory occupied : 1.950 GB
Complete loading : 3 min and 13 secs
Complete loading + displaying all the geometry (until task manager cpu% value returned to zero) : in 3 min and 18 secs

3D Viewport performance : about 37 millisecs

Brief video to show viewport performance : http://take.ms/NYhxx

Mesh Angle 20 + Add Detail:
Memory occupied : 1.929 GB
SAME TIMING OF MESH ANGLE 15

3D Viewport performance : about 32 millisecs

Brief video to show viewport performance : http://take.ms/gj9Ta

Mesh Angle 30 + Add Detail:
Memory occupied : 1.716 GB
Complete loading : 3 min and 11 secs
Complete loading + displaying all the geometry (until task manager cpu% value returned to zero) : in 3 min and 15 secs

Brief video to show viewport performance : http://take.ms/9zv7M


---------------------------
Exporting
---------------------------

Angle 3 + Divide larger than 3 + All
Memory occupied : during meshing 10 Gb, at meshing completed 8.7 GB
Complete displaying of all the meshes : 47 secs
Exporting to obj : in 2 min and 10 secs, File size : 4.64 GB

Poly count in Moi : 19,344,436
Point count in Moi : 25,356,998

Brief video to show viewport performance : http://take.ms/qIGYj

Screenshot :





Thanks a lot and have a nice day :)

I stay tuned.

Ciao!

Hi Michael,

It is the Nov 13 version.
No Anti-Virus running.
I opened it directly from the unzipped file without putting it in the Applications folder.

Still having the infinite calculation on most operations.

I can't repeat the artefact problem for the moment.
Maybe caused by a certain sequence of operations that I didn't note...

It works fine on Parallel's (I didn't perform any speed tests as my projets are usually not to big).

It also works fine on a non Retina iMac under OSX 10.12.6.


Michel

Seems the FrenchString.txt was not updated in the new version! 13 nov 2017 ;)
So here the new one!
http://moiscript.weebly.com/uploads/3/9/3/8/3938813/frenchstrings.txt

P.S. ...I know this is a very secondary thing for the moment :)

But...just to remind you a thing that some day could be amazing to have directly in Moi V4.

That is, a realtime Ambient Occlusion renderer integrated into Moi's viewports.

This example is from "Thea Render" plugin for Rhino :



This is a quick video : http://take.ms/iBJbF


Ciao!

Hi Moritz,

re:
> Hello, Michael,
> is there a detailed manual to get the CustomUI back in V4 for the Mac?

There is no detailed manual available but it would be close to this:

Download the latest CustomUI and unzip it, it will have 3 folders in it, "objects", "snapshots", and "ui".

Right-click the MoI v4 app and choose "Show package Contents". Inside there go to Contents/Resources. Copy the objects and snapshots folder into Resources so they are siblings of Contents/Resources/ui along with the already existing "commands" and "docs".

Now copy the CustomUI/ui/customui subfolder into Contents/Resources/ui.

Now open up customui/CommandBar.htm in a text editor, find line


Now go into the CustomUI ui folder and in MoI go to Contents / Resources / ui . Copy the line which initializes it which is on line #90 and looks like this:

			<script type="text/javascript" src="customui/CustomInit.js" />

Note that it is directly above a </flex>. Now open up the v4 CommandBar.htm file in a text editor, go to line #80 which is similarly just above a </flex> and paste the copied line in.

I'm not sure how much will work directly out of the box and what needs some updates. But that should be how you would merge it in to the new CommandBar.htm .

- Michael




- Michael

Hi Marco, thanks for your detailed testing, that will be particularly valuable to compare against once I am able to continue the performance work for v4 which I hope won't be too far out.

One additional data point that would be interesting would be:


> Mesh Angle 10 + Add Detail:
> Memory occupied : 2.685 GB
> <....>
> 3D Viewport performance : about 200 millisecs


At this level what is the approximate 3D view performance in MoI v3? You can enable the time display in v3 by:
script: moi.ui.showViewportDisplayTime = true;


Thanks!, - Michael

Hi Michel,

> Still having the infinite calculation on most operations.

Well that's a bummer, it's hard for me to figure out what's wrong when I can't repeat it over here.

If you have time could you e-mail me at moi@moi3d.com so we can discuss it back and forth a bit? I can set up a series of builds with additional diagnostics in it to send to you which could help to narrow it down.

Thanks, - Michael

Hi Pilou,

> Seems the FrenchString.txt was not updated in the new version! 13 nov 2017 ;)
> So here the new one!
> http://moiscript.weebly.com/uploads/3/9/3/8/3938813/frenchstrings.txt

Thanks! I have updated it now so any further builds should be up to date now.

By the way are things like accented characters in the UI showing all ok? One of the other new things is that v4 uses a new font which is packaged with the install. I think the font supports a wide range of characters but I haven't examined every single thing.

- Michael

Hi Michael,

The new version 13 nov 2017 is ok now on mac.
Accented characters in the UI showing all ok.
Custom UI work but Options and Help buttons are no longer on the right side of the footer (see my screenshot). Also see the ugly font used for the name of the commands in Ext.scripts.

Thanks again for your work.

JP

Hi Michael,
Thank you for an information about new functions. Sorry, right now I have no time for a detailed answer, I’ll write it today evening.

Finema
I fixed this bug yesterday (updated version not published yet)
Customui/mods/ExtScripts.menu.htm
Line 3, remove space after slash.

No problem Max, I'll be here. I'm glad you found what was wrong with the scripts menu. I think the HTML parser changed quite a bit in this WebKit version it's some algorithm that's detailed in the official HTML standard, the old one might have been more tolerant of malformed tags.

Oh also if you want to make keyboard shortcuts for the node editor, it should be possible now for a dialog to handle key events that will be sent to it when the dialog has focus, see the new ShortcutKeyDialog.htm that's used by the shortcut key editor for information on that.

- Michael

Thanks Max
I've remove space after slash and font is ok now but Options and Help are still near Ext.scripts

Hi, some stranges behaviors: sometimes when selecting an object, nothing shows , no style name, no dimension. And the construction lines often cannot find a point or a line.
Regards
Moujjik

Hi Moujjik, thanks for reporting these bugs. Let me try and focus on the construction line one first - is it possible for you to make a simple example file where it happens reliably when creating a construction line between 2 specific points? That may help me to repeat it over here. Also do you see any different behavior if you set View > "Display hidden lines" ? - Michael

Is it my imagination, or has the font for MoI3 changed to the font for MoI4?
Especially for Ext.Scripts.
- B

Hi Finema,

re:
> I've remove space after slash and font is ok now but Options and Help are still near Ext.scripts

Try switching the inserted script tag line in CommandBar.htm to have a closing </script> tag like this:

<script type="text/javascript" src="customui/CustomInit.js"></script>

It looks like the newer parser is more strict about not allowing self-closing script tags anymore.

- Michael

Hi Brian,

re:
> Is it my imagination, or has the font for MoI3 changed to the font for MoI4?
> Especially for Ext.Scripts.

Can you post a screenshot?

Hmmm, looking through it here I can see a bug that would cause that - looks like v4 reads the font name from moi.ini from a new UIFontNameV4 value to try and keep it separate from v3 but writes it back out as just plain UIFontName which is the same one used by V3. So if you happen to have Open Sans installed in your system font folder that would indeed show up in v3.

I'll fix it up so v4 will both read and write to UIFontNameV4 to keep it separate from V3.

- Michael

Michael
i've delete function LlamaMode() code in commandBar and it's Ok now
see my screenshot and the commandbar file
thanks

Michaels mod to CommandBar.htm moved the Options and Help buttons back over to the right, where they belong.
(I did not remove Llama)
- Brian

<< French accents

For me seems all is ok!

Problems arrive when Notepad++ save in bad format Ansi / UTF (I never remember what is the good one!
For the moment seems its's coo! :)

For the moment the unic mini problem is that the classic Windows NotetPad don't take in count the "Line(s) Break (s)" !