Dimensions wrong - v4 bug?

Next
 From:  3image
10274.1 
I've opened this STEP model in MoI v4. Though the dimensions display shows the expected values the edit dimensions panel is off. Could this be a bug in v4?
Image Attachments:
Size: 223.6 KB, Downloaded: 87 times, Dimensions: 1046x717px
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Frenchy Pilou (PILOU)
10274.2 In reply to 10274.1 
I believe that you must publish the model or send to Michael in case of confidentiality moi@moi3D.com
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  3image
10274.3 
It's free to download at Grabcad, you can try it by yourself: https://grabcad.com/library/wd-101efax-10tb-nas-hard-drive-1
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Frenchy Pilou (PILOU)
10274.4 
If you take each piece separatly seems it's Ok...

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Phiro
10274.5 
Hi,

the error is in a fillet surface.




You could fix it with the ShrinkTrimmedSrf function.

Don't know if the source is the original modelisation software or in the import.

Have fun...

EDITED: 11 Apr 2021 by PHIRO


Image Attachments:
Size: 17.8 KB, Downloaded: 8 times, Dimensions: 226x168px
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
10274.6 In reply to 10274.1 
Hi 3image, it looks like it's a bug in the solver where in the bounding box extents calculation it's mistakenly going outside of the trim boundaries and processing some parts of the underlying surface that should not be active, for 2 of the surfaces that are portions of a torus that Pilou shows above.

I've put it on my list to investigate in the future but I expect it to be a high difficulty and high risk area to try and fix.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  3image
10274.7 In reply to 10274.6 
Hello Michael,
Thanks for your reply, I see. May you elucidate why you expect it to be hard to resolve? I ask only out of curiosity. Thank you.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
 From:  Michael Gibson
10274.8 In reply to 10274.7 
Hi 3image,

re:
> May you elucidate why you expect it to be hard to resolve?

It's because it is a very complex area of code and some things like adjusting tolerance values for what to consider intersecting or not intersecting can produce side effects like causing other things that used to work to now fail.

So it's in an area that would need first a huge intensive effort to properly figure out exactly what is going wrong, and then followed by another huge intensive effort to test a whole lot of other cases to make sure it doesn't cause regressions in other cases.

Basically it's not going to be the kind of thing where it's a typo or simple logic error.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All