I have an installation of Creo 2.0 Academic Edition on about 200 workstations with a floating license server.
Whenever I first load Creo on a freshly imaged machine, the graphics are crazy slow even on simple geometry. Just mousing over a simple cube causes the computer to slowly render the wireframe for about 5 seconds and Creo completely frozen until the process completes. Once I paste graphics win32_gdi into the config.pro file, it the problem seems resolved.
We've been teaching Creo/Pro-E since Wildfire3 and have run into this same problem in every version (since WF4) with many different computers including my personal computer which is an Intel i7 machine with 6gb of ram and dual nvidia graphics cards. The computer that I'm currently teaching with is a Core2 Duo Dell with 2gb of ram and a Radeon X1300. It's a little dated but I have to imagine that it can handle the simple geometry that I'm teaching to high school students.
Attached is a screenshot taken while Creo is choking on the graphics of an imported STEP file. The exact same thing happens on parts and assemblies created in Creo.
My questions are:
What does the graphics win32_gdi line actually do?
And...
Once graphics win32_gdi is inserted into the config.pro file, is Creo taking advantage of any hardware graphics acceleration?