Split line functionality and face colours

[KQD]

We use Creo and SolidWorks (both latest versions) alongside other systems. A huge frustration for us is when marking up files for data release or visualisation for design reviews. Many times we need to decorate a part to show colour/finish/surface finish etc and our workflow in SolidWorks is quite simple.

1. Create a new configuration (to isoltae the markup) and split the relevant faces with the split line tool - split lines are generally taken from projected sketches or surface intersections (so we can also import specific decorations onto parts for toys etc)

3. Apply topology  level colours to the split entities (SolidWorks allows you to "paint" a part by topological levels  - assembly part level, part level, imported body, body, face etc).

4. Export to Keyshot and render.

5. Export to parasolid or STEP and the split faces and face colours come through.

Creo has no equivalent functionality like this (in the base packages). So we are often left with the daft scenario of modelling using Freestyle and Style, then bringing these parts into SolidWorks for data preparation and pre viz work.

Aside from decorative uses like this face splitting has modelling uses in creating surface features, or simply for marking areas in the data where you might apply different surface textures to the part.

[Pettersson]

There's a workaround for this, though it's not very pretty. Here's how you do it: 1. Copy and paste the surface you want to split. 2. Trim the surface the way you want it. 3. Apply a warp to the surface. Don't make any actual changes to it; just apply a warp feature and hit green checkbox. 4. Solidify it. It will now show up as a separate surface that you can paint in a separate color. Step 3 is the key. The Warp command changes the definition of the surface so that it's no longer identical with the original and won't merge with it as solidification. Still, it's a four feature operation for each split, and it's such a simple thing that really should be possible. I'd definitely want a solution to this, but perhaps the above workaround might help you.