Hi JP, thanks for the Retina screenshots. That's great, it's working properly on Retina now, UI text and icons look great now and the 3D viewport content shows full resolution. I know about the viewport names in the upper-left corners, text display inside of the viewports is still something I have left to work on. Please let me know if you see anything else at half size other than that.

re:
> - can't open several documents simultaneously

What method are you using to try and open them, is it by double clicking on a file in Finder? What happens if you choose "New Window" from the menu bar at the top of the screen?

- Michael

Hi JP,

> - fillet and chamfer don't run

Hmmm, yeah it seems that asynchronous factories got broken somehow recently on Mac, I'll look into that tomorrow.

- Michael

If i double click on several files in Finder > that open me several MoI windows (ok)
New Window from the menu is ok
i've updaded my post because tools don't run
thanks

Hi JP, yeah I see that a bunch of commands aren't running on the Mac version, they are all the ones that do their work in a separate moi_commandprocessor process. It works ok when running under the debugger over here which is why I didn't happen to run into that. It's probably something like a path isn't set right, I should be able to fix it tomorrow.

- Michael

ok
an other thing
Sometimes i can't draw any curves or solid on scene.
See my screenshot, the panel on the right stay empty and it's impossible to drax something
Thanks

<< also linked to from the download page on the main web site.

Don't see any link of that! ;)

Hi Michael

Thanks a lot.

The UI working more or less properly on Retina.
Drawing seems to work well.

There is a problem with all operations (fillet, chamber, boolean, ofset etc.)

Cheers Stefan

Michael, congratulations on launch! Exciting stuff. A quick 10 minute pass (no custom ini, just playing) and it all looks GREAT! Looking forward to spending more time playing soon :-)

Hi Pilou,

> << also linked to from the download page on the main web site.>
> Don't see any link of that! ;)

It seems to be there ok... Maybe hit reload on your web browser?

- Michael

Yep : reload was the trick! Sorry for the disturb! :)

Hi Michael!

Thanks a lot for your efforts !!!

This is a brief report :

My laptop config is :
-----------------------------
Windows 10 Pro 64 Bit English
i7-4790K 4.0 - 4.4 Ghz
32 Gb Ram 1600 DDR3
Nvidia Quadro K3100M 4Gb 768 Cuda Cores (Driver Version 385.69)
SSD Samsung 512 GB
-----------------------------

1) Just downloaded and installed. No problem at all :)

2) All V3 shortcut keys works properly with the V4!! Thanks!

3) I spent few minutes playing with the new V4.
I downloaded some 3dm files.

4) Loading is OK

5) To stress CPU/GPU I'm using a 5 degrees mesh angle

6) I recorded this video to show you V4 running on my laptop.
I noticed these things :

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

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

C) As you can see in my video, the antialiasing of edges and above all of surfaces's boundaries is unsatisfactory.
I didn't touch anything in my Nvidia Control Panel.
I'm using V4 as is.


This is the video : http://take.ms/ywed7


7) I have also copied all my custom commands/scripts to the new V4.
In next days I will let you know what works and not works correctly.

Thanks a lot again.

I stay tuned.

Ciao.

p.s.

My laptop has a simple Full HD (1920x1080) panel.

Just some example screenshots :






Ciao!

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