I am developing demolition drawings for several relay protection cabinets for the power generation company I work at. This involves a print with the section to be demo'd, clouded and hatched. The cloud and hatch should be green, specifically color index [130]. Everything else is monochrome.
I am aware that mapping that specific design index color to RGB 0,130,0 achieves this exact outcome. However at points, there are designs that contain other elements outside of the cloud and hatch that use this same color. I am also aware that using level overrides can mitigate the other elements from printing in this color while the clouds still do.
However, I am almost certain this is a bug of some sort as I am unclear as to why the pen table would not be able to output the correct color for a specific element based on selection criteria and output actions defined in the pen table.
The follow pen table is used:
I have mapped pen colors form driver configuration file
Element Selection Criteria: Level: CLOUDS
Element Output Actions: Color: Index [130]
Print is set to: PDF, True Color
The print preview shows everything in black and white...
Is there another setting within the design file that is overriding the pen table? The aforementioned workarounds output the correct color while everything else is monochrome as needed as long as there are no other elements that color in the design file. Why does this not work??
What happens if you set the output action color to RGB and force 0,130,0 instead of using the index color? When you say everything else is monochrome, how are you setting them to monochrome?
Are the other elements you don't want printing green that are index color 130, are they on the CLOUDS level?
Answer Verified By: Christopher Christian
Setting the element output to RGB instead of index solved the problem, for whatever reason when I use the index number it does not change the color output for that level.
The rest of the drawing is black/white(monochrome) via the pen color mapping in the global actions settings within the pen table.
The original work around I changed the design index in this same pen color mapping for index 130 to RGB 0,130,0, in this instance if any other element is the same index it will print green. Which isnt the case most of the time. Nor is it an issue of its own, just would rather use the pen table to modify the output of certain elements instead.
Still unsure why the Index number does not work though...
Thanks for the input!
also, you may have the Element sections in the wrong order. MicroStation processes sections in top down order, and when it finds a match it stops processing other sections.
So this section ordering:
works for me to turn elements on the CLOUDS level to green, but if I put the AllMonochrome section above the Green_Clouds one then everything comes out black because the All Monochrome one matches all elements and no other sections process.
Actually, just restarted computer and microstation, pen table works as expected even with the index number instead of RGB. I racked my brain on this for a few hours going crazy trying to figure out what I was doing wrong. Still not sure what was happening. Didnt have monochrome turned on etc. Just rebooted and reloaded file and voila. Go figure. Thanks for the help anyways!
yep, seen similar failure to do things after a few hours working, did restart and reload msnt and all works as before... mstn has a lot going on and she gets forgetful from time to time, must be early onset dementia after she is getting quite old...being a child from the 80's
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me