Hello, why is the Solid Edge ST7 moving so slow? It's unworkable. I have attached the video of the st7. It only works slowly on certain pieces with many commands, this piece has 15000 part copys.
CPU usage never passed 12-20%, physical memory never passed 40%.
Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (8 CPUs), ~3.0GHz
Memory: 12288MB RAM
Available OS Memory: 12286MB RAM
Page File: 5058MB used, 31225MB available
DirectX Version: DirectX 11
Card name: NVIDIA Quadro FX 3800
Display Memory: 485 MB
Dedicated Memory: 997 MB
Solved! Go to Solution.
After watching your video....I believe this is because the component file has imported as a collection of individual surfaces, rather than a solid model.
You may be able to use the "Show Non-Stitched Edges" tool from the Surfacing tab to identify where a missing face might be, and maybe make a repair to stitch it into a solid model.
Design Manager Streetscape Limited
Solid Edge ST10 [MP2] Classic [x2 seats]
Imported from a step file, heal and stitch checked.
The most interesting thing is that if i put the piece into an assambly the software will move better.
Question: why is the software working so slowly if i have more than enough in pc specs?
You have the blue circle "i" symbol on each feature. This means you need to run the Optimize command.
Some of the downsides of non-optimized geometry include:
Window display performance
Draft Drawing view creation or updates
What the Optimize command does:
"Increases the precision and quality of the model by simplifying B-Surface definitions, heal edges, and identifies and replaces blend like faces with a PS rolling ball blend."
From the Solid Edge Help documentation:
"You can use the Optimize command to increase the quality of the imported model by simplifying B-spline definitions and healing model edges. Even if the model does not contain faults, it is always good practice to run the Optimize command since it improves the precision and complexity in most imported models."
Please take the time to run the Optimze command and see if this helps your issue.
This is a big model/file. Don't try to optimize everything all in one operation. Try to optimize in chunks of data and save between each optimization.