2019.3 Update | Styles + ByBlock Color?

[BlackBox_]

Has something changed here?

If I have a Pipe Style set to show centerline as ByBlock, the Pipe now shows as being White in color, instead of showing as the parent Layer's color, unless individually assigned a non-ByLayer color.

When I individually assign Red (non-ByLayer) color to said Pipe (set for ByBlock), the Pipe remains White.


As comparison, if I have a Block who's Arc, Line, Polyline, etc contents are set to ByBlock, the Block appears as ByLayer unless individually assigned a non-ByLayer color.

[BlackBox_]

*Bump*

Nobody else has noticed this after installing 2019.3 Update? 

[rl_jackson]

Can you send a small snippet of it issue, I've not installed the update yet and could test in 19.2 then install 19.3 to verify. 

[rkmcswain]

@BlackBox_  - I agree, there is a difference between .2 and .3

We had to install .3 to fix the problem where C3D 2019 crashes during startup (CaseNo:15514966)

[Jeff_M]

I am seeing the same thing. Here's a snip showing the same drawing, C3D 2018.3 on the left, C3D 2019.3 on the right. The 2018 is as expected, 2019 is not.

[BlackBox_]

Thanks for the confirmation, @rkmcswain  & @Jeff_M 

---

@rl_jackson -

---

@rl_jackson wrote:

Can you send a small snippet of it issue, I've not installed the update yet and could test in 19.2 then install 19.3 to verify. 

---

The issue is that in 2019.2 and earlier versions/updates, Style elements could be set to ByBlock color (in Style Editor, Display tab) and this would behave the same as Block entities set to ByBlock - they would appear as ByLayer unless you individually assigned a non-ByLayer color.

AFAIK, that's always been the way Styles have worked (which is correct).

With 2019.3 Update installed now, that is broken - all ByBlock color assigned Style elements are showing up as White (with dark background).

So, Civil 3D team broke this basic functionality and anyone who's working on project plan submittals needs to adjust their Styles color assignments, as this changes the resultant lineweight if using CTB (which changes how your PDF/hardcopies look), as well as makes everything appear White in the drawings as well, which is less than helpful. 

Cheers

[rkmcswain]

I don't think this should surprise anyone. Most updates fix two things and break one. Perhaps the surprising part is figuring out what was broken. 

I can't pretend to know about or understand all of the code streams that are going on, but it would be nice if this all were a little more predictable. For example, the aforementioned "C3D 2019 crashes at startup" bug was fixed in the 2019.3 udpate, but the same bug exists in C3D 2020, and no patch is available. 

[BlackBox_]

In other good news....

^^This Style issue malarkey^^  _ALSO_ changes how ByBlock Linetypes are displayed, which is just fan-freaking-tastic for that project submittal today.

[wpagl452]

@BlackBox_, I have confirmed this issue and logged it with the development team. Thank you for bringing it to our attention.

[BlackBox_]

---

@wpagl452 wrote:

@BlackBox_, I have confirmed this issue and logged it with the development team. Thank you for bringing it to our attention.

---

Thanks, @wpagl452  

I know that the Civil 3D team doesn't really want to be dealing with 2019 right now, but....

Cheers

[Jeff_M]

@BlackBox_ , I used a special Hotfix for this issue. I Uninstalled Update 3....C3D2019.2 works just fine for fixing this issue. However, of course it brings back all those other things that Update 3 fixed.... I'm not using 2019, so not sure if this helps you.

Or, what about doing the plotting from C3D 2018? It should still display those same drawings correctly.

[BlackBox_]

Thanks, @Jeff_M 

As you've said, uninstalling 2019.3 fixes this particular issue, but leaves us with what was broken, which is a lose-lose situation for users.

Thankfully, the Civil 3D team has since logged this as a defect and we anxiously look forward to their excellent work to rectify this unintentional lil' oopsie. 

We no longer have 2018 products installed, so that's not an option at this time.

Cheers

[rkmcswain]

@BlackBox_ wrote:

As you've said, uninstalling 2019.3 fixes this particular issue, but leaves us with what was broken, which is a lose-lose situation for users.

I have also notified @bullera as he was working on our 2019.2 issue (crashing at startup). Hopefully a hotfix will be released so we don't have to wait 3+ months on Update 4.