Colourising Non-compliant Walls with Non-standard Vectors

What am l missing here? I am getting closer, thanks to all of your inputs and mine.

image

use levels @L2 so you dont have to use flatten and list create nodes

1 Like

You’re missing this. You are plugging a function (Color.red), not a color…

I have the list of affected elements, yet the Element.OverrideColorInView node is not accepting the input.

Can anyone expand on why this is the case?

image

I don’t know if you’re ignoring my posts …

and mine

And mine

I am not ignoring any, but l do not profess to be as good as you guys, but l am trying.

image

Try and read what a RGB is on Google

Next look at what color.red gives you

Don’t take it personally…

You would have figured this out yourself if you read my initial post.
Try viewing every node preview and every error you get instead of just rushing to us.

1 Like

colour is done, but it is not that it appears not be be accepting the list as an element input

From the latest image, you’re feeding the Element.OverrideColorInView a list with true and false items. Use the configuration you had before, this post Colourising Non-compliant Walls with Non-standard Vectors

You may need to set the node to look at the second level of the list, using the @L2 setting:

Untitled

1 Like

But that is what I’m telling you it is not… You’re passing the “red” component of a RGB color… That is the integer 255 (which you would know if you read about RGB colors). That is not in itself a color…

The output as illustrated by @mellouze (twice now) from the “Color Red” node from Clockwork (or codeblock) gives you a color.

2 Likes

It is colouring the wrong element. The filter bool mask l need to sort out now.

Many thanks ALL.

For the record we’re not trying to be rude or anything of the sorts, but we’re trying to give you a piece of the puzzle and a hint and try to let you discover the solution yourself, that way you’ll learn a lot more than us giving a complete graph that works and you do not understand. For at some point it will no longer work and you do not know how to fix it if you do not know and understand the logic behind.
Don’t worry we all started somewhere and you are embarking on a long and interesting journey with Dynamo.

That said please do be polite and ask for a clarification if there is something you do not understand etc. the people on the forum are doing it voluntarily and are solely trying to help you learn.

And also, if you do not get an answer on your post please do not just copy/paste the same question into other posts that is not how this forum works.

Just my two cents.

2 Likes

I know that the highlighted is the point at which the wrong wall or walls are being colour because it is applying a new Index value, rather than retain the Index of the affected elements.

Now it is either something to do with Map or most likely something obvious :face_with_raised_eyebrow:

Have a look below and see if it makes sense to you… I assume you’re having 4 walls and you want the one with “null” rotation… At least that’s what I’m reading from your screenshot.

Jonathan,

Other than l am not very experienced and usually over think and complicate matters, with something like this. Too many nodes near the end were not do the correct thing.

You have brought the list of elements into the boolmask, then queried them against items which have or have not complied with the criteria, then colourised accordingly.

Many thanks for your patience, input, guidance and kick up the ass!

Many thanks to all.

1 Like