You are not logged in.
Pages: 1
We are using Vericut 6.0.4 with a Dell 470, 3 Gb RAM, 3,3 Ghz double Xeon processor. We have problems with the Verticut simulation to the CNC machine converting, it really takes a lot of time. We suppose, that it should need more cache. Do anyone have any idea, why is it so slow, or any solutions for a faster configuration.
Thank you for your help in anticipation
Offline
Agree,
With every version it looks like things are slowing down.
We have brand new top of the bill systems, and with V6.0.4, 5-axis motion is REEEEEAAAAALLLLLLYYYYY slowwwwwwwwww.
I have posted some questions on this in the past, but never got a satisfaying answer.
Patrick Delisse
KMWE Aerospace - https://www.kmwe.com
(Vericut V9.5, Siemens NX2206, Campost)
Offline
I have Vericut 6.0.1 and two computers.
Dell 360 with 2Gb Ram and Ati FireGL.
This is my old computer in work and at this moment is pc of my colleaque.
Speed on this pc is relative good(5-axis simulate on turbine blades).
Dell M65 with 2Gb Ram and Nvidia FX350(Core Duo 2700).
On identical job is Vericut faster by 30%.
For starting simulate use cutting tollerance 0.8 - 1.2 according to size of blade and disable Apply Accelaration to cycle time.
Enable OpenGL support and use only one view(workpiece).
excuse me please my english:)
Manufacturing of Turbine blades
Offline
The views you have open make a difference in display speed.
Comparatively:
Workpiece Fast
Machine View with OPENGL Fast
Machine/Cut Stock SLOW
2 views, a Workpiece and a Machine are faster than a single Machine/Cut Stock view.
Also the screen size and zoom of each window will effect speed some.
Properties | Tolerance settings effect speed. With X64 and more memory you can run tighter tolerances, but the speed will slow down.
Offline
Pages: 1