graphical problem

[MORENO100]

Hello everyone,
I am moving the first steps to pass from wf5 to creo2, but I immediately encapsulated in a big graphic problem that I did not have in wf5.
I try to expose my problem even if it will not be very simple... .
I use a picture nvidia card k2200, I create 2 m070 and the problem affects the edges displayed in the display "shading with edges".

in creo2 known that if in a set, displayed in "shading with edges", imposed a component with the visualization style "hidden lines", the edges of the other components alter graphically in a horrid manner and also cause a delay/lag at end spin almost as if the program tries to recalculate them. using wf5 I never had any problems like this.

from the innumerable evidence that I did it seems that I can solve everything only by predicting the whole set in "shading with edges" display style. This is just an escamotage to solve the problem, so I trust in your more "official" solution.

Do you also find these problems? How did you solve them?

thanks and good work.

 

[nino67]

Do you also find these problems? How did you solve them?
thanks and good work.

hi moreno100,

I can't replicate what you declared with creo 2 m230, graphics card nvidia k4200, all wu windows 7 to 64bit.

greetings

 

[tecnico_plast]

Could be a video card driver problem, did you try to update it?

 

[nino67]

Could be a video card driver problem, did you try to update it?

I also agree that it might be the driver.... I am using version 341.92.

greetings

 

[MORENO100]

I tried to install the driver 341.92 but the problem remains.
I try to explain the initial problem better by helping me with illustrations.
n.b. I recommend you to do the tests on a backup set because if you save the display style I don't know how to restore it.

 

[320i S]

quoting who tells you to try different drivers, often even certified drivers have some discomfort.
in the past I had much worse problems and I went one step at a time, i.e. installing a direct version of better driver, found the good one, I no longer changed.

 

[MORENO100]

update to my problem:
from the tests I have concluded that the graphic problem I presented above is not given by the driver but by the version of the creo 2.0:

creo 2.0 version m010: presents the problem
creo 2.0 version m020: presents the problem
creo 2.0 version m070: presents the problem
create 2.0 version m230: don't match the problem, solved!! !

 

[320i S]

Well, good to know.

 

[MORENO100]

another interesting note on the versions I tested:
- until the m020 version I detect big stability problems, from the m070 I did not find these problems, I can always open axioms from more than 1000 components without that the message "unreversible error" or without that I collapsed directly.

 

[320i S]

by personal experience, the first versions "m", always suffer from some problem, which are gradually resolved.
But it happens that there is the "zampino" of the maths (made/imported/modified), it is not rare that a set (no matter the size if there is enough ram) that does not want to open itself in main representation, opening it directly in representation that functions, suppressing components and then gradually recovering them, you can find what does not go more specific.

in another company where I worked, however we never installed by default a new version "m" if there were no problems with that installed and however only after a test of a couple of months on a station, it was going to spread it.