Provides Customer Support for a ll certified a nd/or supported gr a phicsĬards. Partner to confirm the availability of this functionality with a given graphicsĬard that has been certified with Pro/ENGINEER Wildfire 4.0. **Please consult with AMD, NVIDIA, or the hardware platform Note: in the event that dual monitor mode fails, we advise use of Span mode as Solution will not be submitted for formal certification as a complete Resolve issues arising when running in dual monitor mode, however, the entire Monitor support**, PTC expects that it will run in this Your graphics card is certified for Pro/ENGINEER Wildfire 4.0 and provides dual Testing of some graphics card models from 3DLabs, ATI and NVIDIA that support dual monitor capabilities.
PTC PRO ENGINEER WILDFIRE 3 WINDOWS
Monitor support is provided in Pro/ENGINEER Wildfire 4.0 on the Windows
PTC PRO ENGINEER WILDFIRE 3 DRIVER
To ensure the comp a tibility of a gr a phics driver with Pro/ENGINEER Wildfire 4.0, a PTC -certified h a rdw a re configur a tion is recommended. Oper a ting systems, the Windows limit isĪvailable with the production shipment of Pro/ENGINEER Wildfire 4.0 in earlyĭet a iled inform a tion on loc a liz a tion for this product, ple a se clickįor 3D-h a rdw a re a cceler a tion, a n OpenGL gr a phics c a rd must be used th a t h a s been tested in a PTC -certifiedĬonfigur a tion. Microsoft TCP /IP Ethernet Network Ad a pter (or higher) resolution support with 24-bit or gre a ter color (Mozill a 1.7.8) is embedded in Pro/Engineer Profession a l Edition Windows XP Home Editionįor individu a l vendor processor support You need to make sure the config files are in the correct directories.Pentium/Xeon/Core Duo/Core 2 Duo f a mily These custom configuration files usually apply to specific projects. You can create and store custom configuration files in your current working directory. The config.pro file does not, however, override any config.sup entries. Notes: The local config.pro and config.win files (in your startup directory) are the last to be read therefore, they override any conflicting configuration file option entries. Startup directory ? This is your current or working directory when you start Pro/ENGINEER. Placing your configuration files here lets you start Pro/ENGINEER from any directory without having a copy of the files in each directory.ģ. Login directory ? This is the home directory for your login ID. Any user starting Pro/ENGINEER from this loadpoint uses the values in this file.Ģ. loadpoint/text (loadpoint is the Pro/ENGINEER installation directory) ? Your system administrator may have put configuration files in this location to support company standards for windows configuration settings, formats and libraries. It then searches for and reads in configuration files (config.pro and config.win) from the following directories in the following order:ġ. If a particular option is present in more than one configuration file, Pro/ENGINEER applies the most current setting.Īt startup, Pro/ENGINEER first reads in a protected system configuration file called config.sup. Pro/ENGINEER reads configuration files automatically from several areas. How Pro/ENGINEER Reads Configuration Files at Startup "I'm only running Pro/E 2001 but here is some information from the help files. RE: Making mapkeys always active Wildfire 3.0 PeterStock (Mechanical) 20 Apr 07 13:36įrom thread554-183010: config.pro gets saved automatically to login dir.: Peter, do you work at Pollak in MA or somewhere else? Pro/E disables you from renaming the sequence from the Modify option in the Mapkey dialog although you could rename in Options if you choose to keep your mapkeys in the config file and use save changed. Lcs for Layer Create Surfs and wanted a mapkey to create a solid layer I could search for lcs and rename lcs lcsu and delete the lcs mapkey then use lcso for the Solid Layer mapkey. If you ever run into the case where you have to rename a mapkey open the allmapkey file in a text editor and search for "key_sequence I had a mapkey with sequence Then when I add mapkeys I hit save all and enter allmapkey#.pro as the name and then delete the old allmapkey and remove the # from the latest allmapkey. I generally keep a file called allmapkey.pro in my working directory or in the default company location and use a mapkey that loads the mapkeys by going into Options and opening allmapkey using a direct path and then reload the config.pro so that the mapkeys don't get saved in both files.
0 kommentar(er)
