You are not logged in.
We uncovered a problem in VERICUT 7.1.1 that could, under specific conditions, cause VERICUT to miss collisions between moving machine components and the cut stock or fixtures. Another symptom of this problem is inappropriately slow simulation when collision checking is enabled and moving machine components are close to the cut stock or fixtures.
The potential for a missed collision (and/or slow simulation speed) occurs when memory is almost completely consumed, either by VERICUT or by other programs running on the computer. The bad behaviour is not consistent and may or may not occur depending on how memory is allocated while VERICUT is simulating.
This problem was discovered late yesterday, and we are working on a solution right now. As soon as it is fixed we will release VERICUT 7.1.2 and publish its availability to all 7.1.1 recipients.
If you think you may be encountering this problem, please contact your local CGTech technical support. If you are willing and able to share your VERICUT project we will use it for testing and to ensure we've implemented a robust solution.
Sorry for the trouble,
Bill Hasenjaeger
CGTech
Offline
At yesterday I try to solve the same problem - VERICUT not detect any collision for Tool and Fixture, but when I uncheck "birds" - see below, I forget about it - problem was solved.
I want make good advise for VERICUT developers - please, uncheck this options by default or NearMiss must be >0
Gentleman will walk but never run.
http://www.postprocessor.ru
Offline
any new informations?
uncheck "birds" does not solve the problem with speed...
Simulation in 7.1.1 is slower for me twice
Manufacturing of Turbine blades
Offline
The problem described in this posting is now fixed and VERICUT 7.1.2's release will happen this week.
We will distribute 7.1.2 via our normal download method for a point release. An installer CD is available upon request through your usual VERICUT distribution contact.
An email with download instructions will go out this week once the release is available.
Thank you for your patience and sorry for the trouble.
Bill
PS I do not understand the 2 posts, nor the references to "birds". They seem unrelated to this internal coding problem. On the speed issue, I'd suggest working with your local VERICUT supplier as there are many possible reasons for slower simulation speed.
Offline
I try to explain topic#2
When I read your start topic, my customer send me a problem project with subject - "Help me! VERICUT missed collision between Tool and Fixture!!!". When we uncheck "birds" - problem was solved (Vericut 7.1.1), of course - for this project, for this case. If all checkbox set as checked - VERICUT "don't see" any collision between Tool and Fixture - Near Miss is 0.0..
Thank you and excuse me.
Gentleman will walk but never run.
http://www.postprocessor.ru
Offline
Dictionary.com> Bird = any warm-blooded vertebrate of the class Aves, having a body covered with feathers, forelimbs modified into wings, scaly legs, a beak, and no teeth, and bearing young in a hard-shelled egg.
I think it's great that Vericut considers birds are worthy of a checkbox, but exactly what does it do differently when you check or uncheck "birds?"
Austin NC APT administrator.
Custom configure GPost for Pro/E,
and other ANC applications.
Offline
1. Excuse me my English. I know who is birds, in Russian if I see checked check-box - I can say - "Bird in box". Little-little bird... Like humming-bird. If seriously - Yes, if this checkboxes checked - no detection any collision with tool and fixture.
Gentleman will walk but never run.
http://www.postprocessor.ru
Offline
After 6 months, I finally figured it out:
Michael Stevenson
Vericut Programmer
PCC Aerostructures
Offline
Offline