Hi Marco, thanks for testing it!

> A) It seems that there is no speed gain compared to V3, both in terms of loading and
> in terms of navigating the viewports (:

That's expected right now and it's good in fact that there isn't any regression. I haven't had a chance yet to finish the work on speed improvements by making use of lots of available VRAM, there is some of the infrastructure in place for it but that's something that I will be working on more once things stabilize. Please remember this is only the first beta and does not contain everything that I want to have in the final v4 release in it as of yet.


> B) It seems that V4 has the same issue of displaying "fake edges" in some part of the models

That's expected, it should behave exactly the same as V3 right now.


> C) As you can see in my video, the antialiasing of edges and above all of surfaces's boundaries is unsatisfactory.

Same thing here, it's expected to behave the same as MoI v3 at this moment. But it will not be difficult for me to add in an option to enable MSAA once the initial stabilization is done.


Thanks, - Michael

Ok Michael!

@You : "...Please remember this is only the first beta and does not contain everything that I want to have in the final v4 release in it as of yet..."

Got it! :)

I stay tuned.

I will let you know my next test results ASAP (I think only late at night...)

Ciao!

Here the FrenchStrings.txt updated! ;)

http://moiscript.weebly.com/uploads/3/9/3/8/3938813/frenchstrings.txt

just a little thing : seems there is no more "line break" when edit with the normal Windows NotPad !
works fine with NodePad ++

Hi Michael,

Firstly, thanks for the V4beta! I look forward to big things
with my favourite app.

As already established, most tools don't work on a mac,
but I wanted to test custom UI and node editor.
As you can see both run with the beta, but this error
occurs when pinching on trackpad in NE.

Also some navbar buttons have disappeared.

Hope this helps
James

Also, when I install Custom UI, I lost icons on the footer (File, Save, Undo, etc...) . (as we see in James screenshot)

Hi Finema, for lost icons with CustomUI, that's because installing CustomUI writes a MoI v3 version of CommandBar.htm in place of the V4 one which is slightly different. So you can't install it by copying the CommandBar.htm directly like you did with v3, either you've got to splice the extra stuff into the new CommandBar.htm or wait for a v4 version of CustomUI.

In general since the UI is slightly different from v3 you can't just copy entire v3 customized UI files into v4, you've got to merge changes in with the new v4 structure.

- Michael

More info on CustomUI missing icons - the missing ones are the ones that used the res:// protocol for getting the icon from moi_lib.dll binary resources. MoI v4 doesn't have any of those anymore and doesn't have a res:// protocol handler anymore so that's why those are missing. You'll need to splice in the v4 buttons for those ones instead of using the v3 buttons.

- Michael

Hello,

Congrats Michael! What a milestone! Big day for you and Moi3D users. Thanks a lot for your effort.

I have 2 questions:

1. v4 will live side by sie with v3, or will replace it?

2. There is any kind of migration soft for scripts? I believe v3 had some sort of batch copying scripts (and/or short keys)?

Thanks.

Carlos

Hi Carlos, thanks! V4 can be used side-by-side with V3 and in fact I'd recommend having them both especially at the moment while there are rough edges being worked out. But it is my goal to stabilize v4 rapidly and get it to full parity with v3.

For migration it's just any custom scripts that you will need to copy over from the v3 commands folder into the v4 commands folder. You can copy the contents of the entire folder over and just say no to overwriting. Shortcut key definitions will come over automatically since they're stored in moi.ini and v3 and v4 will use the same moi.ini file.

- Michael

Ok, so for the Mac version I'm getting close to solving it, I didn't catch it because it only gets messed up when packaging it up for deployment. The way library loading is organized on the Mac is pretty different from what I'm used to. Just part of the brave new world of a native Mac build...

- Michael

OK Michael !
I'll wait for the custom Ui v4.
In fact I just want a button in the interface with which I can run extra scripts. (it's OK, i've just add a line code in CommandBar.htm V4)
I love the new clean interface of V4 on my Imac retina !

Hello,

Thanks Michael for this 64bit flavor !

I did a couple of test to push the mesher :

Engine V-Twin, by Aled J Taylor : +- 23M Ngones !!!

[LINK]https://grabcad.com/library/engine-v-twin-4-valve-heads-1[/LINK]



LAMBORGHINI AVENTADOR, by Fateh MERRAD : +-8M Ngones
[LINK]https://grabcad.com/library/lamborghini-aventador-lp700-1[/LINK]

Hi PaQ.

Thanks a lot.

I was just about to ask Michael some url where to download some huge model for testing.

Thanks.

Hi Finema,

re:
> I love the new clean interface of V4 on my Imac retina !

Yeah it's kind of funny how it works out from really gross to really nice there. The text in particular.

I've managed to track down what was going wrong with those commands on the Mac version and will be able to have a fix tomorrow.

- Michael

Hi PaQ, awesome looking results! Did you happen to look at how much RAM was being used for those?

- Michael

Hello Michael.

I did a quick and dirt test to load the HUUUUUGE file proposed by PaQ :

https://grabcad.com/library/engine-v-twin-4-valve-heads-1 (81MB more or less)

It took about 4 minutes and 40 seconds to load into Moi with my i7-4790K laptop (and Nvidia Quadro K3100M) !!!!

I've made some loading tests using both "drag and drop" and "File - Open"

During the loading Moi's was frozen and in some of the test its screen was totally black, sometimes not.
But, only when the screen was black the loading was successful.
When the screen was not black Moi's apparently discarded the model and at the and of loading Moi's viewport was totally empty.

The model is very heavy and with my Mesh Angle of 5 the rotation of the viewport was very very slow.

This is a screenshot. Please check at the Task Manager :)



This is a quick video : http://take.ms/5PDnw

Ciao!

Thanks for the tests Marco! One of the other things that I want to also work on for v4 is to move file loading off of the main thread so it won't look frozen and also have a progress bar. That will probably go along nicely with large file handling.

- Michael

Thanks for the info.

This is a good idea :)

Please, let me know if you think if it's ok that with a configuration like mine the loading time was normal.

4:50 minutes is a huge amount of time...

You can use the same model I downloaded from GrabCad (proposed by PaQ)

I stay tuned.

Ciao!

Hi Marco, 4:50 is a very short amount of time - it's been common in the past to wait many hours for processing something highly complex like that.

You can probably shorten the load time by setting your display mesh angle to a rougher angle like 30 degrees and uncheck "Add details to inflections". At some point here I think I'll be able to do the display meshing part using multiple cores which should help speed up file loading some.

- Michael

2 minutes 30 to load Engine V twin 80 mo Step
With display mesh angle at 10 it's fluid > really good !