Skip to main content
C
CS_96622973-Newcomer
3-Newcomer
April 28, 2025
Solved

Zoom Delay after update to Creo Elements/Direct Modeling 20.7

  • April 28, 2025
  • 2 replies
  • 1169 views

Hello,

i've done an update from Creo Elements/Direct Modeling 20.2 to Creo Elements/Direct Modeling 20.7.1.1.

Now the same assemblies are very slow in zooming and have sometimes a delay in movement.

I use WIN10 Pro, HP Z4 G4 Workstation with Nivdia Quadro P2000 and 2x16GB DDR4 RAM. Can i make any settings or hardware upgrade to make the programm as fast as it was with V20.2? Or should i install a version beetween V20.2 and V20.7 with more functions than V20.2 but comparable speed?

BR, Chris

 

Best answer by der_Wolfgang

SDPIXELFORMAT= Software is really the very last choice and a compatibility test only IMHO. Every thing what (even 15 year old) CPUs+ GPUs can do in hardware for graphic display is done in Software on the CPU (may be in a single thread)  There fore it is slow, SLOW, SLOW.

Have there been a graphic driver update in the same time period?

Well, why SETTING and UN-SETTING the environment variable should solve the problem .   Uhhh .  that's magic and not understandable. (IMHO).

Any way.   Keep your system as it it and let's keep the fingers crossed in addition.


Thanks for the feedback!

One Hint @ all . :   better try to keep your old version of a software for some weeks to be able to compare old and new version's behaviour..   Well,  if the specific setup.exe does allow parallel installations (which is not that common nowadays)


2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
April 28, 2025

Take a look - "Highly delayed zoom when zooming in and out frequently in Creo Elements/Direct Modeling Annotation": https://www.ptc.com/de/support/article/cs328535 

C
CS_96622973-NewcomerAuthor
3-Newcomer
April 28, 2025

Hello VladimirN, 

thx for fast response, but the linked articel doesn't help to solve the problem. I updated from also V20.2 ...

BR

 
D
der_Wolfgang13-Aquamarine
13-Aquamarine
April 30, 2025

windows has it's own (weired?) stragety to assign a high end graphic card to a process running!


Are you sure that the GPU is doing the job and not the CPU?  ==>>  the Task manager has a tab to show performance of different major components. When zooming / panning the 3D view port the GPU should get under load, not the CPU.

 

What is the situation on your system?

 

  • AFAIK you can assign the Nivdia Quadro P2000 to the process soliddesigner.exe using a Nivdia tool ("optimization" / "performance" ..  )
  • Or you can disable the build in graphic card at all, AFAIR in the system's BIOS. 

Both ways are already described.

So it might be by installing Modeling 20.7 Windows was doing the wrong guess (maybe it will be diced) 

C
CS_96622973-NewcomerAuthor
3-Newcomer
May 5, 2025

Hello Wolfgang,

thx for the hint of task manager performance... i saw, that the GPU is doing the job, if i zoom in/out.

Then i tried out to load the old version V20.2 ... and now the same slow speed zooming occured!

I remembered, that i had an error at opening new views in modeling after first installing V20.7.

"Fehler bei Aktion create_vp/signal/sigsegv"

I found a solution in the cad.de forum by setting an environment variable in the win system:

  • Name der Variablen: SDPIXELFORMAT
  • Wert der Variablen: SOFTWARE

After this the failure disappeared .... but after this zooming got slow.

Then I tried to erase the variable again, and V20.2 was fast, as it was before ... and what a WONDER: Also V20.7 functions now without problem and is also fast 🙂

Thx too all, who tried to help me!

D
der_Wolfgang13-AquamarineAnswer
13-Aquamarine
May 5, 2025

SDPIXELFORMAT= Software is really the very last choice and a compatibility test only IMHO. Every thing what (even 15 year old) CPUs+ GPUs can do in hardware for graphic display is done in Software on the CPU (may be in a single thread)  There fore it is slow, SLOW, SLOW.

Have there been a graphic driver update in the same time period?

Well, why SETTING and UN-SETTING the environment variable should solve the problem .   Uhhh .  that's magic and not understandable. (IMHO).

Any way.   Keep your system as it it and let's keep the fingers crossed in addition.


Thanks for the feedback!

One Hint @ all . :   better try to keep your old version of a software for some weeks to be able to compare old and new version's behaviour..   Well,  if the specific setup.exe does allow parallel installations (which is not that common nowadays)


Terms & ConditionsCookie settingsAccessibility statement