| Title: | Pro/ENGINEER Conference |
| Notice: | Do a DIR/TITLE before writing a new note |
| Moderator: | ALLVAX::SYSTEM |
| Created: | Fri Oct 07 1988 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 426 |
| Total number of notes: | 1446 |
Hi folks, A customer upgraded from NT 3.51 to 4.0 and seems to have lost some functionality in Pro/E and Windows NT. He has an Alpha (machine unknown) with a PS 4D/20. If he uses the built-in screen capture functions (Alt-PrntScrn and Ctrl-PrntScrn) or if he uses the Pro/E command View | Cosmetic | Shade | Save and a subsequent View | Cosmetic | Shade | Restore the colors in the screen capture and the colors in the saved image are incorrect. The customer thinks the problems are somehow related because the incorrect colors are identical between the NT screen capture and the Pro/E saved image. He is using the latest driver, GSS v4.1. He also stated that an indentically configured machine (NT4.0, GSS v4.1) with an older ZLXp-E3 works fine. Thanks, James [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 425.1 | WRKSYS::CHALTAS | Fetchez la vache! | Thu May 29 1997 12:48 | 6 | |
This is expected behavior, except for the part where a ZLXp-E3 works
fine. It's been corrected in a recent build of Pro/E -- Don't
know the build number yet.
The problem is that Pro/E is using a 12-bit OpenGL pixel format,
while Windows is using a 24-bit pixel format.
| |||||
| 425.2 | fixed datecode is 9721 | HYDRA::DONSBACH | Jeff Donsbach, Software Partner Engineering, DTN 297-6862 | Thu May 29 1997 19:10 | 9 |
This is a VERY old problem (like 2 years or more!)
I just recently fixed it. The fix is in V18, DateCode 9721 or later.
Tell the customer to request 9721 as soon as it's available from PTC.
-Jeff
| |||||
| 425.3 | it's a bug on E3 too (but fixed) | HYDRA::DONSBACH | Jeff Donsbach, Software Partner Engineering, DTN 297-6862 | Thu May 29 1997 19:12 | 10 |
Oh, if the E3 works fine, he's not using OpenGL!
Chances are he doesn't have a 3D driver loaded and doesn't even
know it.
The work around for the problem has always been to run in GDI
graphics mode.
-Jeff
| |||||