Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
So I searched for this issue:
- Unable to edit sketch of the main feature
and found articles pointing to disabling the web browser - and browser tabs. This didn't work. So what is strange is that I edited this same sketch a few hours ago, There are external references to a part within an assembly - but this never stopped me from editing the base sketch. I regenerated - tried removing as many external references from the part - except the base feature which I cannot edit. I tried editing the part/base feature sketch in the context of the assembly - it doesn't work.
What happens is I selected sketch and edit - the screen sort of zooms and then nothing.
This isn't due to this article:
Even though I did turn off browser + tabs.
Using CREO parametric 10.0.4.0
I saved files - exited and re-entered CREO - still doesn't work. I edited Config.pro to remove web - still doesn't work. Any thoughts would be appreciated. I can recreate this part since it is simple - but what happens if this were a more complex part that is legacy. How do I recover?
Thanks
That issue shouldn't be in creo 10. I would suggest opening a tech support ticket with them.
If you need help from the community then can you share the file here on the community? (zip it to attach it to a reply)
Is the feature the first feature in the model tree? (no datums or coordinate systems before it)
Specifically with respect to the article, you changed the recommended config setting and then restarted creo?
So I sort of figured this out - though still do not know why this was happening.
I went back before feature and added another feature. After doing this - the "locked" feature/sketch could then edited. The dims were somewhat messed up - but this allowed to salvage a few features.
Sounds like there were missing external references because the original assembly model they were created in was missing or changed. The added feature provided something to reference, allowing it to be edited. I would have expected some warnings in a pop-up window (these could be disabled in the config) or in the message window.
So yeah - I had the top level open at the time - I even edited within the context of the assembly - still didn't work. This is the first time encountering this issue - and I always use external references to design within context of top level. I will break them later date for final release. Well there is a solution role back to Datums - create a first feature and close. Worked for me this time.
Yeah - weird no warnings - nothing.