How I 3D scanned a whole freakin' mountain range with a drone | FULL WORKFLOW 

Man what an experience that was. I'm used to multipitching, but the idea of dropping something hundreds of feet was just utterly terrifying.

@@pwnisher definitely a tradeoff when climbing where you have to sacrifice a little bit of your comfort zone for a great experience!

Heck yeah!! Thanks so much for checking this out 🙏🏼

Hahahha i try, and can't do it alone! Thanks for your kind words!

Shoot it's gonna be SOON too!

Thanks Matthew!!

Go get it and be safe! Thanks for watching!

@@pwnisher no, thank you!!! For posting Masta Clint! Stay safe keep creatin' and collaborating, and always inspire imagination! Peace

Mr. ANTZ! Yooo wassup! Thanks dude! Yeah all Unreal Engine :D I'm falling deeper in love with the program.

@@pwnisher yeah man unreal is great ! You definitely inspired me to learn unreal:)

well u would need to shoot at overcast days and also try to get a drone that can fit godox ar400 ringflash with a dslr so that there are no shadows there.

In my case, it wasn’t severe because the sunlight only hit like 10-15% of the scan (cause we got there so dang early) but I also chose lighting condition (in 3d) that favored the scan, as well as framed out the pre-baked lighting as best i could.

for gta6

Whoa!! I’m legit curious now! I’d love to see this in action. If you’re on Discord, hit me up (link in description)

@@pwnisher Sure, just did, sent you a dm on discord

@@BartKuipersdotcom Did you guys ever do this???!

Textbook, son!

If there's a better way to set up the normal channel i'm all ears! Thanks for the headsup.

@@pwnisher I wanted to link to a relevant article, but RU-vid doesn't like that. Here's attempt 2 without the link. Best: leave them untouched, unlike bump maps they're already accurate. Medium: look at normal map blending techniques like the one described in "Blending in detail" by Colin Barré-Brisebois and Stephen Hill (a.k.a.: self_shadow) Better than nothing: chuck a normalize node at the end. Some normals may still be a weird angles, or 0, but at least the non-zero ones are at least the right length.

@@pwnisher Yep lerping a blue color isn't how to do normal strength, the blue channel on a normal contains no information it's essentially a 50% gray on the blue channel. Lerping in general should be viewed as a gradient switch to blend A and B, if the alpha switch is overshooting value between 0 and 1 you are essentially boosting the A alone in an unpredicting way. You should multiply by the same number your R and G channel then combine it back with it's blue channel, normalize the result and plug that in. Red and Green channel is what containing the normal lighting info in X and Y , which is why there are different formatting (directX OpenGL) based on the software axis system (y-up, z-up). To sum up on your example: (R channel * float "normalStrenght") (G channel * float "normalStrenght") then feed the result back in a "AppendMany" (where the blue come from the original one or just a number 0.5) to construct the resulting normal, normalize node before plugging in. You could also plug in a lerp between the boosted normal and the original giving you even more fine tuning controls as long as you clamp the control value between 0 and 1. Furthermore, desaturation node works better than choosing a channel from the albedo texture, since the real way of desaturation is to average the channels ((R +G +B)*.33). But this is almost accurate. Otherwise never ever use a 16k textures in a game engine, when unpacked in memory your 2 textures would be using around 2GB of GPU RAM. it would be really really bad in a gaming context you would have tremendous chugging in streaming and the amount of crash reports on your game would be unmanageable ;). People sometimes mess up their understanding of weight of textures in a realtime context, it's not the compressed size that matters if the file is 138mb it's not relevant at all apart from telling you the size it will require on disk, when opened in memory it's uncompressed and for textures it's ((pixelwidth * pixelheight * number of channel) *1.3 mipmapping) bytes.

@@2Jackrabbit Good addition about the uncompressed size! As for the R,G channels; I would expect it to be better to decode the normal, rather than trying to manipulate it in its compressed form.

@@RC-1290 No it would be totally fine since shaders works at runtime into what is uncompressed already ;) But that would still be the way to make a normal intensity, not a lerp with overshooting value in the alpha. That is something I teach about shader math, if you are "boosting" a lerp you either have the input wrong or using the wrong operation. A quicker way otherwise in unreal is to use the flatten normal node with a negative value.

Agreed! I try to tailor them that way as often as possible.