MoI discussion forum
MoI discussion forum

Full Version: V4 beta Nov-13-2017 available now

Show messages:  1-2  …  63-82  83-102  103-122  123-142  143-162  163-182  183-202  …  223-231

From: Metin Seven (METINSEVEN)
14 Nov 2017   [#123]
Many thanks Max and Michael!

Michael, an option to switch off V3 compatibility and get the Alt key for keyboard shortcuts in return would be nice, but it's not a priority to me personally. A higher priority level for me would be more navigation customization options, particularly being able to set Alt + RMB for panning.

Thanks,
From: Michael Gibson
14 Nov 2017   [#124] In reply to [#119]
Hi moujiik, thanks for the screencaps for the construction line problem. Can you also please post the 3DM file so I can follow along with the same data you were showing?

Thanks, - Michael
From: Michael Gibson
14 Nov 2017   [#125] In reply to [#120]
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

Thanks for reporting this - that you're both using 10.9.5 is probably the clue I needed. It could be something simple like I forgot to set the minimum allowed OS version just on one particular module. I have a partition of 10.9 over here so I'll check it out.

- Michael
From: Przemas
14 Nov 2017   [#126] In reply to [#100]
> I can introduce a flag to allow you to force either Direct3D11 or OpenGL mode, maybe the other one will work better.

That would be great and would help those trying to use it under WINE. Personally the only thing that stopped me from purchasing MoI were the small but annoying issues when I tried to run it on my Linux workstation (the common one was that while I've been able to start it quite easily, mouse-over highlights were always a frame off so for example I didn't know what was going to be selected). Extra options that would allow us to troubleshoot are very welcome :) .
From: moritzbock (MORITZ)
14 Nov 2017   [#127] In reply to [#117]
Ho Michael,
after some attempts I managed to restore the CustomUI.
Unfortunately I still have error messages with some scripts (see photo)

- Obj Library = Operation failed - Line 0
- Ext Scripts = dto.
- Snapshots = dto. + Background changes to white, Language changes from German to English

Have you got a clue for me?

And some icons are still missing....
Do you have any idea where I could look for it?

thanks in advance
-moritz

Image Attachments:
Bildschirmfoto 2017-11-14 um 21.21.46.png  Bildschirmfoto 2017-11-14 um 21.22.08.png  Bildschirmfoto 2017-11-14 um 21.22.16.png  Bildschirmfoto 2017-11-14 um 21.37.01.png 


From: Max Smirnov (SMIRNOV)
14 Nov 2017   [#128] In reply to [#127]
Hi Moritz,
wait a week (or two). I'll release new version of CustomUI
From: moritzbock (MORITZ)
14 Nov 2017   [#129] In reply to [#128]
Hi Max,
I'm looking forward to it....
-moritz
From: Marbleman
14 Nov 2017   [#130] In reply to [#128]
Sounds great Max
From: mkdm
14 Nov 2017   [#131] In reply to [#66]
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!
From: Michael Gibson
14 Nov 2017   [#132] In reply to [#131]
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
From: moujiik
15 Nov 2017   [#133] In reply to [#124]
Hi Michael. Here it is.
Moujiik

Attachments:
Fenetre.3dm


From: Michael Gibson
15 Nov 2017   [#134] In reply to [#120]
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
From: Michael Gibson
15 Nov 2017   [#135] In reply to [#133]
Hi Moujiik, thanks for posting the file, I can the construction line snap problem over here so I'll be investigating it soon.

- Michael
From: bemfarmer
15 Nov 2017   [#136]
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
From: Michael Gibson
15 Nov 2017   [#137] In reply to [#136]
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
From: Finema
15 Nov 2017   [#138] In reply to [#136]
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
From: mkdm
15 Nov 2017   [#139] In reply to [#132]
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)
From: wastzzz
15 Nov 2017   [#140]
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.
From: Michael Gibson
15 Nov 2017   [#141] In reply to [#139]
Hi Marco,

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

Yup, that's it exactly.

- Michael
From: Michael Gibson
15 Nov 2017   [#142] In reply to [#140]
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

Show messages:  1-2  …  63-82  83-102  103-122  123-142  143-162  163-182  183-202  …  223-231