Cannot print custom display styles

i have created some custom display styles which i apply to saved views then reference into sheets. 

They will not print! See image below. displays as intended in the sheet. Print window just ignores the entire reference. 

Parents
  • All,

    I am experiencing similar problems.

    Duncan, how did your SR go? Has anything been further actioned?

    I created a display rule so that some of my elements are given a specific display style.

    I  tested with a customised filled hidden lines display style where visible edges are set to black (color 0) ....no background colour is set.

    The print output is okay when set to rasterized... which for me is not really an option.

    However when I set it to un-rasterized, all of the visible edges disappear. It is almost like the lines are printing white on white background.

    I have also tested it with a customised wireframe display style where all elements are set to black (color 0) ....no background colour is set.

    On screen this looks good.

    However, when I go to print the lines are not visible.

    If is set it to print Monochrome then it appears kind of okay.. (but that is missing the point for me)

    On screen, color 0 is normally white (256,256,256) and on a black background. It has always printed black.

    Can someone from Bentley do a simple test and confirm if this is a bug?

    None of these are dynamic views and not 3d.... just plain old 2d dgn files. I am testing this on AECOsim CEU4 (equiv Microstation U11)

     

    AECOsim SS6 + CONNECT U4, Windows 7 Pro, 64Bit, Intel Xeon E3-1275 v5 @ 3.6GHz, 32GB RAM, NVIDIA Quadro P1000

  • This is quite a big dea.

    We hear from Bentley that it is not good practice to mix customised pen tables with Aecosim DVs however if these display styles don't work well, then what are our options?... really struggling here.

    Is nobody from Bentley able to comment?...any workarounds (other than printing raster)?

     

    AECOsim SS6 + CONNECT U4, Windows 7 Pro, 64Bit, Intel Xeon E3-1275 v5 @ 3.6GHz, 32GB RAM, NVIDIA Quadro P1000

  • Who told you not to use custom pen tables with aecosim DV' because that is bullsh*t. They are essential to a DV/CVE workflow, pen tables are the only way to resymbolise cached elements 

  • Yeah we have been pen table along with DVs to date... but given our transition to CE we wanted to leverage the (theoretical) potential of the display rules as much as possible given the significant flexibility in re-symbolising based on building component properties and drawing seed.

    For example it would have been great to do coloured wall-scope plans that coloured walls based on there type code.

    Actually, I don't think that recommentation was strictly Bentley's (sorry Bentley), it was the following wiki, which I encountered a while ago (took a while to find it again):

    https://communities.bentley.com/products/microstation/microstation_printing/w/wiki/14344/printing-dynamic-views-what-works-what-does-not

    In general, one should choose to use Dynamic Views OR element-based pen tables -- not both.

    I recall we had some funny issues in the past with how our current pen table, which is heavily-customised (mostly for our MS users) interacted with our DVs (I cannot recall what...it will come to me)... I planned to strip this back to focus primarily on 2d drafting items, but given the issues with Display styles maybe not worth the effort.

     

    AECOsim SS6 + CONNECT U4, Windows 7 Pro, 64Bit, Intel Xeon E3-1275 v5 @ 3.6GHz, 32GB RAM, NVIDIA Quadro P1000

  • The real downside to DV/CVE workflow is the inability to override cache'd elements, whether colour, linestyle or otherwise, meaning all symbolization has to be done at DV level. This means you have to create multiple different definitions of the same views for different outputs. this clogs the models, slows down file switching,regeneration and printing. 

    I have found that display styles work easiest with ABD when you just skip the dv out. ie reference a 3d model directly into a 2d drawing without cutting or cache-ing. elements resymbolise instantly as you require, though you then lose things like 2d drawing symbols. 

    The most successful output I have had comes from a combination of simple 2D CVE display, with some model elements referenced directly on top(spaces usually), controlled via display style/display rule via reference presentation display

Reply
  • The real downside to DV/CVE workflow is the inability to override cache'd elements, whether colour, linestyle or otherwise, meaning all symbolization has to be done at DV level. This means you have to create multiple different definitions of the same views for different outputs. this clogs the models, slows down file switching,regeneration and printing. 

    I have found that display styles work easiest with ABD when you just skip the dv out. ie reference a 3d model directly into a 2d drawing without cutting or cache-ing. elements resymbolise instantly as you require, though you then lose things like 2d drawing symbols. 

    The most successful output I have had comes from a combination of simple 2D CVE display, with some model elements referenced directly on top(spaces usually), controlled via display style/display rule via reference presentation display

Children
No Data