Doug, one of the wierder things about this problem is that it only effects shaded mode, no other view mode. The shading can sometimes be brought back with hide/unhide. Anyway, the parts only disappear after a file save, the very next time the part is moved. It also isn't consistent. I work a lot in shaded mode, but the times when it was left in wireframe and saved and later moved, I could turn on shading, no disappearing part. No other graphics functions are effected, including some of the more sophisticated ones, such as those in the Visibilities menus (Depth cue, clipping). The last time I saw this problem was on a Unix system when
20 came in. But after awhile, several builds down the road, the problem went away.
Re: the accuracy setting. Yes, there's a lot more attributable to it than you'd realize, especially any problems with export quality. That's one of the reasons I leave mine fairly high by default in the start parts, one decimal away from the limit. I've never heard of 'too high' being a problem, except in regen time. Fewer regen failures, geom checks, shelling or surface offset failures make it worth it. I've even fixed some gross failures of imported iges surfaces or got 'Heal geometry' to work by jacking up the accuracy. I'm constantly amazed that the software 'knows' all it needs to know to set the appropriate accuracy by itself, yet leaves us to fiddle with it. Why?
: > First, since the program is written and compiled for Unix, I believe the : graphics : > drivers are based on Wildcat. Everything non-Wildcat (3dlabs), is foreign : and some : > kind of approximation, some kind of 'workaround', of which, PTC is the : Supreme : > Ruler and Pro/e is the 'workaround' capital. This is most true on : graphics. If you : > are on Windows, this graphics is the classical ugly red-headed stepchild, : scorned : > and rejected. No, there is no DirectDraw or Direct3D in Pro/e. OpenGL on : Pro/e is : > a 'close approximation', virtually a myth. So, nothing about it is lawful : and : > predictable. : >
: > When PTC gives up its clever ONEDISK compile/license/distribution : strategy, with : > endless patching and 'workarounds', when it does a two-steam (Unix : [multi-flavor] : > and Windows [NT/non-NT] release), when it conducts licensing 'less : efficiently', : > you will notice a big difference in the code and the quality ~ less : goofiness, for : > sure. : >
: > If you want to see a very nice graphical program, written by PTC, for the : Windows : > platform, and one which uses DirectX facilities, do yourself a favor and : download : > Pro/DESKTOP Express. It's free and it's an eye-opener. Try any of the : models that : > come with it, viewed as transparent (icons at bottom left, third from : left), then : > press the 'Smiley face' icon in the bottom middle. If Pro/e graphics were : this : > good, you'd never hear a peep out of anyone. : >
: > David Janes : >
: > : > The problem is models disappear in shaded display mode (the default in : > : > Wildfire) : > : > The shaded image will diappear on a simple model after working for : while, : > : > and on assemblies some of the parts disappear. They will highlight if : you : > : > pass the cursser over them, and the reappear if we change to one of : the line : > : > draw modes ie: hidden lines gray, or wire frame or no hidden lines. : > : > Screen is set to 1280 x 1024 pixels, changing doesn't seem to help. : > : >
: > : > Anyone have asimilar problem and find a fix? : > : >
: > : > Mike D : > : >
: > : >
: > : : > : : >