Видео

You don't even need textures for this, just write a fragment shader that interpolates between two colors depending on the fragment Y coordinate. You can pass the model minY and maxY coordinates as uniforms to the shaders to correctly normalize fragment Y between [0, 1].

Bro how to download auto reload from the disk. I use drag and drop option but it don't show preference option like your. Plz guide me

way back when i was in school, i got a+ on graphics course: if you are using a basic gradient, if the pixel in viewport hits a non integer coordinate in uv e.g. 12.38 it will take average of 12th pixel on UV map and 13th pixel on UV map. so even with 64 pixel texture you are not losing that much data. be cause im pretty sure that inthe middle value will be same as higher size texture.

Thanks for the tutorial.

it would be so awesome to have a single image with a lot of gradiented hues and have every model in the game have that as a texture

Would you happens to have any recommendations for Grease Pencil animation tutorials? I have created a character, i created a storyboard, I created an armature, I have everything in my head ready aaaaand, I can't find a tutorial to help me figure out how to do the actual animating part? As a youtube study type, I don't have anyone to go to for help and have not been able to find a vid bring something from grease pencil drawing, to armature, to animation, then to publication. I know you're the guy to ask @Moltenbolt <3

just saw an 80 lvl post featuring this. Its rlly cool, I've been using the palette style texturing for a while now but didn't think to use gradients.

ive been doing this for a while since i started copying the artstyle of some objects i saw in a roblox game called road to grambys this trick is sometimes used in like those sloppy simplistic simulator games which is like the first instance of me seeing this trick used still really neat trick that alot more people need to know

Make sure your textures per color are at least 4 pixels wide if you try to put them in a game that'll try to use mipmaps.

How to handpaint like a BOSS: be good at photoshop daaaaaamn bro i didnt know that thanks

another tip: press tab to turn on snapping for moving minis. if your grid is not with 1m^2 units, snapping units can be set aswell.

excellent introduction for people's first character

the page you linked has the 2048 versopn, what program you use to make the 64x64?

Everyones talking about using smaller textures for optimisation. Why is no one talking about not using textures at all, and making Gradients form UV coordinates, I do this all the time in UE.

I wonder who tf makes 2k textures for lowpoly?

how did you hide the selected overlay at 3:20 to better see the model ?

I think this is really cool and was surprised at how simple it is.

This is really cool. I was wondering something, is there a reason you are painting in your light into your texture instead of using a light?

Great plugin, fantastic tutorial. Two quick questions: 1. I know I can bring in pbr images into a layer. but is it possible to use a procedural texture on a layer? I was able to get some combination using a mix shader node, but I'm hoping there's a more straight forward way to do that with the add-on. 2. is there any way to create clipping mask? (IE: draw one layer, and then have my second layer only draw within the bounds of layer one). Thanks!

can you help me pls; I installed the add-on you wanted, but when I want to select the image editor, it does not appear.

Another optimization for Kane Emanuar’s Nintendo 64 romhack…

Nice subject!

This is bad science and mostly without profiling; Arguments here do not take into account the way drivers, textures and shaders work. the difference mostly will be in VRAM but the guy's method of small scale texture might still be slow. And that is because once you use a texture; you bought the farm; there will be overhead that will take a big chunk of your performance; from that point , 64x64 vs 2048x2048 becomes less important. (If you are using a 64x64 texture; you may as well make a shader that gets a dataset (encoded in a texture, that dictate base color and gradiation values) and calculate it EVERY TIME; could be faster than getting a 64x64 texture and you can insert your entire game's textures into a single texture that reads values on how to generate the pixels gradiation). *The only thing i am unsure of; is how to make it work with UV coords. Now; going forward; the right direction will be to combine multiple small textures into a bigger atlas texture, but remember; atlas textures requires offsetting (Searching for the proper texture coords) that also costs performance. *Once more; it becomes quality vs VRAM vs speed.

I model for the N64 where every single bit of texture memory saved is important. To keep file sizes as low as possible, my gradients are literally TWO pixels. One for each extremity of the gradient. I've modeled shoes, complete with soles, a rim and even a shine on the top, with ~25 tris and a single 16*4 texture. bilinear filtering is fantastic for gradients

btw did u know u can select all faces with a similar area using Shift + G helps with the selection u were doing at 3:08

Wouldn't it be even smaller if it was expressed as vertex attribute paint?

