just downloaded V4.

I first noticed the window pane font seems missing, see attached. after this when i open a file i am presented with the open dialogue box, this works fine but after i have selected open I just get a big white box where the open dialogue box was. I dont see the desktop or other software in this "box"

I am on a iMac with system el capitan i think. I say i think as the proverbial white box won't let the about this mac show up!

so it seems the white box maybe there whilst its processing the opening of a large file (80mb). Also the text in top of panes now has some text in it once i opened a smaller file. see attached. Would be good like you say to make moi responsive whist processing - at moment screen is unworkable until file has opened.

matt

Hi Matt, re: frozen appearance while loading - yeah I want to do some work a bit later on that should prevent that from happening. At the moment though it's normal for it to look odd during a heavy file load that's from the UI not responding promptly to the operating system telling it to redraw right then. Just as long as it goes away once the file is actually loaded.

- Michael

Hi Finema,
My footer DOES have Options and Help. (Edit, yes, no longer separated to the right.)
I recall seeing a scrollbar earlier today...

- Brian

Ok, I just updated it to a new Nov-13 build which should fix the problem with lots of commands not running on Mac. No changes for the Windows version. The updated version is here: http://moi3d.com/beta.htm .

Hopefully that should get the Mac version going well now.

- Michael

I did NOT copy any icons over from MoI3.
There are about a half dozen differences +/-
- B

so I've managed to open up a monster of a file (could never open in v3) but now i notice the number in top left of my window viewport shows 3d -611. What does the 611 mean? i noticed one small models this number was around the 5 mark . .

great work micheal, I'm blown away that i can now crack open a lot of these big files :-)

WOW!!

Looks GREAT on a iMac 5K!!!

And so far the tools are working now!:-)


I have one main issue:
My Mouse is not zooming... (Apple MagicMouse2) instead its panning... :-(
But 3Dconnexion is working :-)

something curious:
My shortkeys are imported but show up different..
Example: Copy Clipboard was CMD+C and in V4 its Alt+C

I love the new Inputboxes for the shortkeys! :-)

V3:



V4


Michael you are GREAT!

Hi Matt, that's great that you can work with files that V3 couldn't handle!

> but now i notice the number in top left of my window viewport shows 3d -611. What does
> the 611 mean? i noticed one small models this number was around the 5 mark . .

The number up there is the amount of time in milliseconds it took for the last screen draw in that viewport. That will be up there for a while so it will be a little easier to measure display performance as more work is done in that area.

You could probably speed up that heavy model redraw by modifying some settings before you open the file, try going to Options > View and set "Mesh angle" at the top to a rougher angle like 25 degrees and uncheck "Add detail to inflections". That will make for a bit rougher looking shaded surface display but should also increase performance. With smaller files if you want them to look nicer on screen you can set it back to the default Mesh angle = 10 degrees.

- Michael

Hi r2d3,

> WOW!!
>
> Looks GREAT on a iMac 5K!!!
>
> And so far the tools are working now!:-)

That's great! And yes it should be a particularly big improvement on Retina displays.


> I have one main issue:
> My Mouse is not zooming... (Apple MagicMouse2) instead its panning... :-(
> But 3Dconnexion is working :-)

Yeah I thought that magic mouse might be a problem, the difficulty is in figuring out the difference between it and a trackpad being used. At the moment I kind of sacrificed the magic mouse for trackpads to work with multi touch. I'll be working on this some more in the next few days.


> something curious:
> My shortkeys are imported but show up different..
> Example: Copy Clipboard was CMD+C and in V4 its Alt+C

Hmmm, yeah probably a bug or complication left over from Wineskin - in V3/Wineskin Alt and Cmd were interchangeable and couldn't be set separately because when you used Cmd Wine would actually send an Alt key since Windows programs don't know about Cmd. So it's something like V3 actually stored them in the moi.ini file as Alt but then displayed Cmd in the editor pane. I'll have to think of what to do about that.


> I love the new Inputboxes for the shortkeys! :-)

Good! Yes now as you probably noticed when you set up a shortcut key you actually do the keystroke you want instead of typing in the name manually. That should make things easier to set up.

Thanks,
- Michael

Great work, Michael! Thank you!
I tested both Win and Mac versions - everything works good.

P.S. At the moment some of my scripts don't work, but it's OK, I'll fix them later.

Hi Michael,

Thanks for the new native Mac version.

Just downloaded Nov 13th Mac version.
Testing simple operations on Mac book pro Retina OSX 10.9.5
Yes, the new interface is very crisp on Retina display. Nice!

All Construct operations enter into infinite calculation.
When no objects selected, if I click on screen repetitvely, strange artefacts appear and disappear randomly.

Creation of curves and Solids work fine and Transform operations work too.

Also, are there any differences between v3 ini and v4 ini as they share the same file on my Mac ?

Thanks again,

Michel

That's great Max! So one thing I've been meaning to tell you is that a couple of months back I used your node editor as the main compatibility test. Initially it didn't work on Mac and I found it was mostly because I was at that time returning back native paths from directory functions like getUIDir() etc... which was pretty different than how V3/Wineskin/Mac behaved with its pretend z:\ drive paths. So to solve that I made those functions still return Windows/Wine style z:\ drive paths still with v4. That seems easiest anyway since then scripts can just focus on handling one kind of path and work cross platform with less platform specific logic needed at least that's the idea. But I may be missing some places that should accept either one of a "script path" or a "native path".

If you do want native paths there are new functions moi.filesystem.toNativePath( path ) which will convert from a "Script path" (z:\ drive on Mac) into a native path and moi.filesystem.toScriptPath( path ) which does the reverse.

Also you've probably seen already but the Mac directory structure has changed somewhat since there's no drive_c/moi in it anymore. But on Mac getProcessDir() will return Contents/Resources and the commands and ui directories are under there so hopefully that will resemble the old structure fairly well.

If you can tell me which scripts aren't working or send them to me I'll see if I can tune up things so they work as-is hopefully. They may be exposing things that should be fixed up so other scripts in the future don't have to worry about some details like path conversions. Some other things like any layout behavior differences from the newer WebKit may need to be changed in the script though.

Thanks,
- Michael

Hi Michel, thanks for testing it!

> All Construct operations enter into infinite calculation.

Hmmm, I was hoping this was solved by the new build from just a couple hours ago. Please carefully check that you definitely have the Nov-13 build and not the Nov-12 one.


> When no objects selected, if I click on screen repetitvely, strange artefacts appear and disappear randomly.

So if something is selected it doesn't happen? Is it possible to get a screen capture of one, that may give me a clue for where to look.



> Also, are there any differences between v3 ini and v4 ini as they share the same file on my Mac ?

There shouldn't be any difference - MoI v4 will put a couple new settings in there like the main window position is stored differently so it can handle stuff like full screen zoom state but v3 should just ignore and retain any of those new things.

- Michael

Hi Michel, do you possibly run any Anti-Virus software on your Mac?

- Michael

Hello, Michael,
is there a detailed manual to get the CustomUI back in V4 for the Mac?
-moritz

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!