I attended a Hands On Workshop yesterday, and today I'm really digging into it on my own computer (Dell M3800, 16 Gb RAM).
It's freezing (Creo Parametric Not Responding) on my computer. A lot. On simple stuff, like reorienting the model, and creating a boundary blend. We don't plan on deploying until testing M020 for a couple months at the earliest, but as it is on my computer, the user experience is too painful.
Anyone else play with it yet?
David R. Martin II
Senior CAD Application Specialist
Amazon
I never expect to run F000 as an official release. F000 is for internal testing, M010 is the only build I would consider installing for my users and this is only after I tested it to make sure things work. I am curious to see how much of the Menu Manager has been integrated into the UI. I think it's sad that we are still dealing with a UI element from Pre-Wildfire days.
Hi folks
On the topic of getting computer specs via command line, for years I've run with this (examples below):
- Creo startup on each computer uses dxdiag to store the spec
- These spec files are processed
- The stats are presented in simple pie charts for graphics, processor, memory, language, etc
It all runs in the background, you just view the web-pages for the latest charts of specs. Occasionally clear out old specs for computers no longer in use.
Regards
Ed
DxDiag:
dxdiag /whql:off /t creo~%COMPUTERNAME%.txt
- copy these to common area
Process data:
for /F %%f in ('dir /b creo~*') do (
find "Card name:" < %%f >>log
find "Username:" < %%f >>log
etc...
)
What about a command to find what version of OpenGL a graphics card currently supports.
Steve G
For the record, my issues may be more related to the Dell M3800 than Creo 3.0. I dropped my M3800 off with our IT department because it blue screens a lot. (Before the M3800, it had been years since the old BSOD.) The M3800 has a ton of graphics issues.
Both Creo Parametric 3.0 and Direct 3.0 appear to work fine on my old Lenovo W530.
David R. Martin II
Senior CAD Application Specialist
Amazon