[pdp.aero]

Hi there,

Have a quick question. What is the difference when a database appears to be kinda grayish but still a model and a pinkish when it is imported into PW?

What do these colors indicate?

I see that two protocols of STEP files are supported.

"STEP file types supported for import are protocols AP 203, configuration controlled 3D designs of 3D mechanical parts and assemblies, and AP 214, core data for automotive mechanical design processes."

So how come when I import a STEP file exported like:

STEP AP214
AUTOMOTIVE_DESIGN

I get grayish model but if I import like:

STEP AP203
CONFIG_CONTROL_DESIGN

I get pinkish model. I would appreciate if you could help me understand the difference and how to avoid incompatible formats of STEPs.

Cheers, Pay.

[dgarlisch]

Import of STEP (and all database files) are assigned the color specified in the imported file. If no color is defined, then PW defaults to pink.

See also attributes, display docs.

[pdp.aero]

Originally Posted by dgarlisch

Import of STEP (and all database files) are assigned the color specified in the imported file. If no color is defined, then PW defaults to pink.

See also attributes, display docs.

Thanks David. So they are just STEP with colors.

Do you have any idea why sometimes a step files imports with no quilts? Just curves.

More information maybe helps. A step file had a boolean operation in ESP and then the result in egads format imported in PW but there is no quilt just hidden curves. Same step file is showing to be OK in esp and OK in PW alone. But after the boolean operation and export in egads format in PW quilts fail to be there. Re-export of the same file with protocol AP203 solved the issue though. I am just trying to figure out what happened and if this kinda issues can be detected beforehand.

Interestingly, I tried freeCAD to re-export the same file but didn't solve the issue. It's a mystery

[dgarlisch]

I'd be guessing.

Attach a simple, ZIPPED STEP file that demonstrates the problem.

Or contact Pointwise support for help.

STEP files are ASCII. Zipping them makes them much smaller.

[pdp.aero]

Originally Posted by dgarlisch

I'd be guessing.

Attach a simple, ZIPPED STEP file that demonstrates the problem.

Or contact Pointwise support for help.

STEP files are ASCII. Zipping them makes them much smaller.

Funny thing is that particular step file that I cannot share is showing this problem. I have tried to re-produce the problem but I couldn't.

Yep I did vimdiff but nothing seems to be much different between the one showing that problem and the one that had been re-exported, except the header that includes the protocol.

[dgarlisch]

Originally Posted by pdp.aero

Funny thing is that particular step file that I cannot share is showing this problem. ...

Of course you can't share it.

Without a file, there is not much more I can offer.

[dgarlisch]

One quick thought just jumped in my head.

You said the model was "grayish".

Do you have hidden ents shown by any chance (View, Show Hidden)?

All hidden entities, when displayed, are "grayish".

[pdp.aero]

Originally Posted by dgarlisch

One quick thought just jumped in my head.

You said the model was "grayish".

Do you have hidden ents shown by any chance (View, Show Hidden)?

All hidden entities, when displayed, are "grayish".

I am aware of hidden entities. Those are dark grayish. This one is bright grayish. As you said the bright gray is just color of stp file.

The thing is when the stp file gets imported alone everything is fine. Quilts are there.

But when it is imported into ESP first and have an operation, and then the egads result gets imported into PW, that particular region associated with stp file completely lose their quilts. Everything gets hidden and by showing hidden, there are only curves there. The problem is the stp file but I was wondering how can I find out what exactly makes the stp file incompatible.

If I re export the same stp file from some CAD software then everything is fine either importing alone or even after having an operation in ESP and getting the egads imported. No problem at all.

If I discover this mystery I would update here or would contact the customer services to have their opinion. Thanks a lot.