16-Pearl

Solved

Family Table models vs Model Check

Forum|Forum|3 months ago
December 12, 2025
3 replies
330 views

Hi there,

I have a frustrating problem with Model Check.

We use screws in our assemblies. Those screw's length is defined by a family table.

Unfortunately, ModelCheck always checks those screws in the assembly and causes a "is modified".

Even if I check the assembly with the option "top level".

I already added "IF ( MODELNAME EQ ISO* ) NOCHECK" to condition.mcc
But no luck. Creo keeps modifying those models nevertheless.

If I open the screw itself and run model check, I get a "nocheck", which I expect.

BUT Creo list the model as "modified" anyway.

General

Best answer by Mat

a little Update:

That "behaviour" also shows up with other random instances of other family table driven models (e.g. flatten sheetmetal).

BTW, I forgot to mention, that I am running Creo 10.

I tried several things:

emptying configurations (removing tests from modelcheck)
I ended up with a completely empty check.mch and start.mcs file.
That config_init.mc only contained "MC_ENABLE YNA Y" to be able to run modelcheck at all. ModelCheck still modifies those instances.
I installed Creo 12 and tested Modelcheck again.
MC also modifies those instances.
I also started Creo without any custom config.pro options ( besides modelcheck_dir to point to my testing mc-files).
Still no luck.
In an act of desperation, I "downgraded" to Creo 9.
And there You go. ModelCheck runs as intended!

At this time, since all of my configuration file changing attempts were unsuccessful but only switching to Creo 9 worked, I consider this as a bug in Creo Parametric. If it is a bug (please comment, If You can see the same behaviour with Your Creo installation in a Windchill environment), Creo 10 and above are affected.

M

MartinHanak

24-Ruby III

Hi,

just a basic question: Are all FT instances successfully verified and then the generic model saved?

M

Mat

Author

16-Pearl

Yes, they look all verified:

M

Martin_Hill

10-Marble

Does your Model Check change the assembly layer settings in any way?

If so, this can propagate down to the parts in the assembly causing them to be modified.

M

Mat

Author

16-Pearl

the layers of the assembly or the parts are not changed.

even more strange, if I change the condition.mcc file and add "IF ( MODELNAME EQ asm0001.asm ) NOCHECK", MC still runs its checks on the model.

I can only convince MC to ignore that model (or run other checks for testing), if I set the condition to "MODELNAME EQ asm0001*"

M

Martin_Hill

10-Marble

There is a difference between MODELNAME (PTC_COMMON_NAME) and FILENAME.

Are you using Windchill?

M

Mat

AuthorAnswer

16-Pearl

a little Update:

That "behaviour" also shows up with other random instances of other family table driven models (e.g. flatten sheetmetal).

BTW, I forgot to mention, that I am running Creo 10.

I tried several things:

emptying configurations (removing tests from modelcheck)
I ended up with a completely empty check.mch and start.mcs file.
That config_init.mc only contained "MC_ENABLE YNA Y" to be able to run modelcheck at all. ModelCheck still modifies those instances.
I installed Creo 12 and tested Modelcheck again.
MC also modifies those instances.
I also started Creo without any custom config.pro options ( besides modelcheck_dir to point to my testing mc-files).
Still no luck.
In an act of desperation, I "downgraded" to Creo 9.
And there You go. ModelCheck runs as intended!

At this time, since all of my configuration file changing attempts were unsuccessful but only switching to Creo 9 worked, I consider this as a bug in Creo Parametric. If it is a bug (please comment, If You can see the same behaviour with Your Creo installation in a Windchill environment), Creo 10 and above are affected.