Skip to main content
J
JB_103049021-Visitor
1-Visitor
May 31, 2022
Question

Reduced Creo Parametric Loading Times

  • May 31, 2022
  • 2 replies
  • 1819 views
I am using Creo Parametric - Release 6.0 (connected) Release 6.0 and Datecode6.0.3.0

We have configured Custom Config.pro and custom Config.sup files. One thing that I have noticed is that Creo has taken a direct degredation to how smoothly it ran and how quick it loaded parts and assemblies. Could there be issues with the Config.pro and the Config.sup files have an impact on how long it takes to load data.

As a note, we are integrated with Teamcenter using IPEM. If I run the integration without, the custom "/sup, and /pro" files, I don't face any issue, which leads me to believe the issue lies in the Config.pro, and config.sup files that we updated.

    2 replies

    S
    23-Emerald III
    StephenW23-Emerald III
    23-Emerald III
    May 31, 2022

    Always a possibility that your config files could cause loading issues.

    I troubleshoot config files by removing 1/2 of the config file at a time and load with just that 1/2 of the file. If the problem disappears is still there, it is likely that one of the options in that 1/2 of the file is the problem, Depending on how large your config files, you can keep cutting them in 1/2 and testing each 1/2 until you get it narrowed done to just a few. Then test each setting. Once narrowed to a few, it's usually easy to spot the most likely candidates for problems.

      R
      remy21-Topaz I
      21-Topaz I
      June 1, 2022

      Dichotomy is the recommended methodology indeed to pin down the option responsible for an issue.

        B
        23-Emerald III
        BenLoosli23-Emerald III
        23-Emerald III
        May 31, 2022

        In Creo, open the config.pro and config.sup files and see if there are any flags indicating an invalid or out-dated option.

        Steve's plan is a good one if all options appear to be valid.

        J
        JB_103049021-VisitorAuthor
        1-Visitor
        May 31, 2022

        @BenLoosli , and @StephenW, I appreciate your help, I was able to go in and take a look at those items, I even went as far as Commenting out all of the configurations that were in those files. Unfortunately, this didn't solve the problem. But it lets me know that the Config.pro, and the Config.sup are not the culprits. Which leads me to the IPEM Configuration to connect Teamcenter and Proe together. I will need to take a different route, as I thought the issue was on the Proe side of the solution. Turns out its on the Teamcenter side.

         

        Thanks again. 

         

        First time posting in the forums here, and was pleasantly surprised with the response time and speed. 

          S
          23-Emerald III
          StephenW23-Emerald III
          23-Emerald III
          May 31, 2022

          It's a good way to rule out the obvious potential issues.

          If you have and customization on the interface, you may also want to  temporarily rename creo_parametric_customization.ui file . 

          Just to rule out that it is trying to load something that may be causing the issue.

           

          In time, I may be asking you questions! Our Engineering technology group has been testing the IPEM  connection to Teamcenter. I don't think they have decided on the implementation or not!

          Terms & ConditionsAccessibility statement