What should I do if a file is generated when PROE opens a file after PROE is opened?

Proe is a very memory-intensive software,If the memory is less than 2G,Open some relatively large components or parts,It will automatically pop out,If you have a small memory,Upgrade is a good way。

In addition, PROE is developed on the UNIX system, and the rules for reading memory are different from those of Windows, and sometimes (not often) it will conflict with other file memory, resulting in an exit. If you open the same file and bounce out frequently, you can do this:

2. Or restart.

ug files are often corrupted and cause the previous work to be wasted, but proe rarely has this situation (or never, I have been using proe for six years, and I have never encountered it), and when I quit for no reason, I directly find the reason for the computer itself.

What about graphics cards? The landlord mainly considers the issue of hardware compatibility. Software compatible with non-existent.

Change to the most stable XP system or Win7 flagship version, install a version, and install another one, several versions are compatible on one machine.

It is recommended to re-order and try again.

Regarding the method of opening the higher version of proe (above) in the lower version of proe, I have summarized the following two methods:

First of all, let's talk about the premise, so far, all lower versions can only add features to open the high version, and cannot be modified.

One. Simple.

1.Directly open Creo and save it as a file in a specific format, such as save Creo as a neutral format such as stp igs.

Two. More complex.

1.Perform certain installation file operations on higher and lower versions;

2.Set up two versions of the configuration;

Three. Here is a brief introduction to these two methods.

1.Simple.

1) "Directly open the cracked potato and save it as a specific format file".

However, when the earlier version is opened, no feature steps are displayed in the model tree on the left, and the part features cannot be modified. Where*igs、*.The STEP format can be opened with other 3D software.

2.More complex.

1) "Perform certain installation file operations on higher and lower versions";

Install the directory from a higher version of the proe program: *i486 nt gcri folder.

, the duplicate file is placed in an earlier version.

Proe program installation directory: i486 nt obj folder.

2) "Set up two versions of the configuration";

For example, if the rock wheel is between and , do the following:

To open it, click on the menu "Tools", Options, and enter the right value of CRI Grafting Enable in the left box: yes.

This configuration is mainly used when opening parts that have been proed in earlier versions and needs to be modified.

To open, click on the menu "Tools", Options, and enter the right value of Topobus Enable in the left box: yes.

This configuration is mainly to activate the data transformation of the high and low versions;

After this method is set, the model tree feature steps can be displayed when the lower version proe opens the higher version proe part; But, again, cannot be modified.

Until now, there has been no way to modify the features of the Model Tree when a lower version opens a higher version of the part.

Every time we run proe, the system supports the generated track file (which is the cumulative version), which records all mouse clicks, keyboard inputs, and file retrieval until exiting or interrupting.

Since this track file records all our operations, is it useful? The answer is yes. We just need to rename and remove the suffix, and then [Function]--**Trajectory Training File] to reproduce the record of this trajectory file.

Actually, this is not what we need, we are going to use it to recover files, so the methods to recover files are:1Rename the track file and remove the suffix; 2.

Open this file in Notepad, find the last done, and delete everything after that; 3.Finally, call [Function] in Proe -- **Trajectory Training File], open this file, and save it after it is successfully generated.

Use trail wisely

During the design process, there are often times when you suddenly jump out or forget to save the disk. Although proe provides trail files, the success rate is very low! Is there really no way to retrieve files that have not been saved?

I thought about it, I researched. Finally found a way to save with TRAIL!

At the beginning, I created a new part and drew a random curve. Then I forcibly quit and of course wouldn't save. When proe is forcibly exited, a new trail file will be generated.

Depending on the config settings, the location of the trail will be different. Not much to say here!

Then I restart proe, create a new part, save it, and exit! At this point, a new trail file will be generated, which is the one with the largest number of suffixes. With a texter.

After opening it, I took a closer look and found that the real save turned out to be these few sentences:

activate

main_dlg_cur`

cp input the object to be saved [.]

tr Then I use the texter to open the trail generated when I force an exit. It was found that the following characters are the statements that produce the curve feature:

cp All elements are defined. Select an element or action from the dialog box.

The CI curve has been successfully created.

At! The %ci curve has been successfully created followed by an inserted line, paste activate

main_dlg_cur`

Then save it and suffix the modified trail file.

Change to txt, which is a text file.

Start proe, function --** Track file, select the text file just now. Start playback. Finally, a dialog box appears: whether to exit or not. Select: Yes. Then the save screen will appear.

A: What should I do if the file pops up before it finishes playing?

B: Then find the place where you need to save it, and add that sentence to it!

If you don't follow proe, you can't open the proe file, and the web page can't be opened.