turn a copy-geometry sketch into extrude/revolve

[FD_11904661]

Hi, im working on a university project and new to the whole top-down design game.

I have already created a sketch and some datum planes in my skeleton model. (I have many variables, so there is a lot of references).

Next, I have published some of the sketches as a publish-geometry, so i can use it as a sketch for my parts which will be part of my assembly.

Now Ive got the problem that i just cant get the copied sketch to work like a normal sketch for revolving or extruding parts.

I have already tried moving the copy-geometry around inside of my model tree (main assemby, subassembly, part), but the only way I could imagine using the copied sketch as a revolve/extrude sketch is by referencing every single line inside of my copied sketch and using it to make a new sketch, which just does not seem rigth.

Sadly, I also cant find any tutorials on this specific problem, because everyone uses the copy-geometry feature for already existig parts and not sketches.

Bonus question: should the publish/copy-geometries always end up inside the footers?

Yours very frustrated student,
Filip

Creo parametric 8.0.4.0

[tbraxton]

"...but the only way I could imagine using the copied sketch as a revolve/extrude sketch is by referencing every single line inside of my copied sketch and using it to make a new sketch..."

This observation and statement are accurate. Your copy geometry from the skeleton (source) to the target part(s) does not bring a sketch but curves from the sketch to the target part. You must reference these curves to create a new sketch for features in the source model but there are tools to make it easy such as project->loop. There is one way I can think of to replicate the sketch in both models and drive it from a single parent object. To do this you would use a notebook (*.lay) file to define global parameters (dimensions driving the sketch) you would then declare this notebook to all models needing the parameters to replicate a sketch to be controlled by the notebook. I am not suggesting that you necessarily do this, I would need to better understand your design intent. If you can explain the logic and desired behavior of the sketch in the skeleton to be used in a dependent model, then you will likely get some advice on methods to capture the design intent.

I would expect when you provide details on your design intent there will be a better method to manage it than what I proposed above.