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 !

I repeated the same test using a mesh angle of 10.

2.7GB or Ram occupied and 3:55 minutes to load.

Well...I still consider this a long time :)

I know that comparing very different software is a useless thing but....just to give you a info :

the same model loaded into Rhino V6 WIP took about 1:25 minutes to load as a Block entity and with display style as Shaded.
And the rotation of the viewport was many times faster than in Moi.
I thought it was in this way because of the Block, but I have also "exploded" the Block into standard polysurfaces and the viewport performance
was still excellent.

Please check this video : http://take.ms/2hCTj


This is a screenshot :



@You : "...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..."

I think this will change the things a lot!

Thanks :)

P.S. Tonight I will repeat the same test with my Desktop PC to see the difference with my laptop.

My PC config is :

Windows 10 64Bit Pro Eng
i7-7700K 4.5 Ghz (running at a real and constant 4.45 Ghz)
32 Gb DDR4 at 3000 Mhz
SDD NVME M2 Samsung Evo 500 GB
and...Custom Gtx 1080 Ti (11 TFLOPS in FP32 and 11 GB GDDR5X RAM)

CommandBar.htm just needed one line added at line 80, for CustomUI to work, after copying customui and nodeeditor files to V4 ui, and _variousCommands
to V4 commands folder. (IMHO)

				</vcenter>
>>>line 80+/->>>>>>>		<script type="text/javascript" src="customui/CustomInit.js" />
			</flex>
			
			<div>

				<span class="vspacer"></span>

If V4 window is NOT maximized, my large CustomUI _files screen only blinks on and disappears.

Some Icons are missing from nodeeditor screen.

(Best to let the pro's post modified files, I'm just an amateur :-)

Congratulations to Michael for the terrific upgrade!

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

If I remember right, when meshing the engine @23Gb of ngones, the system usage was about 20Gb of ram.
The meshing process takes 73sec, on a 6 cores cpu ... freaking awesome I would say !

Hello,

Excellent update, I no longer have to move to another application to continue with larger models. I am experiencing a little odd behavior with fillets, I have a model that is a bit of a torture test. When I attempt to fillet all the features at once it gives me a calculation failed but ends up filleting around half of them anyway. There is one fillet that is a persistent problem but I'm chalking that up to nothing changing in the filleting engine.

yes for line 80
but now Options and hHelp are no longer on the right-hand side of the footer

Hi Michael,

Many thanks for the first beta. I've read that there are already some people who have tested the Mac version. Do I understand correctly that most functions don't work at the moment in the Mac V4 beta? In that case, would it be OK if I to wait until the next update?

Thanks,

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.