Bit of a problem with Inset.
 1-19  20-29

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-19  20-29