Startup TOOLS: Changes in the data packages
Version 9.0.0.0
Changes in the data packages can affect files of the project or data directories. These are subdirectories of the system directories projects or data:
–Creo configuration settings of the standard startup projects: <operatingenvironment>\parametric\configuration\projects
e. g., in the startup project directory for Creo 12: std_sut_creo_c12p.
–Object data for standard objects: <operatingenvironment>\parametric\data
e. g., in the data directory for Creo 12: sut_creo12.
— Names of files and directories changed
The project and data directories have been renamed, as well as the files for the Creo configuration options (configuration blocks).
The notation has been changed as follows, here in data for Creo7.
Data directory |
Project directory |
Configuration blocks (config_*.pro files) |
|||
old: new: |
std_sut_int_de_creo7p sut_creo7 |
old: new: |
std_sut_int_de_creo7p std_sut_creo7p |
old: new: |
config_sut_de_c7p_core.pro config_sut_c7p_core.pro |
— Changes across versions
As of version 9.0.0.0, changes to configuration options will be made uniformly for all Creo versions. A specific version is therefore no longer specified in the changed files and is replaced by the * character, e. g. config_sut_c*p_core.pro.
— Configuration settings for startup projects
The following Creo configuration options have been added (+), removed (–), or changed (~) in the config_*.pro files (configuration blocks) of the standard startup projects:
Versions: Creo 4.0 – 9.0
In file _config_sut_c*p_nc.pro
~ |
Anpassung aller Pfade an neue Umgebungsvariablen. |
In file config_sut_c*p_dir_file.pro
+ |
intf_pv_recipe_dir |
$GTS_DATA\config\pview |
+ |
intf_out_pvs_recipe_file |
$GTS_DATA\config\pview\stools_pvs_pdf.rcp |
~ |
quick_print_drawing_template |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_quickprint.drw —> |
~ |
search_path_file |
$GTS_DATA\config\search_int_de.pro —> |
~ |
template_solidpart |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_start_prt.prt —> |
~ |
template_sheetmetalpart |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_start_smt.prt —> $GTS_DATA\library_dir\start_model_dir\sut_start_smt.prt |
~ |
template_designasm |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_start_asm.asm —> $GTS_DATA\library_dir\start_model_dir\sut_start_asm.asm |
~ |
template_drawing |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_start_drw.drw —> |
In file config_sut_de_c*p_mapkeys.pro
~ |
Umbenennen aller *.frm Dateien |
In file config_sut_de_c*p_piping.pro
~ |
display_thick_pipes |
yes — no |
~ |
piping_design_method |
spec_driven —> user_driven |
~ |
pipeline_solid_start_part_name |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_start_pipe.prt —> |
~ |
pipeline_start_assembly_name |
$GTS_DATA\library_dir\start_model_dir\sut_int_de_start_asm.asm —> |
~ |
pipe_solid_label_format |
RO,-,NUMBER- —> RO-NUMBER- |
~ |
piping_project_data_dir |
$GTS_DATA\library_dir\piping_config\project_dir —> $GTS_DATA\library_dir\piping_config\project_data_dir |
~ |
piping_spec_dir_file |
$GTS_DATA\library_dir\piping_config\project_dir\spec_inneo_sut.csv —> |
– |
piping_re_convert |
automatic |
File
+ |
config_sut_c*p_piping_mapkey.pro |
— Object data: New settings for hatching
When updating to version 9.0.0. and newer, new settings for color effects and material files must be made in the data packages.
Creo Parametric 4.0 introduced the default hatching format *.pat. Before, Creo Parametric used its own format *.xch. Starting with Creo Parametric 9.0, the default value changed from XCH to PAT.
The configuration option default_hatch_type must be set to the new default PAT. All Startup TOOLS XCH files are converted to PAT format and are no longer delivered as XCH files.
Please note: Changes in data packages can be diverse and vary in complexity. In a simple case, a Creo Parametric symbol may be changed – in this case only one file would be affected, which can easily be transferred manually after a user check. However, if a work process is changed, e. g. the use of appearances and hatch definitions in material files, many files and configuration settings will be affected. The effects of each file must therefore be checked. It is recommended to use a test environment. |