Hello Michael.

@You : "...At this level what is the approximate 3D view performance in MoI v3?..."

Well, as promised I repeated the test with my desktop PC both in V4 and in V3 to check if there's some performance improvement in terms of
loading time and viewport responsiveness.

I repeat here my config :

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
Svga Gigabyte GeForce GTX 1080 Ti (11 TFLOPS in FP32 and 11 GB GDDR5X RAM) with latest drivers.

And this is the detailed report :

------------------------------------------------------
Loading in Moi V3 with Mesh Angle of 10 + Add Detail
------------------------------------------------------

Memory occupied : 2.474 GB
Complete loading : 4 min and 38 secs
Complete loading + displaying all the geometry (until task manager cpu% value returned to zero) : in 4 min and 46 secs

3D Viewport performance : about 195-202~ millisecs

------------------------------------------------------
Loading in Moi V4 with Mesh Angle of 10 + Add Detail
------------------------------------------------------

Memory occupied : 2.474 GB
Complete loading : 3 min and 23 secs
Complete loading + displaying all the geometry (until task manager cpu% value returned to zero) : in 3 min and 30 secs

3D Viewport performance : about 192-201~ millisecs

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


These are my final considerations :

1) Loading time of V4 is 1 min and 15 secs faster compared to V3 : very good result!!
Anyway I suppose (and hope) that these results could be even much better with a more optimized multicore routine.

2) Unfortunately I see that the viewport performance are almost identical...

But, as you said, this is only the very first beta and I'm confident that ASAP you will improve Moi's performance.
If I remember correctly, some times ago you have written that you are planning to include some sort of settings or internal behavior that
would make Moi able to use the all the power and the huge amount of Vram of the modern GPUs if one of them is found into the System.
I strongly hope so, because it's really a pity to see a GPU with 11GB and 11TFLOPS (and 480 GFLOPS in Fp64) almost underused.

I stay tuned.

Have a nice day and thanks for all.

Ciao!

Hi Marco, thanks for the additional test! For viewport performance that's actually great news for now that it's the same as V3 and not regressed. It's looking like the transition to 64-bit and using a new cross platform graphics layer have not run into problems.

> If I remember correctly, some times ago you have written that you are planning
> to include some sort of settings or internal behavior that would make Moi able to use
> the all the power and the huge amount of Vram of the modern GPUs if one of them is
> found into the System.

Yup, and I'm still planning on that and have some of the infrastructure needed for that in place, it's something that I'll continue once things stabilize and reach full parity with V3.

Thanks! - Michael

Hi Michael. Here it is.
Moujiik

Hi Martin,

> I confirm the experience of Michel, VIP (VINC)
> http://moi3d.com/forum/index.php?webtag=MOI&msg=8675.56
>
> A simple extrude in the new version from NOV 13 still calculates infinitely.
> I also use OS X 10.9.5
> And I have a non-retina display

Yeah so this was still broken on OS X 10.9 and 10.8 , it looks like it's due to a change in dyld starting with 10.10 that I was unknowingly relying on.

It will be fixed for the next beta and if you e-mail me at moi@moi3d.com I'll send you a test version to try.

Thanks, - Michael

Hi Moujiik, thanks for posting the file, I can the construction line snap problem over here so I'll be investigating it soon.

- Michael

Something is very wrong with my "install" of customui in MoI4, in particular the external scripts.
MoI3 seems to be confused about which external scripts to use (?)
I've been copying variations of draft TruchetTile.js files, and the copies do not seem to go to the right command directory,
or else the wrong command directory is being access by MoI3...
It seems that MoI3 is using the font, or the wrong command directory, hard to tell.
Windows copy file command seemed to be saving the local older copy to file as copy(2), instead of saving the file being copied
as copy(2), but maybe this was an illusion.
Anyway I guess I'll wait for Max's customui for MoI4...
Just reporting this strange situation, I am not really crazy.
- Brian

Hi Brian, so the font thing is because the font name is read from moi.ini , which is shared between v3 and v4. I had intended for V4 to use an entry in moi.ini named UIFontNameV4= so it wouldn't interfere with v3's font name, but unfortunately although it reads from UIFontNameV4= , it still saves to the original UIFontName= property used by MoI v3. So yes if you happen to have the Open Sans font installed in your operating system fonts V3 will start to use it.

I'll have this fixed up for the next v4 beta so v4 will use its own separate property and won't interfere with MoI v3's font name anymore. But for now it shouldn't really be doing any harm other than making it kind of feel like v4 is taking over your v3 I guess!

I don't know about the CustomUI scripts problem, but Max says that he's going to make an updated version of it.

- Michael

Hi Brian,
I have tried CustomUI on V4 and that's work for me on Mac OS 10.13.1.
If you want you can test with modified CustomUi pack in attachment

Hello Michael!

I'm glad to know that my tests are useful for you.

@You : "...It's looking like the transition to 64-bit and using a new cross platform graphics layer have not run into problems..."

Good. I understand your point of view.
A "no regression" it's kinda like a "foundation" :)

@You : "...Yup, ...it's something that I'll continue once things stabilize and reach full parity with V3...."

Perfect.
I'm pretty sure that this will be a "quantum leap" for Moi in general!
Leveraging on the modern GPU's power makes a huuuuuge difference :)

Ciao e grazie! (in Italian)
(Thanks!)

Marco (mkdm)

Hi Michael,
I really miss the snap names when snapping (Mid, End, Int etc..)
Is there a way to get them back?

Thank you,
Max.

Hi Marco,

> Good. I understand your point of view.
> A "no regression" it's kinda like a "foundation" :)

Yup, that's it exactly.

- Michael

Hi Max,

> I really miss the snap names when snapping (Mid, End, Int etc..)
> Is there a way to get them back?

They'll definitely be coming back but I still have some work to do for implementing them. It's one of just a couple still unfinished areas, it's not that they're just disabled by a setting or something like that. May be something like a couple more weeks before having these last pieces working again.

- Michael

Thanks!

Thank you Michael.

I'll wait for Max's update. (The customui is working well in MoI4, as far as I can tell.) But meanwhile, I'll do some more
testing of my file copying (perceived) problem/confusion, with some more elaborate test names for *.js. (I'm using notepad++.)

(I've got 391 windows fonts installed, but do not see Open Sans.)

- Brian

Hi Finema, thank you, but I'm on Windows7, customui is working, but I seem to have a problem with script file copying(?).

Hi Michael,

I noticed that it was more fluid to create solids (sphere, box, plane) on the V3. There is a slight dead time between the first click and the second click on V4.
Also sometimes it is impossible to create the shape after the first click. Pick panel fields stay empty. (it happens randomly)

Thanks

Hi Finema,
the CustromUI runs so far and reacts as desired.
Unfortunately, however, no thumbnails are shown in the Obj Library.
Clicking on the saved. 3DM files does not load the models and new models cannot be saved.
The Ext Scripts window will open as expected - but some scripts won't run at all or abort with an error message.
The Snapshot function works like it should.
-moritz

Hi Moritz
I only use Extscript, it's because i don't notice thumbnails error.
We are waiting for Max CustomUI update.

To me the beta does not work :(

nice.
how much will be an upgrade from v3?