Such a good tutorial (minus the nyehs, don't miss those). After my 3rd rewatch I figured I should leave a comment.

Holy crap, is there a way to "thumbs up" this video even harder, 'cause daaaaaamn, this video is solid gold. +1 for Android Arts, I've been keeping tabs on Arne's site for years, and it's such an awesome place.

How much of an impact will this make on performance if the textures aren´t gradients?

Feliz jueves

A small hint from a technical artist: using this approach, you should either import textures as uncompressed OR make all the ramps 4 pixels wide (due to the way compression works).

It's because the bilinear texture filtering that the GPU does for you, does most of the gradient work at a low resolution, you should be able to go very very small... until of course neighbouring pixels from other colours start to bleed in.

body you killed time thanks from game dav

I know the prices may very so no point in bringing that up, but if I didn't have a Tablet already this really sounds like a good deal. "Deuces!" P.S, I also love your little guy you made, seems like a cool MON, would also love to see the evolution big stack get completed one day too.

Let me see you do that with .x export and import using unreal engine!

I am an Art Director at a VR company, and since Meta Quest architecture is not very powerful (as it is basically just an Android phone forced to display 4 K resolution twice!), I used this technique a lot. The game is called Toy Trains, and 90% of assets use one 2 K texture with a matrix of these gradients crammed into a corner. The rest of the space was used for more detailed textures ;) (And still, 40% of this texture stayed blank because this technique was so efficient)

Does it work on subd models?

So, I guessed the 64 was on the right, however it was a mixture of things that led me to say that. If you had come out of the gate and said "Here's two models" then left them there for a moment, I wouldn't have guess there was a difference between them off the bat. (how you framed your question and the... sharpness of the 64's texture is what had me guess it but that's... just about it. It was all hunch.) This is great for low poly models, mostly for game engines. Which, is 70% of the reason you'd make them low res in the first place. Lower cost to the GPU and CPU means the game will run faster and smoother. Assuming that there aren't other factors destroying their resources. However, there should be something to note about using this for some higher poly models too. You might not be able to get away with 64x64 res, but you could lessen the size of the texture, or more importantly, give your model a different feel to them. The bevel highlight trick should be of high note as you can use the same trick on something like a buckle of a belt, or some other harder surfaces. Mixing textures can help too, but be careful not to go too crazy. Even if you aren't building something for a game engine, you want to make sure your project doesn't crash just by switching to render view. This was well worth the wait, and a wonderful end of the year tutorial, just wish I had the mental state to have gotten to it when it came out. To any new Dunces out there, keep looking to the horizon and to your feet as you move forward. If that makes sense. XD

maeking seams does nothing in project from view

4:28 incorrect. 2048x2048 = 4194304 pixels (2^22) 64x64 = 4096 (2^12) 2^22 / 2^12 = 2^10 = 1024 one texture is 1024 times the number of pixels than the other, which should translate to around the same change in file size. this is exactly why i prefer much smaller textures.

Why use textures at all if all you're adding is colors? Just use vertex colors instead!

I knew this method by the name of "Lazy Unwrapping". I think it's very fitting, but it's very good regardless :)

Very clear and I like the result. Tell me how it is more convenient for me to make a low-poly model in voxel style, so that the step between the vertices is as if on a cubic grid, but where I want it would be possible to cut off the face of the cube but still leave the vertices at the points tied to the selected grid dimension. I would also like to assign colors to individual faces, is it somehow convenient to do this in blender? Thanks

You know you could do this with zero textures at all

2025: Algorithm: anything and everything about gradients I got your back, buddy.

It seems like you could just make 1 pixel wide gradients instead of down sampling the way you did with the texture in the video. It causes a lot of the gradients to bleed into each other. But I'm sure it was just for demonstration purposes. When you reduce the gradients down to 1 pixel wide you also have a lot more play in how long and thus detailed you can make the gradients.

Large textures are why games today have massive file sizes. Thank you for sharing this technique!

Amazing stuff! Thank you!

I worked on a couple stylized 3d kids cartoons and we used this technique. Often times assets needed to be made very quickly and for simple assets we'd use the concept in our texture sometimes as the color swatch. we'd overlay a BW Grad with a seperate unwrap. It's more generic. Since it wasn't for realtime and creating multiple uv's for other parts wasn't an issue. You could always bake it as well. Edge maps/Highlights/Glows/Grunge and detail Tile and more. It's still a good workflow for a consistent look without touching Photoshop. A big benefit is the resolution of your final assets texture is way more detialed than if you baked it to a texture. There's a lot of better techniques now to help this type of workflow.