Skip to main content
F
fgosti1-Visitor
1-Visitor
May 25, 2016
Question

Problem saving .pvz file (Creo 2.0)

  • May 25, 2016
  • 1 reply
  • 2832 views

Hello,

I have a problem in saving a .pvz file of an assembly with Creo 2.0 M080. When I click "Save" it doesn't save the file.

In a similar pc, with the same versione of Creo and the same assembly, the file .pvz is saved regularly.

Can you tell me why? What can I check?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

B
BillRyan16-Pearl
16-Pearl
May 26, 2016

In Creo Parametric, go to File -> Options -> Data Exchange.  If you don't see a recipe file path for Product View, then it is using the default recipe file from Startup Directory.  You may want to define the recipe file for Creo and make sure it is being used in the Creo Session.  I have multiple recipe files and use my config.pro to point at the desired one.

Also, I wouldn't touch Croe Parametric Builds M070-M110 as they had all kinds of problems for us.  The newer builds have a lot of upgrades in regards to PVZ.

F
fgosti1-VisitorAuthor
1-Visitor
May 27, 2016

I check that in File -> Options -> Data Exchange -> "Recipe file .pvz" there isn't a specified .rcp file (so it use the default file).


Can you tell me how to define a recipe file or where I can find a correct recipe file?


PS: I check that Creo save the .pvs file but not the .pvz




B
BillRyan16-Pearl
16-Pearl
May 27, 2016

If both computers are using the default recipe file that comes with the Creo M080 Install, then that is not your issue.  I don't have any other ideas as to the issue, besides possibly checking differences between the graphics driver or config.pro file. 

Terms & ConditionsCookie settingsAccessibility statement