Animatable Pixel Matrix Display

After watching Next Gen, I was inspired by the LCD-like displays of the robot faces. I had an idea about using dynamic paint to drive the material. The basic idea is to render out the dynamic paint into an image sequence. Those images are then fed into the material where it is pixelated.

And blah. blah… Just go check out the included .blend file and have a play with it. :slight_smile:

LCD.blend (3.4 MB)



EDIT

I’ve made a bunch of updates to the material to make it more intuitive. I’ve also included a part of my rigged robot so you can play around with the dynamic paint aspect of the setup.

29 Likes

very cool idea !

looking forward to seeing the nodes you came up with…
really interesting stuff.

Jarek D (DJ)

Great idea!

I haven’t forgotten about this project. After my first post I decided I needed a robot to go along with the display. I got a bit carried away.

So with that out of my system, I’ll finally get back to improving the matrix material. :slight_smile:

4 Likes

Very cool! also really liked that effect in Next Gen,
Could you share the node setup?

Of course, I plan to share the setup once I work out all the kinks. I should have more time to finish it up tonight.

1 Like

I’ve finished the material (for the most part). See the original post.

Amazing! thanks for sharing :wink:

How the hell did you work this out?!
the math nodes drive me crazy, it is so difficult!

could you expand and explain your workflow towards this node setup?

It’s not so bad once you weed out all the extra fluff I included. I’m about to go to bed, but I’ll break down the nodes for you the next time I’m at my computer with some free time.

Until then, I’ll give you a hint if you want to keep tinkering with it. When manipulating vector space, adding/subtracting is like translating and multiplying/dividing is like scaling. With that in mind, mute the chains of math nodes then unmute in order of operation to get a sense for each step.

Ok, here’s a breakdown, ebi. Hopefully you like reading. :smiley:

First let’s break down the Quantize node group. This is responsible for pixelating the texture it’s fed into with some vector math. To do this, we need to work on the X and Y (UV) coordinates separately.

Quantize

The nodes in blue aren’t essential to the function, but let’s start there. Our goal with this node group is to pixelate an image, and allow you to to scale the pixels up and down. When scaling in UV space, the transform happens from the origin (0,0) which is at the bottom left corner. That works fine, but I wanted the pixelation to line up to the center of the image.

See in the .gif how the pixels are perfectly centered as the pixels are scaled? The blue nodes are responsible for this. When modeling, you can move the pivot to where you want to scale from. In UV space, you can’t move the pivot to the center of the texture, but you CAN move the center of the texture to the pivot.

That said, here’s what’s happening, starting with the blue node in the top left:

  1. Get half of the pixel size.
  2. Add that value to 0.5.
    • UV space is 0 - 1, so this gives us the center of the U/V vector PLUS half of one pixel (so the “pivot” is at the corner of the pixel, and not the center of it.)
  3. Now get the vector and subtract (translate negatively) by this center value.
    • At this point, the center of the texture has moved to the bottom left corner. Now we can scale from the center.
  4. In the first gray node, take the vector and divide by (scale down to) the pixel size.
    • The texture now tiles across the mesh. If the vector length is 1 and the pixel size is say 0.05, then 1 / 0.05 = 20 tiles (pixels) across. In other words, our vector space was scaled from 0.0 - 1.0 to 0.0 - 20.0.
  5. “Round” quantizes the vector space. 0.0 - 20.0 becomes 0 - 20.
  6. Multiply the vector by the pixel size to scale it from 0 - 20 back down to 0 - 1
  7. Lastly, we need to undo step 3, by adding (translate positively) back to the original UV space.

Now for the matrix node group.

It’s as simple as the quantize group when you take out the blue and red nodes. Just like before, the blue nodes have to do with changing the scale “pivot point”. The red nodes are simply there to make pixel gap and pixel squareness sliders more user friendly. That leaves you with 5 gray nodes doing all the work.

I’ll skip the blue and red this time:

  1. Divide the vector by the pixel size.
  2. Feed this into a modulo, which in most basic terms, repeats the texture
    • This group is being fed into a procedural gradient texture, which doesn’t repeat like an image texture does.
  3. Subtract (translate) each pixel by 0.5 to re-center them. This node should have been blue.
  4. Multiply (scale) each pixel individually by the gap size
  5. Feed this into a power node with the exponent controlled by the squareness input.
    • The higher the exponent, the sharper, or more “square” a curve looks.
  6. This node group is plugged into the gradient texture.
    • The gradient is plugged into a “greater than” node to make it solid black and white. This is your mix factor for the lit and unlit pixel materials.
    • The gradient texture can also be plugged (without the greater than node) into a bump map node to give the pixel grid some dimension.

That’s about it. Let me know if that clears things up for you.

19 Likes

Great stuff! I still need to wrap my head around it but thank you so much for all you hard work! Cheers!

No problem, ebi. I’m just paying it forward. :slight_smile:

Hey folks. I’ve made a bunch of updates to the material. I’ve also gone ahead and included part of the robot from a project I’ve been working on so you can play around with the dynamic paint rig.

A note on the mouth dynamic brush: There are some basic shape keys hidden away if you select the mesh. I’m just too lazy to properly set up drivers for them.

2 Likes

Amazing work, and thanks for sharing!
When I watched Next Gen I got intrigued by the eye shader indeed :smiley:

I thought you maybe used Dynamic Paint, I guess it was part of the magic hehe

I’m having issues importing an image. Where there should be an “Open Image” button, there is a slightly different one called “Unpack Item”. Help a brutha out?

Hi MerlinsMaster. The .blend has an example texture packed into it if I recall, which is sort of like a .zip file. You can unpack it by going to file > external data > unpack all. You’ll end up with an extra texture on your drive, but should then be able to open your own.

That worked, thanks!

This is so cool and perfect for the project I’ve been working on!

1 Like

Hi there! This work is truly amazing (and a lot of fun to play with)!

I’m having trouble with the animation though… I’ve opened my 3 face images, set the “image texture” node to image sequence in order to animate them using the "offset button. But when I change the offset from one number to another (say 1 to 2) the face disappears… I don’t understand why.

Some additional hints: the 3 images a correctly set as corresponding to offset 0 to 2, though to see them I have to change the image selected in the node, and set the offset at the value corresponding image.

Many thanks to anyone who could help with that :slight_smile:

A blender newbie