Skip to main content
1-Visitor
Mar 19, 2025 1:44 PM UTC
Solved

Black screen on Creo

LK_13027707_0-1742391821826.png

Hi, I use creo 11.0 edition. When I want to select plane nothing happens

 

BenLoosliAnswer
23-Emerald III
Mar 19, 2025 2:48 PM UTC

Try using graphics win32_gdi in a clean local config.pro.

Also try this solution: Article - CS348177 - The graphics window is black with the Model Tree displaying the model in Creo Parametric

We have 1 workstation that works fine with Creo 9 but gets the black screen with Creo 11.

Also try update your graphics drivers. What graphics card is in your computer?

11 replies

Dale_Rosema
23-Emerald IV
Mar 19, 2025 1:51 PM UTC

Your top & front plane seem to be hidden. Is you right plane hidden as well?

Translate
BenLoosli23-Emerald IIIAnswer
23-Emerald III
Mar 19, 2025 2:48 PM UTC

Try using graphics win32_gdi in a clean local config.pro.

Also try this solution: Article - CS348177 - The graphics window is black with the Model Tree displaying the model in Creo Parametric

We have 1 workstation that works fine with Creo 9 but gets the black screen with Creo 11.

Also try update your graphics drivers. What graphics card is in your computer?

Translate
1-Visitor
Mar 19, 2025 3:35 PM UTC

Hello, i added graphics win32_gdi to config.pro file and run it and it works

Translate
Dale_Rosema
23-Emerald IV
Mar 19, 2025 5:42 PM UTC

The is then showing you that it is a video card / video drivers issue.

win32_gdi just clears everything out to help you with diagnosis.

Now you have to take it (win_gdi) out and find out if the video card and drivers are PTC approved.

Typically the latest and greatest drivers have not been proven out and should not be automatically updated.

 

You'll take a performance hit if you leave it in your config.pro.

Translate
24-Ruby III
Mar 20, 2025 1:13 PM UTC

Hi,

what graphic card is installed in your computer?

Translate
1-Visitor
Mar 20, 2025 2:37 PM UTC
I have nvidia 1650
Translate
StephenW
23-Emerald III
Mar 20, 2025 2:43 PM UTC

Its a gaming card, so it's not supported. That doesn't mean you won't be able to get it working.

You will have to experiment with driver downloads. Sometimes the latest driver is all you need, sometimes you have to try random drivers for your card/system. Trial and error is your best bet to really fix the problem.

The graphic win32_gdi option will work but if you do anything other than simple stuff, it will be slow to continue to use.

If you do testing on drivers, remove the option from your config.pro before testing. You can always re-add it back if you don't find any working drivers or until you find one.

Translate
24-Ruby III
Mar 20, 2025 4:24 PM UTC

Hi,

you can also add following options into config.pro file and test their influence.

 

enable_opengl_fbo no
enable_opengl_vbo no
enable_opengl_shader no

Translate
MikeBennett
17-Peridot
Mar 21, 2025 7:33 PM UTC

Hello @LK_13027707 

 

This looks like an antialiasing setting issue like that described in CS348177.  In Creo 11.0, the default value of config.pro option enable_fsaa was changed from off to 8 so consider changing this back or exploring other values.  This option can also be changed in File > Options > Entity Display > Anti-Aliasing

 

Mike

Translate