The old machine was a Xeon 3.2GHz Dell 690. It rebuilt the punch holder in 260s and Scooby in 71s - all as predicted from the spreadsheet. Graphics performance was poor - very sluggish and don't even think about realview (QuadroFX 4500)
A new workstation was ordered, Dell because that's what the company buys. This meant that it had to be an expensive Xeon again (T5500, Xeon W5580 3.2GHz, XP64, 12GB RAM, 10k RPM disks, SW2009 SP4.1). I have always had Quadro FX graphics cards and had a bit of a predjudice against anything else, particularly ATI. However, reading some comments on this forum and reading specs, particularly memory bandwidth, I decided on the FirePro V8700.
The new system cost a whopping £3000 including a substantial discount from Dell. I could have bought an overclocked Core i7 running at 4GHz for half that. Our IT manager recons overclocking is unreliable and for home use rather that business "mission critical" systems.
Well, benchmark rebuild results are exactly as predicted, 63s for the punch holder and 20s for Scooby - a big improvement and general modelling is much more snappy and responsive. The problem is graphics performance. It really is not that much better than the old system. I have tried all the settings in SW and yes, "use software open GL" is off. Model rotation is jerky and parts turn into blocks. I have compared using the same assemblies which are not complex and do not have more than 100 parts although some are transparent which I know slows things down.
Processor usage during model rotation is 25%. That leaves three cores and a graphics processor twiddling their thumbs and me feeling as though I am wading through treacle.
Is this as good as it gets?
SolidworksAdministration
The models turning to blocks when rotating is a SW system option on your computer.
Go to Tools > Options > System Options > Performance > Level of Detail slider and push that all the way to the left (Off).
Do you have an assembly that you can post that exhibits this issue? I will see how it the graphics works on my system.
Cheers,
Anna
In addition to Anna's comments, I have a few questions.
1. Do you have realview turned on? Do you have shadows turned on? What scene do you use for these assemblies?
- Try turning off shadows, and see if that fixes it. There are also different scenes (with/without reflections, with/without shadows) and that can drastically effect your rotational speed if realview is turned on.
2. Under Tools>Options>Document Properties>Image Quality>Shaded and draft quality HLR/HLV resolution, what is the slider set to. Is it in the red zone?
- Red zone bad. make sure that slider (and all your part & assembly templates) have it set somewhere else. If you are having performance issues, I suggest somewhere closer to the middle or right 3/4. It should still make circles look like circles, but help some (if it was in the red).
... and don't forget the Vertical Sync 'problem' ... https://forum.solidworks.com/message/22182#22182
Thanks but I already tried all of these settings - except for the vertical sync. the only likely candidate for that in the ATI Catalyst was "wait for vertical refresh". Turning that to "always off" didn't make any difference.
If I hide all the transparent parts in the assembly, performance is reasonable. However, I would have thought that this system could cope with that. In fact, when rotating, it stalls and judders when the transparent components come into view.
Anna, I would have liked you to have the assembly because you are using the same graphics card. However, I cannot make that data publicly available. Thanks for the offer anyway.
I suspect that this is a simple case of not managing my own expectations. I wonder if I should have stuck with Quadro!
Check that the correct driver is installed.
According to http://www.solidworks.com/sw/support/videocardtesting.html it should be 8.543.1.3
If that driver is already installed, maybe try re-installing it, or installing the latest offering from the ATI site.
Correct driver was installed (the Dell version). The latest ATI offering has made no difference.
Kelvin, why have you suddenly become "2242"