Data viz and Wall textures

[BartHays]

Hello all,

 

I am using Data Visualizations to clarify who is responsible for different scopes of work on a project. 

Everything is working well, except for Walls that have textures by face object. 

Form some reason these textures are not getting overwritten by the Visualization manager.

Below, the blue walls are textured by Component and the Vis overrides the texture as expected.
The wall with the Bee on it is a wall textured by Object with the LEFT parameter having texture. I believe the VIz manager should overwrite this texture too (It should be all orange like the exposed bit on the bottom). 

I can convert the Bee wall to being textured by component and/or add a thin extrude for the texture, so I have a workaround, but I think this is a bug, right?

 

Bart
 

 

 

[E|FA]

21 minutes ago, BartHays said:

I think this is a bug, right?

Yes, a bee is a bug.

 

Sorry, I couldn't help myself.  And unfortunately I don't have a useful response to your question.

[michaelk]

Yes you can.  You just need to assign a texture to the Data Vis.

 

I'll attach an example.

237111356_DVTest.vwx

[BartHays]

Hi @michaelk

 

I think my issue is more complicated. 

I can override simple textures but look at the two elements in this file.

One shape has a decal and it seems to break the data vis ( object disappears) - If I delete the decal, it works fine.

The wall object works fine if textures re defined by Component but if texture are defined by Object, they dataviz doesn't work correctly.

 

After creating this test file, I created an extra Rendeworks Texture, with just a color shader, the same color as my Dataviz solid fill color, and applied it to the Dataviz. It did fix the issue with the decal, but not with the wall texture.

 

Regardless, I shouldn't have to create new Renderworks texture for every override in my Dataviz.

(Update: if I just create a Texture with the color shader as Object Attribute, I can use just one texture and assign it to all of my Data viz items)

 

Bart

1695338170_testDV2.vwx

Edited May 19, 2023 by BartHays

[michaelk]

Try this:

1695338170_testDV3.vwx

[BartHays]

Yep, thank you,

That is basically my workaround now.

 

Still, can we agree this is a bug? I'm not sure how to go about submitting it. 

 

Bart

[michaelk]

Submitted!  VB-195868.  We'll find out soon enough if it's a bug or working as designed.

 

But you ask a good question about submitting bugs.

 

I think this still works:  

 

https://www.vectorworks.net/support/bugsubmit

 

But I think bugs also get vacuumed up in the Troubleshooting forum.

 

https://forum.vectorworks.net/index.php?/forum/55-troubleshooting/