Bit of a problem with Inset.
 1-14  15-29

Previous
Next
 From:  blowlamp
5508.15 
Hi Michael.

After following your mini tutorial, it's all clear now.
I like the 'isolate' feature for keeping the work flowing smoothly.


Thanks for your help.



Martin. (2)
  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
5508.16 In reply to 5508.1 
Hi Martin, so after a whole bunch of testing and debugging I was finally able to track down the bug that was making your original 1mm inset here fail, it was a bug in the latest update to the geometry library.

So I've got that fixed now so the next v3 beta will be able to do that inset again ok.

Thanks for posting the file!

- 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:  blowlamp
5508.17 
Brilliant!

You seem to work very hard on making MoI as good as it can possibly be, so thanks very much for that.


Martin (2).
  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:  blowlamp
5508.18 
Michael.

I'm using the November 2012 release here.

If you extrude the conrod.3dm to (say) 20mm and do an Inset on the top face with the Thickness at 2mm, Direction = inwards, and the other two options unchecked, then no inset happens (for me).

Swapping the Direction setting or ticking the Use separate height feature seems to clear the problem - even if these options are then subsequently reverted.

Just to mention that when I tried Inset for the very first time on this beta, I saw a surface leak through the large hole of the conrod file, but I haven't seen that happen since.


Thanks for all your hard work.

Martin (2).

EDITED: 6 Nov 2012 by BLOWLAMP

  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:  DannyT (DANTAS)
5508.19 In reply to 5508.18 
That's a strange one Martin, it's quite random, sometimes it works sometimes it doesn't. I did find if inset fails, hit cancel, leave top face selected, hit inset again and it works.

Something for Michael to investigate.

-
~Danny~
  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:  blowlamp
5508.20 In reply to 5508.19 
Yes, it is Danny, but I have a supernatural ability to find these things you know :-)


Martin (2)
  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:  DannyT (DANTAS)
5508.21 In reply to 5508.20 
:) I don't know if having a supernatural ability in finding problems is a good thing or bad thing ;)

-
~Danny~
  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:  blowlamp
5508.22 In reply to 5508.21 
Errr... I'll ask the Mrs when she gets home ;-)


Martin (2).
  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:  DannyT (DANTAS)
5508.23 
Hi Martin,

Was this inset problem fixed with the V3 Nov 6th release.

Danny.
  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:  blowlamp
5508.24 In reply to 5508.23 
Danny.

I'm still not finding it 100% reliable (random fails) unless I enter both the Thickness and the Height, in which case my experience is that everything works fine and the tool is perfectly usable. This is with the 2nd version of the Nov 2012 beta - the one with the repaired .sat and .step imports/exports.


Martin (2).
  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
5508.25 In reply to 5508.24 
Hi Martin, I'm able to reproduce the occasional inconsistent behavior, so there's definitely still some other bug lurking around in there somewhere, sometimes this kind of sporadic failure can be due to bugs using uninitialized memory.

I'll continue to dig into it and see if I can track down this other bug too, it can be hard to get to the bottom of things that don't reproduce reliably though but I'll try.

- 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:  Michael Gibson
5508.26 In reply to 5508.24 
And hey, at least it works some of the time now, that's some amount of progress since in the last beta it was broken all the time... ;)

- 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:  blowlamp
5508.27 In reply to 5508.26 
Hi Michael...

...I think we all know that you won't be able to rest until you've got to the bottom of it :-)



Martin (2).
  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
5508.28 In reply to 5508.27 
Hi Martin, so I think I've finally gotten to the bottom of what was going wrong with the Inset case that you posted in this thread - it had to do with a bug in the "test for coincidence between closed curves" mechanism in the geometry library.

I've got it fixed for the next v3 beta and it looks like this case that was behaving with sporadic errors should work properly after that.

Thanks for posting the example file.

- 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
 From:  blowlamp
5508.29 In reply to 5508.28 
Nice one, Michael!

Thank you very much - I hope it didn't take too much time to find + fix.


Cheers.
Martin (2).
  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

 

 
 
Show messages:  1-14  15-29