Show messages:
1-8
9-28
29-48
49-65
From: mkdm
Hello Michael!
How are you? I hope fine.
Thanks for this new improved beta.
After downloading I did just a very quick loading test with a middle size 3dm file.
Unfortunately I have first uninstalled the previous beta, so I can't compare the new results with older one, but this new beta it's significantly faster than the original 3.0!
Also the display engine seems to be much more fast and fluid than version 3.0
My config: i7-7700K 4.5Ghz with (only) 4 cores, 32GbRam 3000Mhz, Nvidia Gtx 1080 Ti overclocked.
The 3dm file I have used for the test: about 196MB
You can download it at:
https://grabcad.com/library/ngoc-mai-tug-boat-1
And these are the results of my loading test:
Moi version 3.0 :
Mesh angle set to 10.0: loading time about 26 secs
Mesh angle set to 5.0: loading time about 39 secs (total memory occupied by Moi: 2.5 Gb), rotation of the maximized 3d viewport is pretty slow
Moi version 3.0 :
Mesh angle set to 10.0: loading time about 7 secs
Mesh angle set to 5.0: loading time about 11.5 secs (total memory occupied by Moi: 2.51 Gb), rotation of the maximized 3d viewport is MUCH MUCH MORE FASTER!!
VERY WELL!!!!
Now I hope to see a new antialiasing routine for the meshes rendered into the viewports (not for the curves or the edges but for the boundaries of the surfaces, that are still very jagged). I think that leveraging on the GPU power we should not have bad performance.
And...before you ask :), changing the antialising settings with the Control Panel of the GPU doesn't lead to no improvements.
Thank you very much!
From: ed (EDDYF)
Tested with some large files on my WIN10 6 core PC. Very fast and smooth!
Ed Ferguson
From: pafurijaz
:)
From: Marbleman
Thanks Michael
From: Michael Gibson
Hi Alex,
re:
> Here is a simple STEP export same file one from V3 and another from V4.
Can you please post the STEP files that you used to make those screenshots?
Also is this new behavior that has started in this just released V4 beta or does the previous V4 beta behave the same way? If you don't have the previous v4 beta installed any more please e-mail me at
moi@moi3d.com and I'll send it to you.
Thanks, - Michael
From: danperk (SBEECH)
Thanks Michael!
Excellent speed increase on loading!
Edit:
Tested with Rotation script on 300mb file..
Ver.3.0 = 135 ms
Ver.4Aug28 = 30 ms! 8-)
From: OSTexo
Hello,
Significant consistent performance increase on load and display, awesome work.
From: Michael Gibson
Thanks everyone for testing it - I'm glad the performance updates are working well!
I have also updated the first message with the list of bug fixes and change for this release.
- Michael
From: Finema
Thanks Michael !
From: Frenchy Pilou (PILOU)
French Updated :)
http://moiscript.weebly.com/v4-quoi-de-neuf.html
From: Metin Seven (METINSEVEN)
Hi Michael,
Just about everything seems to work fine so far in the new beta.
"Mac version multiple windows - Add "Window" menu to Mac version top menu. Shows all open files and allows switching between them easier. Also support Cmd+Tilde (Cmd+~) and Cmd+Shift+Tilde for switching to next/prev window."
Very convenient, thanks. That was one of the few advantages of the previous Wine-based Mac version of MoI.
"Mac AMD performance - fix problem with default buffer location with OpenGL on some AMD cards that was causing slow redraws on some machines like iMac pro."
The latest MoI V4 beta runs smoothly on my Mac. There's only one minor behaviour that occurs when panning in the viewports: as soon as the pointer nears the border of a viewport, the panning accelerates, causing the scene to quickly disappear out of view. If this doesn't occur using a mouse, then it might be related to the Wacom Intuos (Pro Medium) I'm using (latest drivers installed).
Also, I assume you've heard that Apple is ceasing OpenGL support in an attempt to motivate macOS coders to adopt their Metal library. I've heard that Metal is quite competent, but I fully understand that it's a nuisance for coders to be forced by Apple to add support for it.
What are your thoughts about Metal support? The Blender developers are planning to move to Vulkan and add a Metal wrapper for macOS, while AMD has jumped in and already added full Metal support in their free Radeon ProRender renderer.
Regards,
Metin
———————
visualization • pixel art • illustration • animation • 3D design —
https://metinseven.nl
From: coi (MARCO)
there was a discussion about that some time ago
http://moi3d.com/forum/messages.php?webtag=MOI&msg=8964.1
quote:
But there are a couple of reasons why this is probably not a big problem for MoI.
One is that MoI does not require advanced OpenGL functions, it's not like I've been blocked by anything while waiting for them to update to a new OpenGL release level. It seems likely that they will freeze it at the current level and not just outright remove it, we'll see.
The other is that MoI v4 is well positioned to switch to Metal if necessary because part of the MoI v4 rewrite was to use a graphics library called BGFX which supports multiple rendering back ends. So MoI v4 does not make OpenGL calls itself directly, it makes calls into BGFX and then BGFX handles the OpenGL stuff. On Windows MoI calls into BGFX and BGFX uses Direct3D11 functions. So MoI's own viewport drawing code is well separated now from any specific graphics API.
BGFX also has a Metal rendering back end as well. I haven't tried using it yet because it was officially at WIP level when I started using BGFX and also Metal is only available starting on macOS 10.11 while I wanted to support older OS versions than that for v4. I might wait to try it until I'm comfortable requiring 10.11 as the minimum supported platform which is simplest but there is some possibility I could figure out supporting Metal only on 10.11+ while still supporting OpenGL on older platforms. I haven't dug into that yet. But anyway there is a pretty straightforward path to getting MoI to use Metal.
..upps, just saw, that your posted in that thread as well, but on a different matter...then just as a reminder ;D
From: Michael Gibson
Hi Metin, thanks for testing it!
re:
> There's only one minor behaviour that occurs when panning in the viewports: as soon
> as the pointer nears the border of a viewport, the panning accelerates, causing the
> scene to quickly disappear out of view.
That sounds like the autopan function, it's so you can continue to pan in one direction without having to start a new motion.
It starts when you're a little ways out from the border and when it has started you can leave the cursor right in that spot and it will continue panning without any motion required but if you continue to move it closer to the edge it will speed up.
If it is bothering you it is possible to disable it in moi.ini under:
[View]
<...>
DisableAutoPan=y
re: Metal, there is some previous discussion on that here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8964.3
The main thing that is bothersome about it to me is it isn't supported on older OS versions. Metal only works on 10.11 or higher, and currently MoI supports 10.8 and up. I'll probably look into it some more when I'm ready to bump up the minimum OS version that MoI supports running on. I don't really expect to gain much with a switch over though, MoI already does a good job of batching things up so things like lower driver overhead is not likely to make any difference for my particular case.
So it is annoying in the sense that it will involve doing some work for no particular benefit.
If it helps Apple make higher quality drivers then that could be a benefit though. That's why MoI doesn't use OpenGL on Windows. On Windows MoI uses Direct3D11 primarily because the drivers for it tend to be better tested and overall high quality.
Thanks, - Michael
From: Metin Seven (METINSEVEN)
DisableAutoPan has solved the panning behaviour, many thanks Michael. If you'd get a penny for everything you've solved here, you'd be a millionaire. :)
And I suspected I had already discussed the Metal issue here, but as I also did at the Blender forum and ZBrush forum, my memory failed me. :)
I fully understand your arguments regarding Metal, and like you mentioned MoI already runs smoothly in its current incarnation. Apple will undoubtedly include OpenGL for quite some time to come, just will not support it anymore. So you will have plenty of time to make a transition when you're ready for it.
Regards,
Metin
———————
visualization • pixel art • illustration • animation • 3D design —
https://metinseven.nl
From: AlexPolo
Hi Michael,
Have tested in MoiV4 June and same problem with STEP export part names are lost when imported into SW.
Here are all the files.
Image Attachments:
moiv3.JPG
moiv4june.JPG
From: Michael Gibson
Hi Alex, thanks for sending the files. I tested opening the V4 STEP file in Rhino, ViaCAD, Autodesk online viewer, and back into MoI and the names come through ok in all those cases.
I see in a discussion on the SolidWorks forum from last year where you were asking about a similar problem, another user mentioned to try unchecking the "enable 3D interconnect" option in SolidWorks, does that make any difference?
I have sent a message to the author of the STEP import/export library that MoI uses to ask what has changed in STEP export with the newer library that is used in v4 (the June v4 beta updated these libraries from v1.7.11 to v2.0.8) and if there is any way to configure the export to get SolidWorks to see the name.
Thanks, - Michael
From: AlexPolo
Hi Michael,
I have checked with SW Interconnect function and when I switch to this mode where it keeps the step file as a reference file which you can re edit whether it comes out of MoiV3 or MoiV4 the parts names are lost - will do some more research on this I use this heavily in my work flow - I use MOI as a concept tool and general shaping do final preparation in SW then save as STEP for sharing with other SW users.
From: Michael Gibson
Hi Alex, can you please contact me by e-mail at
moi@moi3d.com and we can continue there?
The author of the STEP import/export library wants to send some test files over to you to see if this can be tuned up.
Thanks, - Michael
Message 9044.27 was deleted
From: pafurijaz
Hi, I just wanted to report that in version 4 is not remembered the last directory all the times that I have to open a file I have to redo the path through the various directories, only if a file is saved in .3dm Moi format v4 remembers the last route used, with Version 3 this does not happen. Of course I must also say that I use Moi3D with Wine.
Show messages:
1-8
9-28
29-48
49-65
