The color problem you mentioned only occurs if you put the spring directly into the assembly.
The assembly uses color 16 for coloring the plastic parts, and there color 24 will properly be used to colorize their edges.
However, if you generate your spring DIRECTLY inside that assembly file, using color 494 for the spring quads/triangles,
and color 24 for the spring edges, then of course it will get the wrong edge color.
Your tool in this regards is somewhat wrongly using our files structure!:
The spring should not be generated directly inside the assembly file.
IF you would instead generate it in a way in which it REPLACES the spring part completely,
then your generated spring can use colors 16 and 24 as usual, and would be referenced from
the parent assembly as color 494.
Then everything would appear with correct colors.
May I suggest to modify the generator of your tool this way?
The "trick" of hardcoding the edge color using an RGB value is counterproductive IMHO.
The assembly uses color 16 for coloring the plastic parts, and there color 24 will properly be used to colorize their edges.
However, if you generate your spring DIRECTLY inside that assembly file, using color 494 for the spring quads/triangles,
and color 24 for the spring edges, then of course it will get the wrong edge color.
Your tool in this regards is somewhat wrongly using our files structure!:
The spring should not be generated directly inside the assembly file.
IF you would instead generate it in a way in which it REPLACES the spring part completely,
then your generated spring can use colors 16 and 24 as usual, and would be referenced from
the parent assembly as color 494.
Then everything would appear with correct colors.
May I suggest to modify the generator of your tool this way?
The "trick" of hardcoding the edge color using an RGB value is counterproductive IMHO.