cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

Importing Parasolid (x_t) causes Creo 5 to Crash! Help!

Go to solution
nebraska-engr
8-Gravel
8-Gravel
‎May 31, 2019 12:50 PM
‎May 31, 2019 12:50 PM

Importing Parasolid (x_t) causes Creo 5 to Crash! Help!

Hello,

 

I am running Creo 5.0.4.0 on Windows 10.

 

I am trying to open a standard parasolid file and it causes Creo to freeze while loading (spinning wheel of death). Shortly after, Creo stops responding and crashes.

 

I have tried this on another coworkers computer with the same setup as me, and it crashes for him too. Has anyone seen this before? I read online that you should be able to open x_t filetypes, but this seems to not be the case for me. Please help!

Labels:
0 Kudos
Notify Moderator
1 ACCEPTED SOLUTION

Accepted Solutions
StephenW
23-Emerald II
23-Emerald II
(To:nebraska-engr)
‎May 31, 2019 01:51 PM
‎May 31, 2019 01:51 PM

You may want to try NOT loading any configuration files. Rename any config.pro and/or config.sup.

This will bring you back closer to an out of the box scenario.

If you can attach the file here, I would be happy to try. I'm on Creo 4 (not 5).

It's possible the file is a bad export. If you have another cad software, try importing.

I have created exports that have been too complex or large. I have also received them. Sometimes you have to work with the file provider to get the right recipe and strike a good balance

View solution in original post

Notify Moderator
1 REPLY 1
StephenW
23-Emerald II
23-Emerald II
(To:nebraska-engr)
‎May 31, 2019 01:51 PM
‎May 31, 2019 01:51 PM

You may want to try NOT loading any configuration files. Rename any config.pro and/or config.sup.

This will bring you back closer to an out of the box scenario.

If you can attach the file here, I would be happy to try. I'm on Creo 4 (not 5).

It's possible the file is a bad export. If you have another cad software, try importing.

I have created exports that have been too complex or large. I have also received them. Sometimes you have to work with the file provider to get the right recipe and strike a good balance

Notify Moderator
Top Tags