11-Garnet

Question

Creo 3.0 first thoughts?

Forum|Forum|11 years ago
July 23, 2014
41 replies
13853 views

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

Show previous replies

D

davehaigh

13-Aquamarine

Speaking of which, I've tried to find a way to report the graphics hardware using a script. Anyone have a clean easy way to get a report of the graphics card via the command line?
Version of the graphics driver would be helpful also.

David Haigh

T

TomU

23-Emerald IV

Right. Here is the full statement:

PTC Creo 3.0 requires a graphics cards supporting OpenGL 4.0 or later.

E

EricVidra

1-Visitor

Update your drivers to the latest (Nvidia 307.45) for FX540 ,FX550, FX560, FX580 now support OpenGL 4.2

We learned this the hard way with some users running outdated drivers going into Creo 2.0

Eric

"I am employed by Toyota but I am not speaking on behalf of the Company. These are my personal opinions only."

D

davehaigh

13-Aquamarine

I did a quick search, and found this: (typed into a command shell)

C:\Users\haigh1>for /F "tokens=* skip=1" %n in ('WMIC path Win32_VideoController get Name ^| findstr ".") do set GPU_NAME=%n

:\Users\haigh1>set GPU_NAME=NVIDIA Quadro 3000M

:\Users\haigh1>set GPU_NAME=LANDesk Remote Control Mirror Driver

:\Users\haigh1>set GPU_NAME=Intel(R) HD Graphics Family

One problem it resets the GPU_NAME with each line of output. So when I echo the parameter it gives me the one I don't want.

C:\Users\haigh1>echo %GPU_NAME%
Intel(R) HD Graphics Family

David Haigh

S

STEVEG

21-Topaz I

I use this:
msinfo32 /report sysinfo.txt

Then this:
find "Adapter Description" sysinfo.txt >> vid_card.txt

I'm sure it could be put together but when I set up a new computer I write that file out for other info too.

Steve G

D

DamianCastillo

1-Visitor

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.

P

proed

1-Visitor

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...

)

D

dgschaefer

21-Topaz II

Anyone have a link that shows a complete list of what Nvidia cards & drivers do support 4.0? A quick search at Nvidia's web site didn't reveal anything.

My month old laptop with a K3100M is not listed on that doc linked below, but I certainly hope it would support 4.0.

--