Issue with 'views' disappearing

[ptc-5314269]

I have just started at a new company and they has just started to use Creo 1.0, so no-one has much experience with Creo.

The issue I am having it that when I am doing an assembly, the standard 'views' will randomly disappear without me actually doing anything. So I cannot snap to a view on modelling (top, front, side etc.), I cannot find a way to get them back.

can anyone help?

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.

[James62]

Can you tell for sure these model views were defined in that model before?

In case the default views are gone I use the following mapkey:

mapkey -sdv @MAPKEY_LABELSet 6 default views;\

mapkey(continued) ~ Select `main_dlg_cur` \

mapkey(continued) `igToolbar_AncestorIGT_IGT_GRP_inh396938342.proe_win:casc340798662`;\

mapkey(continued) ~ Close `main_dlg_cur` \

mapkey(continued) `igToolbar_AncestorIGT_IGT_GRP_inh396938342.proe_win:casc340798662`;\

mapkey(continued) ~ Command `ProCmdViewOrient` ;@MANUAL_PAUSESelect XY plane.;\

mapkey(continued) @MANUAL_PAUSESelect XZ plane.;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `T`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `TO`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `TOP`;\

mapkey(continued) ~ Update `orient` `namedviewPH.NameVw_IP` `TOP`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_Save`;Yes;\

mapkey(continued) ~ Open `orient` `SetupOptions`;~ Close `orient` `SetupOptions`;\

mapkey(continued) ~ Select `orient` `SetupOptions` 1 `dynorient`;\

mapkey(continued) ~ Update `orient` `spinPH.YSpinBox` 180.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.YSpinBox` 180.000000;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `B`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BO`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BOT`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BOTT`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BOTTO`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BOTTOM`;\

mapkey(continued) ~ Update `orient` `namedviewPH.NameVw_IP` `BOTTOM`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_Save`;Yes;\

mapkey(continued) ~ Update `orient` `spinPH.YSpinBox` 0.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.YSpinBox` 0.000000;\

mapkey(continued) ~ Update `orient` `spinPH.XSpinBox` -90.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.XSpinBox` -90.000000;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `F`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `FR`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `FRO`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `FRON`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `FRONT`;\

mapkey(continued) ~ Update `orient` `namedviewPH.NameVw_IP` `FRONT`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_Save`;Yes;\

mapkey(continued) ~ Update `orient` `spinPH.XSpinBox` 90.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.XSpinBox` 90.000000;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `B`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BA`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BAC`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `BACK`;\

mapkey(continued) ~ Update `orient` `namedviewPH.NameVw_IP` `BACK`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_Save`;Yes;\

mapkey(continued) ~ Update `orient` `spinPH.XSpinBox` 0.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.XSpinBox` 0.000000;\

mapkey(continued) ~ Update `orient` `spinPH.YSpinBox` 90.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.YSpinBox` 90.000000;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `L`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `LE`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `LEF`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `LEFT`;\

mapkey(continued) ~ Update `orient` `namedviewPH.NameVw_IP` `LEFT`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_Save`;Yes;\

mapkey(continued) ~ Update `orient` `spinPH.YSpinBox` -90.000000;\

mapkey(continued) ~ Activate `orient` `spinPH.YSpinBox` -90.000000;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `R`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `RI`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `RIG`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `RIGH`;\

mapkey(continued) ~ Input `orient` `namedviewPH.NameVw_IP` `RIGHT`;\

mapkey(continued) ~ Update `orient` `namedviewPH.NameVw_IP` `RIGHT`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_Save`;Yes;\

mapkey(continued) ~ Select `orient` `namedviewPH.NameVw_List` 1 `TOP`;\

mapkey(continued) ~ Activate `orient` `namedviewPH.NameVw_PB_SetCur`;\

mapkey(continued) ~ Activate `orient` `OkPB`;

The mapkey is made in Creo 2.0 as far as I remember, but I guess it should work in Creo 1.0 as well.

[MartinHanak]

Jakub,

I tested your mapkey. It works in ProE WF5. In Creo Parametric 2.0 it does not create views. I think it's easy to recreate it in CR2.

Martin Hanak

[James62]

Ok, Martin.

It's propably a Creo 1.0 mapkey then.

[ptc-5314269]

I have tried your solution. I was able to recreate the views. But again randomly they disappear!

The standard views always start in the assemblies / parts that I start but then they disappear. I know how to recreate the views, but I was hoping there would be a simple option I could click which would reset the views

[MartinHanak]

Colin,

if you create new part using PTC template, you will see that it does not contain default views. This is because in PTC template, views are not defined. If you create views, save the part, remove it from session and open it again, then it must contain views.

If you create another part using PTC template, then you have to repeat the same process. To prevent such behaviour, you have to prepare your own templates containing views and use these templates during model creation.

Martin Hanak

[TomD.inPDX]

I have used Creo 1.0 and did not have this issue. I am wondering if this is more a case where you are not using the same template models for different models. I know that if you start a model with the "empty" option, it does not come with views. Several other PTC template do. Maybe a little more background would help.

And yes, if you create a view orientation and save it, it will stay with that part or assembly. It should never disappear unless you specifically delete it. If you save the part and open it in a new session, it will still be there. ..at least, if should be.

There are occasions where views loose their references. In this case, the view will remain, but you get an error message in the message prompt. Again, this should not affect saved views.

There is no quick way to make a lot of views. You cannot import them and you cannot save a series of views to use in another file. I have made start parts and start assemblies that have all my predefined views already saved in them. This is normal operating procedure for Creo. You can make these template parts, but in essence, I open a part and save-as for the new part.

I will not say that you have not run into a bug. It may well be. Even if it is, there will be little help from PTC since support for Creo 1.0 has lapsed on Oct 5th, 2012.

One thing about Creo 1.0 is that it was an introduction to the new platform. Creo 2.0 is the unofficial bug fix for Creo 1.0. I don't know anyone who would, if they had the choice, to stay with Creo 1.0. It may well be worthwhile to talk with the CAD admin people to understand why they have not upgraded.

So, -if- you are on this road and have no choice for the long term, it would be in your interest to try to duplicate the issue to see if you can avoid it. Save often; recall a previous version of the file and see if the views re-appear. I think others here would be willing to review a file and see if they see the same as you. Again, this is not a bug I have experienced, and I started Creo 1.0 at datecode F000.

[TomD.inPDX]

...and welcome to the forum!