HEEEEELLLP!!!!

[james.lynch]

Hi everybody, I'm in a bit of a pickle! I recently upgraded to M110 and now when I open a drawing all I get is a black windowbut the datums are visable!


View attachment 801


I dont think I did anything different..


any Ideas?


Thanks


James

 

[james.lynch]

I have reinstalled the Graphics driverand ProE M110, with no luck.. I'm goign back to M80 in the hope that problem will be fixed..


nobody else had this problem no?


Btw I'm using a DELL 360 wtih a GeForce 5900, it was working fine with it before..

 

[james.lynch]

ok, reinstalled M80 but still no change.. however, i did notice that it was still looking at an old config.pro adn would you believe when I deleted that, it fixed itself.. I dunno what option was causing the problem though..


is there a way to compare two config.pro files?

 

[cristelino]

TryView attachment 802
Edited by: cristelino

 

[Pommares]

Have you tried changing the background color?


Sometimes after a conversion, if the lines happen to have been set to black, you want any other color for a background. As some of the stuff is visible, it occurs to me that that might just possibly be the problem. Happened to me once.


Guy

 

[james.lynch]

cristelino,


yeah looked at that, it's set to opengl..


Pommares,


nothing to do with background colours...

not to worry, I deleted the old config.pro and now it's sorted, I have to remack some of the changes that I had put it but that won't take that long.


Thanks everybody for your help anyway!


James

 

[cristelino]

NOT ONLY OPENGL

set display edge

clearance triangulation

edge display quality



Or is posible to have an conflict motherboard with some components



crsitelino

 

[james.lynch]

no I dont think it was a conflict wir any hardware.. it was workign fine.. adn now that I have deleted the old config.pro file, it is ok again...


I don't know enough about the config.pro setting to actually take a really good indepth look at what got corrupted or what I modified (I mean messed up!

) to cause the error..


I would have liked to have gotten it sorted but this workaround sorted it out..


thanks anyway,


James