Full Version: V4 beta Sep-10-2020 available now

Show messages:  1-8  …  29-48  49-68  69-88  89-108  109-118

Hi Michael, thanks a lot for taking the time to look at the file. The only goal with this stupid 20 copies was to get a real cofee break when testing the loading time. I will give the dimension trick a try, and tell you how it goes :)

---

So I added a text + horiz line dimension after the 20 copy (it requires a bit a patience :P)), but saved file is still 2.42Gb, "only" 5 models are saved, and the dim annotations are gone when reloading the file (makes sense as it's probably the "last" object in the list).

---

Hi PaQ, dang I thought that would do the trick. Thanks for testing it anyway.

- Michael

---

Hi dear Micheal I have a request on layer management system, it's will be useful if we had the possibility to lock a layer when you hide or select, and an other but maybe more complex the ability to menage groups of object maybe with an other windows similar to layer manager for groups.
A simple system for grouping a couple of objects make simpler handling correlated solid during transforms, and that maybe is useful when import a model as a block, grouping like collections inside Blender make more endless possibility on managements of assembly
Thanks!

---

Hi pafurijaz, grouping is something that I do want to work on in the future.

You can lock/unlock items in the Scene Browser currently by using Ctrl+LMB on the left side of the item:



- Michael

---

I searched in this layer form filed many times but I not had a success, thanks, Moi has a lot hidden features build in the UI.

---

Hi pafurijaz, it's documented in the Scene browser section of the help file:
http://moi3d.com/3.0/docs/moi_command_reference11.htm#scenebrowser

- Michael

---

I also noticed (accidentally)
F1 = context sensitive help.

---

thanks very kind, I started without documenting or tutorials, is too intuitive to me and is my fault, I also have many PDF.

---

Hi pafurijaz, yes after you've been using MoI for a while that may actually be the best time to go over the help file documentation to find out various smaller details. Those are kind of hard to absorb all at once when you're just starting.

- Michael

---

Hi Michael,

Just like to know if this feature exists or if it could be viable in V4 "final".

Text tool centre alignment.

Ability to centrally align as default option.
User would put the text point on origin.
If one letter typed say an "I" its centred on origin.
If 3 letters typed say "moi" the "o" would be the letter
closest to origin.

Nb. If the origin of the text is placed somewhere else asides the "origin"
then the text is still centrally aligned horizontally to where the point was placed.

---

Hi Stefano, currently I'm trying to wrap up v4 and not add in any new features but that one might be easy enough to put in, I'll take a look.

Right now you can get the centered result you want by using the Transform > Align command after creating the text.

- Michael

---

Hi Michael, thanks for the response and recognising the suggestion! - Stefano

---

MoI v4 Beta September 10,2020

Adding a new style and changing color. Select 'Pick Screen Color' then move the mouse around the dialog box and the dialog box jumps horizontal back and forth as the numbers update.

Has this event been reported yet?

My screen capture software limited in colors...

Wayne

---

Hi Wayne, thanks for reporting that, this is the first report of that problem. That dialog is implemented by the Qt framework so that's a Qt bug, I'll see if they have a fix for it that I could apply.

There is a setting in moi.ini which if set will make MoI use the Windows system color picker same as MoI v3 did instead of the Qt one. It does not have a pick screen color option at all though. But if you want to try it, that is set in moi.ini under:

[Color Dialog]
UseV3ColorDialog=y

Thanks,
- Michael

---

Hi Wayne, I found a Qt open bug on that:
https://bugreports.qt.io/browse/QTBUG-43506

But it's still open and hasn't been fixed.

I'll take a look at fixing it up myself. Having the mouse coordinates is not really useful so if I just remove that text from being displayed that should fix it.

Thanks, - Michael

---

Dear Michael,

I recognized a strange thing where I am not sure what software is causing the issue.

When exporting in V4 beta Sep-10-2020 a closed curve that was joined from 2 or more single curves in IGES format and importing it to my CAM software, the CAM is importing the curve twice. So I get two times the same object. I tried the same with MoI3D v3 and here just one object is visible after importing to the CAM. Could there be a loop counter issue (the classical n instead of n-1 counter-end issue) in v4? Or is it an IGES format issue between CAD and CAM?

This does not happen with curves that just have one element like a line or a circle, whereas a rectangle is causing the issue as well.

Best regards

Joerg

---

Hi Joerg, could you please post an example file that has the problem? If you could post both the .3dm file as well as the IGES file generated from it I'll take a look to see if anything is wrong with them.

What is the CAM software you are importing into?

Thanks, - Michael

---

Hi Michael,

Thanks for your super fast response!!!

I attached two 3dm files each with a simple square inside stored with v3 and the other with v4 beta 2020-09-10 and the two IGES files that were created with the two different MoI3d versions.

I use Condacam as CAM software.


Greetings, Joerg

Attachments:
Square V3.3dm
Square V3.igs
Square V4beta 2020-09-10.3dm
Square V4beta 2020-09-10.igs

---

Hi Joerg, so in MoI v4 I have updated the library used for IGES, STEP, and SAT formats to a new version, and the new version by default outputs the curve contained in a "subfigure", a type of component instance. That's the difference from the V3 output, the V3 output just has a composite curve entity without any other hierarchy.

It should only be in there once but it seems that Condacam is inserting it multiple times maybe as it traverses the assembly tree when it visits the parent container element as well as the "leaf" tree node.

I think that's a quirk that may be unique to Condacam, I'm not seeing it come in as duplicated in other software.

It looks like I can set an option on the export to generate output as in V3 without it being contained inside an assembly hierarchy. Can you please test the attached file which was generated using that? It seems to be the same output as V3 so I think that should work ok with Condacam.

In the next v4 beta this will be a flag you can set in moi.ini under:

[IGES]
ExportFlattenAssemblies=y

- Michael

Attachments:
Square_V4beta_with_flatten_assemblies.igs

---

Show messages:  1-8  …  29-48  49-68  69-88  89-108  109-118