Beyond Dev - Tyler Walker

Tired of your custom normals breaking during shapekeys? #b3d #NPR

🔥 I made a new type of addon! While working on my production, I wanted to look into ways of making python tools stay local to the file-space of a Blender project, and then use these for custom pipelines. Here’s a demonstration: youtu.be/7R7NSvZOmZc #blender

@thorn_neverwake Ahhh makes sense! I haven’t added curve support yet ! Will do

@realBeyondDev This might illustrate it. I can't add curve objects to the Camkeys assignment.

Here's how to do this in the viewport w/no camera needed, in just a couple clicks, with no hair or body clipping. #camkeys makes it super easy.

これ写真勢に良さげでした 特に広角で撮る時の効果が大きい

@thorn_neverwake Oh, you’re having problems with lattice objects? Can you describe the issue more specifically and I will get it fixed!

@realBeyondDev Camkeys works nicely, but it seems to only work on a mesh object.

@ToroidalFox The flattening method does not. But the camera cone based radial method does. How do you see stereo being used in combination with this kind of fov correction ?

@realBeyondDev All these tricks have recently popped up on my feed and I'm wondering if these tricks work for stereo camera.

Many are asking: "Why not put camera further + reduce FOV?" A few reasons:✨ **Primarily to unlock artistic control.** 1. TOP LEFT: Lower fov removes depth perception. That kind of problem makes action sequences feel lackluster. But the face looks nice like a headshot. D- 2. TOP RIGHT: Conversley, w/wide angle fov, the face + hands looks all distorted. However, this does give a great sense of depth! D- 3. BOTTOM LEFT: MIXED FOV w/camkeys unlocks the best of both worlds. See how the face looks flattering like the ortho view but we still get the front hand looking bigger close to the screen? A+ 4. BOTTOM RIGHT: ANIMATED MIXED FOV w/camkeys takes that a step further. S+ **#camkeys does this all w/o changing background fov~ by only changing apparent fov of your character you can get all the details of your scene in a nice wide angle while keeping your character looking good!**

I think it comes down to workflow preference on the point of “pop”. It is possible to do animation work to make more exaggerated depth, but that’s much more fine tuning (but gives better artistic control than this mixed fov approach). Mixed fov is meant to be a low effort shortcut to forced depth similar to tons of manual bone keying (like arc system works does). In my experience this method saves me about 80% of bone placement work time in my camera acting Keyframe, but it’s not a full replacement for bone keying. On the point of mixed fov (super common in NPR to want wide angle scenes with close ups of characters) i’m not sure bone keying can solve this in a realistic amount of work. Flattening in camera plane makes most sense in the options I’m aware of

@realBeyondDev But why do you want the "pop" when character barely moves forward? Make their moves really "pop", then you won't need any tricks like wide fov, or having character's nose almost touching the camera

Yeah that’s the crux of the issue right there. Doubling distance also reduces sense of depth, and lower fov does so even further. So we lose all that pop we get with a closer camera. Ideally want to achieve a solution that doesn’t require moving the camera so we can get that nice depth change in the field of view while still getting the advantage of flatter projection rays onto character features that matter so the result more flattering without distortion on facial features etc

@realBeyondDev Obviously you loose all sense of depth with orthogonal projection. I was suggesting merely keeping fov down. Like halving fov and doubling distance. The bottom-left looks great. But it lies about how much character moves toward the camera.

@zakarum4 Oh, wow I wasn’t expecting this. Appreciate the candid honesty though. I did make the example more extreme than you suggested to illustrate my point.

@realBeyondDev Right-Down looks awful. Top-Left is not smaller fov I suggested, but 0. Ofc it looks meh.

Very cool. Would love to support this project. I’m working on a normal keys extension to the gltf format that I think would fit very nicely into this ecosystem. Happy to contribute on GitHub, but want to make sure I don’t step on any toes, I see a roadmap there. Is that everything I need to know or is there a spot with more detail I should take a look at? x.com/realbeyonddev/…

Writing some specs 😗 Proof-of-concept/prototype coming soon-ish. github.com/miramocha/Exte…

Here are all the videos in the same order so you can look more closely if you want

@iabom Sufficiently advanced geo nodes is indistinguishable from bananas. I think that’s how it went

@realBeyondDev What black magic is this

Use geodes falloff on the whole character instead of going purely flat. #camkeys even passes viewport data to the GN so you don’t even need to use a camera.

@ArrisTottle_ x.com/realbeyonddev/…

@realBeyondDev Why not just change the focal length

Good question! A few reasons ✨ 1. Lower fov removes depth perception. Take a look at the video below. See how the ortho (low/zero fov view) makes the back hand the same size as the front hand? The hand in front needs to be way larger to give good sense of depth. That kind of problem makes action sequences feel lackluster. But the face looks nice like a headshot. 2. At the same time, if you look at the single wide angle fov, notice how the face looks all distorted. The hands and other details on the edges of the lens do too. However, this does give a great sense of depth! 3. Flattening with falloff in camkeys unlocks the best of both via mixed/multiple fov’s. See how the face looks flattering like the ortho view but we still get the front hand looking really big close to the screen? If we were to just play this green haired girl back with low fov / ortho view she wouldn’t look like she’s leaning in close to the camera or moving far away. That’s the big difference here. x.com/realbeyonddev/…

@realBeyondDev Why not just put camera further and reduce fov?

そうなんです！僕のアドオンでは、Geometry Nodes内でデフォーム前の法線を先にキャプチャしておいて、頂点位置を平らにつぶす処理のあとに「Set Mesh Normal」で元の法線を書き戻しています。 なので、形状は変形しても法線まで平らな形状に合わせて再計算されにくく、元のシェーディングをできるだけ維持する仕組みです😊

モデルのデフォームは全体に均一にかかるのではなく、 カメラ距離にも応じるんだな。 逆パースじゃなくて平らにつぶしちゃうけど、こちらのアドオンでは法線はどうしてるんだろう。🤔 #Blender #b3d

They are asking about my addon I think which does something a little like what you’re doing with geodes. @Crashbandit03 you can go to my store page to find docs, there’s also a video there, and some videos and examples on my x profile. I won’t advertise my addon with a link here tho ✨

@Crashbandit03 @realBeyondDev Which addon are you talking about? This is my geometry node setup, done with Blenders default nodes.

Developed my GN further, works now with separated meshes too. Instead of flattening, I warp the model so looks like it was filmed with another focal length. Vertex groups to make the arm 80°, the face 0.01° and rest appears 20° focal (due to camera setting) #blender #b3d #geonode

@realBeyondDev Its interesting how different the angles end up becoming because of the flattening thing. It inspired me to try and paint it out just to see how it’d look to try and illustrate those angles whilst keeping the directions…

@krysidian Exactly 👍 good intuition

@realBeyondDev Are you using Python to pass in Viewport information into GN?

@MannerBoy1981 gn ✨

@realBeyondDev good night Beyond 🌖