⚡ If you're already a Notion AI user, you can get started today with Q&A already in your Notion workspace: ntn.so/defaultcubeqa
@xrayessay6 ай бұрын
I can’t believe I got clickbaited with Ian Hubert in the title into watching a edging tutorial 😩
@girltrashstuff6 ай бұрын
+1
@pepperandsage22956 ай бұрын
nah why is this what actually happened 😭
@VODYJOLMS6 ай бұрын
bruh you putting it into words makes it so much worse
@VallyWake6 ай бұрын
as we all are (I've also subscribed just in case)
@campoyo37886 ай бұрын
phrasing. 🤣
@maximusgerardin6 ай бұрын
No one mentionned so I'll do it, but there is a built-in lens distortion by just switching the camera type to Panoramic, and then Lens Polynomial and you have a bunch of control
@Lazy_Hanby6 ай бұрын
yeah, but only works in cycles
@MDigitalProductions6 ай бұрын
Two legends in one thumbnail ❤
@Thomas_Lo6 ай бұрын
Masterfully baited my click. I guess I can now count myself amongst your generous sponsors. Enchanté, everyone! 🥂
@severinehedi6 ай бұрын
5 minutes of sponsor is crazy
@copordrop6 ай бұрын
it's actually 6:33 of sponsored content (over half of the video)
@skmgeek6 ай бұрын
@@copordropglad my sponsorblock segments helped lol
@ivanpergasiFreelance3 ай бұрын
watching you in action is like looking at my ADHD from outside of my body....
@KeirCB6 ай бұрын
There is lens distortion under cycles, the polynomial fisheye lens will help
@GANONdork1236 ай бұрын
In the viewport it only works in Cycles render view. I think what he's asking for is for it to also work in solid and material view, which I'm not sure is possible since Workbench and Eevee are both rasterization renderers and not path-tracing renderers.
@murtog15 ай бұрын
It's been a while since I visited this channel and man have I been left behind
@DLCSpider6 ай бұрын
The day Blender gets AI Python code generation is the day I will purchase and download 3DS Max.
@alvarorodriguez15926 ай бұрын
Why? Programmers are much less salty about anyone just copying their code, if they have anything at all against it.
@DLCSpider6 ай бұрын
@@alvarorodriguez1592This isn't true, there's still the ongoing law suit against GitHub Copilot. But even ignoring that, it would be a massive statement against intellectual property, even if the change itself doesn't target artists themselves directly. And with no care for IP, AI generated 3D models would just be the logical next step. Apart from that, you'd either blow up Blender's file size by a couple of GB at least to store the LLM data or it would require an internet connection to some server you do not control. An internet connection that could be used to upload your 3D models for training. Du you want all of this just to get rid of a couple minutes of googling (which you'd probably still have to do to some degree)?
@CGSTUDENT155 ай бұрын
Its like a little notion tutorial and also a sponser
@lolledopke6 ай бұрын
It’s not possible to automatically indent Python code as the indentation itself contains information (unlike languages like Java for example). You could have two programs with the same code but different indentation and they would both be valid but produce different outputs.
@steamer2k3196 ай бұрын
Agreed. I will add that the auto-formatting in something like PyCharm Community Edition is probably about as good as he's likely to find.
@bman59886 ай бұрын
Shader editor repeat zone is my number one wish as well.
@JointManJoe6 ай бұрын
ah yes, identation in python, famously used primarily for readability and nothing else...thanks AI
@lesterlauritzen6 ай бұрын
This is where a blur node would come in handy. It's a much easier way to find high frequency details using a slightly blurred version and then taking the difference. But still no native blur node in the shader editor...
@quackers9696 ай бұрын
It's not a limitation of Blender, it's just straight up not possible to do blurs and similar effects (sharpen, emboss, etc.) in shaders, at least in any practical way. Keep in mind that shaders are not pixels, they're code that's used to generate they pixels you're seeing. Effects like blurs are achieved by a weighted sum of a pixel and its other neighboring pixels. This is a problem for shaders because there's no coherent way to define what a "neighboring pixel" would even be in that scenario.
@Lucas729286 ай бұрын
@@quackers969 the fact of not having a neighboring pixel isn't really a problem, if it was the case, convolutions in any continuous space (ie real or complex numbers) would also be impossible, which clearly isn't true. The problem with a blur node is that it's incredibly inefficient to calculate due to the fact that you have to sample around each point a given amount of times for every point on the surface, for every ray sample. You can easily end up with millions and millions of calculations in a "simple" material just because it has a blur node
@lesterlauritzen6 ай бұрын
@@quackers969 then we use vectors instead of the pixels. You can already approximate a blur effect using some tricks with the vector coordinates. Or maybe have a blur option on the image texture node to apply on the pixel level before going out to other nodes, like many other apps have. Not possible? Have you seen blender’s development?!Never say imposible. ;)
@GANONdork1236 ай бұрын
@@quackers969 Bluring textures should be simple enough. The linear interpolation setting on the image texture node itself is technically a blur effect.
@quackers9696 ай бұрын
@@Lucas72928 I was oversimplifying, but yes the extra samples required is ultimately the reason why a blur node impractical to implement in shaders. The reason I mentioned images and pixels though is that the fact that for images, all the data we need to perform a convolution is already there. Whereas for shaders, we pretty much have to sample multiple times, effectively ballooning how many times the shaders have to recalculate. It's because shaders are not the same thing as images that make it so that we don't have access to the same tools & assumptions that make calculating convolutions for images a lot more reasonable to compute.
@dack426 ай бұрын
Looping in the shader nodes as suggested would likely be quite inefficient. The usual way of doing edge detection is by convolution - a generalized convolution node would be nice for this and many other texture operations (different types of blur, etc). This could probably also be done with OSL nodes.
@kunemann6 ай бұрын
My NUMBER ONE wish for blender: The ability to keyframe the visibility of collections and parent objects. I’m not a programmer, but I can’t imagine it’s that complicated. Should be feasible with a for-loop ¯\_(ツ)_/¯
@raulgalets6 ай бұрын
bro is goated. 3 minutes in I learned 187 things.
@am3sdigital6 ай бұрын
If blender had a good blur node in its shader, you could blur it slightly, then divide or subtract it from the unblurred image. Changing the blur intensity would then change the thickness of the edges it “detects.”
@Leo_Aqua6 ай бұрын
External image editing works so why can't we have external code editing?
@onjofilms6 ай бұрын
This is a fact. And probably a fact that is iterated amongst a large number of your subscribers, but I subscribed because Ian said he was a fan of your channel.
@th.e.nglish6 ай бұрын
can't you do the camera trick using Panoramic instead of Perspective, then Fisheye Equisolid. FOV 360 and lens put whatever.
@ColinFox6 ай бұрын
Auto-indentation (of incorrectly indented code, like you did in this example) in python is not possible, because the system would not be able to tell where an "if" or "for" block ended. This is the problem with python, indentation actually matters.
@sicfxmusic6 ай бұрын
00:04 For a sec I thought you are the Boeing whistleblower 🤣🤣
@wilsonwilson36746 ай бұрын
A mathematical way to find the edges is the gradient (making a 2d vector out of the partial derivatives of x and y). Then find the magnitude of that vector and threshold it to determine if it's an edge. Your way works as is, but it's something I recently looked into and thought it might interest you.
@levelupvfx6 ай бұрын
Just as a heads up, you can get proper lens distortion in the camera settings, but its pretty jank. You need to change the type to Panoramic, then if you tweak the K values, you can control distortion and focal length. These things are suuuuper finnicky though and usually you want to just tweak them by increments of like 0.001. Try each K slot out and see what it does. I think k1 k2 and k3 are the main ones to play with, k4 goes crazy really fast making it look more like a fisheye lens at almost any value. Again its super jank though, also the changes are only visible in Cycles render mode, so it makes adjusting the camera in a heavy scene pretty annoying.
@amr_antar6 ай бұрын
could u explain the speeeeedy tuts of Ian Hubert but in detail for beginners ? it will be great content here
@Tomy_Yon6 ай бұрын
That x-ray showed the alien you. 🙂
@philipashmore6 ай бұрын
Have you tried getting the AI to generate python code that implements the shader nodes you want?
@science39576 ай бұрын
Well time to go back to blender
@AdamEarleArtist6 ай бұрын
at 5:16 is this called solarization, or at least it looks very close to it.
@cashoyboy6 ай бұрын
this is my avengers endgame
@frkatona6 ай бұрын
That is some nightmarishly egregious clickbait my friend. I'm gonna have to dislike just on principle. But also this feels like an overly-complicated Difference of Gaussians
@MichaelSoluyanov5 ай бұрын
Image Input but for shaders
@thewardenwardron32636 ай бұрын
On the python auto indent: you do not want that. python is kinda annoying for this, that much is true, but indentation is how you separate code blocks. take this example: if i_want_to: place_cube() place_sphere() Now, is the 3rd line wrong? how is an algorithm supposed to know that you only want to place the spheres if the condition evaluates to true? maybe you want to place spheres no matter what, and only place cubes if you want to.
@rajendrameena1506 ай бұрын
Why not post on blender RCS...
@a2_games6 ай бұрын
parallax mapping inside parallax mapping...
@anirbantripathy52366 ай бұрын
Where is ian hubert😭😭😭
@hameddesign706 ай бұрын
a better voxel sculpting engine please im begging you, in 3d coat and zbrush we can go above 100m polygons with 4gb ram, blender struggles to work with 10m polygons with 64gb ddr5 ram please tell them to fix the issue
@Ablumz6 ай бұрын
Yeah, houdini goes crazy on the voxel and point counts as well, that is one of the core elements limiting blender from being a jack of all traders - master of all. If they also added physics nodes to geo nodes on top of that, Blender would be the end all be all 3d software
@goatpepperherbaltea78956 ай бұрын
Smh 😂
@Thomas_Lo6 ай бұрын
Oh, yeah, please don't generate wishlists or any other kind of issues and post them to open source projects. Never. Do. That. Ever.