Skip to main content
MartinHanak24-Ruby III
24-Ruby III
February 15, 2024
Question

When saving an assembly, Creo Parametric 10.0 unexpectedly modifies component model files that were

Any Creo 10.0.x.0 release behaves as said in Subject. I will upload test data created in Creo 7.0.11.0 and video showing the "problem".

Note: I already opened Case at PTC Support.

    19 replies

    MartinHanak24-Ruby IIIAuthor
    24-Ruby III
    February 15, 2024

    Full Subject text ... When saving an assembly, Creo Parametric 10.0 unexpectedly modifies component model files that were created in the past.

    Translate
    MartinHanak24-Ruby IIIAuthor
    24-Ruby III
    February 15, 2024

    Test data.

    Translate
    MartinHanak24-Ruby IIIAuthor
    24-Ruby III
    February 15, 2024

    Video attached.

    Translate
      aputman13-Aquamarine
      13-Aquamarine
      February 15, 2024

      I hate to be the cynic but when the software went to a subscription licensing, I'm willing to bet they made the decision that all part models need to be current so that you are locked out of ALL your data when the subscription expires.  It's the only way to force people to completely do away with their persistent license.  I don't see your case being resolved. 

      Translate
      aputman13-Aquamarine
      13-Aquamarine
      February 15, 2024

      Thank you for noticing and opening the case with PTC.  I hope you update this post with the results of your case.  I'm curious to see what is their response. 

      Translate
      MartinHanak24-Ruby IIIAuthor
      24-Ruby III
      February 16, 2024

      PTC immediately opened SPR.

      https://support.ptc.com/appserver/cs/view/spr.jsp?n=15163415

      Translate
      MartinHanak24-Ruby IIIAuthor
      24-Ruby III
      February 28, 2024

      Hello to all,

       

      Here is the R&D Feedback ... I just stare in surprise

      ==================================

      The file size change is expected and is very small which has only metadata info added that is required to support Creo 10, there is no specific model/design change that would impact customer negatively.

      Infact, customers may not like to iterate their files for such change as they could have released files. It’s a one time change that we see.

      ======================================

       

      Translate
      BenLoosli23-Emerald III
      23-Emerald III
      February 28, 2024

      Even if the file was not changed significantly, the header internally should still be updated to indicate that the file was saved in Creo 10.

      I haven't tried it, but can the modified file with the header still showing Creo 7 be opened in Creo 7? If so, that may be why PTC is not changing the header. But then what does Creo 7 do with the extra line of metadata that Creo 10 added?

      Translate
      MartinHanak24-Ruby IIIAuthor
      24-Ruby III
      March 6, 2024

      Yesterday I came across an article https://www.ptc.com/en/support/article/CS409743.

      Today I asked PTC Support what is planned in Creo 10.0.5.0.

      To be continued...

      Translate
        MartinHanak24-Ruby IIIAuthor
        24-Ruby III
        March 12, 2024

        Today my Case was closed successfully.

        Anyone who wants to can follow SPR 15124259  https://support.ptc.com/appserver/cs/view/spr.jsp?n=15124259 

        The solution to the problem is planned in Creo 10.0.5.0, Creo 11.0.1.0 and Creo 12.0.0.0.

        These releases will stop modifying old files using the hidden config.pro option prevent_silent_sync yes (default value is no).

        10.0.5.0	Jun 2024
11.0.1.0	Q3 2024
12.0.0.0	Apr 2025

         

        Translate
          Terms & ConditionsAccessibility statement