Volumetrics Plugin for Godot 3.2! (Coming soon): Page 3

Volumetrics Plugin for Godot 3.2! (Coming soon)

Megalomaniak

@SIsilicon28 said: Awesome recording friend! I wish I could give three awesome reactions, especially for the kind words you said about my plugin. :D <3

Well, to make you feel better awesome is worth 2 points. Like is 1.

Megalomaniak

Just a quick test recording, but I did get the capture of the running project working, just didn't think to crank up the bit-rate for the encoding. Also, since youtube doesn't support uploading from waterfox classic I put it up on the drive instead. :/

https://drive.google.com/file/d/1giT-eOtTLQOy_2VL-Fh98ElsAFvpZj_R/view?usp=sharing

SIsilicon28

That's a great recording @Megalomaniak. :D I liked how you were demonstrating the volume under lots of motion. The smearing artifacts could probably be reduced with a lower tile size or more samples. Speaking of which, what we're the settings you we're running it at?

And about the youtube export thing, couldn't you just export to any ordinary video file, and then upload that to youtube? Not that you need to. These recordings your offering are great guys, but they're not ready yet till I'm done ironing out the project, and give the demo controls to play with. That you can record.

When the demo scene is ready I'll let you know. Thank you again guys for helping me. I appreciate it. :)

Megalomaniak

For that capture just this. Did try to run with everything maxed and shadows cranked up to 1024 but that seemed a bit too laggy.

For the youtube upload, it's youtube telling me that my browser isn't supported, might just have to install waterfox current/modern side by side.

SIsilicon28

Oh I didn't know Waterfox was a browser. Oh that makes more sense. :) I sure hope my optimization will help.

SIsilicon28

Ok, so I have good news and bad news. The good news is that I added uvw scale, offset and border blending to volumetric materials. Now local volumes can have a softer falloff, and making scroll smoke is possible too (If you have a 3D texture for it)! :) The bad news is that my attempt at optimizing the renderer didn't work out. I couldn't manage to figure out how to split the processing of the volume integration to 2-4 stages. I'm leaving the shader code in there for now in case I do figure it out.

So like I said before, when the demo is ready, feel free to start recording it. Thank you for your support guys! <3

SIsilicon28

Hoo boy! I got myself carried away again. Instead of finishing the demo (which I did), I created a 3D texture generator. Now it's easier to texture fog! :D And now, I believe it is finished. You may now make a video of the demo and @Calinou, whenever you're ready, you may use your offline renderer to take a cinematic walk through the scene. I forgot to add this in the README, but the G key toggles the GUI.

Megalomaniak

Haven't recorded anything yet, but added a quit action to keymap and changed project settings to run fullscreen 1080p then exported a release build.

With default settings was running 60fps on the RX470, changing sampling to 128 drop down to hover between 57/58 frames. Changing to 64 samples and tile size to 8 dropped to 45 and tile size of 4 resulted in 29 fps.

At default the fans are running reasonably silent, but with any of those changes the fans noticeably ramped up, too.

SIsilicon28

Once vulkan is available (and I get a GPU that supports it) I'll definitely optimize this plugin further.

Megalomaniak

I wonder if it's possible to sample in a non uniform way, so points further away from the camera get less sampled and closer to camera get more. Not sure if that's even a good idea though, just a random thought. Unless you already are doing something like that.

SIsilicon28

As a matter of fact, I am doing that. The distribution property allows you to squeeze more layers closer to the camera. And by design, points further away take up less pixels than the points up close since the textures are calculated in clip space.

Edit: Also, what key did you map exiting to? I'd like to add that to the project.

Megalomaniak

I went with shift + escape, mostly because I couldn't bother remapping escape to free it up, but maybe a simple check depending on mouse state to determine escape keys functionality might suffice.

I mean escape key feels like the right choice for quitting it, but then escape key is also the intuitive thing to hit when you don't see the cursor and you are desperate to find it.

SIsilicon28

I improved the README a little more, and created a diagram showing the different volume techniques commonly used. What do you think?

Megalomaniak

testing to see if I can iframe a drive link. edit: Doesn't seem like it.

https://drive.google.com/file/d/1cgZAn6nl2VH0_YgTILjxqGmIhHZMeUdP/view

SIsilicon28

Awesome! Thank you @Megalomaniak . :D How should I credit you?

Megalomaniak

However you see fit, can just leave it be. All I did was a quick recording, and I still feel like I can probably increase the encoding bit-rate further.

SIsilicon28

Alrighty, I have a question. When this plugin is released, would it be a good idea to make a new post, or just edit this existing one?

TwistedTwigleg

I’d say either way works fine. I’d choose whichever works best for you.

SIsilicon28

Ok.

« Previous Page