Ultra Engine testing

[Josh]

@klepto2 It would be easy to work those objects into the clustered forward grid so this is definitely doable.

[klepto2]

added a moon  with moon phases depending on the sun angle

needs some tweaking and the light of the moon is not included yet. 

[Vida Marcell]

Bruh whats going on here, how you guys have ultra?

[IceBurger]

19 minutes ago, Vida Marcell said:

Bruh whats going on here, how you guys have ultra?

Those that have access to the SDK can get ultra

[SpiderPig]

A few of us are testers.  Its not finished yet.

[Josh]

Here are the results I am getting mixing screen space reflections with environment probes. The two blend very nicely. Of course it will look bad if you make a level out of mirrors, but if you use normals maps to break up the reflection and only make some parts shiny I think this will give good results: Also note how the sky reflection pans in reflections, instead of being basked into the probe cubemap.

 

[IceBurger]

28 minutes ago, Josh said:

Of course it will look bad if you make a level out of mirrors

There goes all hope for that house of mirrors horror game I queried about in January

[Josh]

It's not very glamorous but this is important: I replaced my screen unproject functions with matrix-based functions that can handle any arbitrary projection matrices. This is important because some VR headsets use funny projections for rendering. This is the reason Leadwerks does not support post-processing effects in VR, but now it should be no problem.

https://community.khronos.org/t/position-reconstruction-from-gl-fragcoord-and-depth-value-using-matrix-multiply/109115

[Josh]

I've got the lighting working consistently between SSR and environment probes now. An SSR reflection gives identical light levels to the environment probe. Next step is to blur the SSR so it matches the roughness of the environment probe sampling. You can see a few artifacts here because the SSR is perfectly sharp but the env map reflection is rough.

[Josh]

Adding randomness to the reflection vector is pretty effective at handling rough surfaces, but it introduces a lot of graininess:

[Josh]

More ray samples lowers the framerate but it looks quite good. I need to try isolating the SSR result and running that through a denoise filter.

[Josh]

Looking good, but I want to try one more approach:

[Josh]

These results are promising. Graininess is gone, edges are still sharp, and performance is much faster.

[SpiderPig]

Heaps faster, looks great!

[Josh]

Yeah, I think this approach will work very nicely. All the artifacts are mostly eliminated and the cost of the effect is very low. This is all being rendered on a GEForce 1660.

These slides were helpful:
https://www.ea.com/frostbite/news/stochastic-screen-space-reflections

[Josh]

It's looking very good:

 

[IceBurger]

1 hour ago, Josh said:

It's looking very good:

I can't believe it 👀

[reepblue]

I have been getting as kick of your video thumbnails but I honestly don't think your exploiting the algorithm to the fullest. Maybe next time try adding red borders, arrows and circles to create a sense of urgency. Emojis are cute and everyone likes them so maybe add a few of those in for good measure. You can also try being creative by including meme references and/or anime girls in your thumbnails.

Play stupid games, win stupid prizes. 🤡

[Josh]

Zero graininess, zero flickering, even with bright lights and very rough surface. SSR roughness matches environment probes closely. Framerate is fast, maybe I can make it faster.

[Josh]

This is so much higher quality than what I was getting with voxels.

[klepto2]

Hi Josh, 

while you're working on new features and refining them, i would like to suggest some improvements to the client hub:

1. Update-Tab:
   1. It would be nice to have a Button to directly browse the installation directory (like in the Projects tab, where you can click on the project to open the base folder)
   2. Another addition, which would be nice: An ability to create a backup of the current installed Version, currently I keep track of this manually and create backups, but depending on how you plan to support multiple version channels, it might be nice to easy rollback to a previous one. (without hoping that you provide the correct version channel, maybe a simple zip file or tar)
2. Project-Tab:
   1. The warning icons and delete button are not indicating, that they can be clicked and there is now real indicator what happens if you click them (tooltips to the rescue?)
   2. The delete icon should be replaced (in my opinion) with a trash bin or something like this. A hint, that the project is only removed from the project tab would be nice as well.
   3. Backup:
      1. The backup should be kept in a separate folder, which should mimic the original folder structure. The current system fills the dev folders with unnecessary files, which can make the fast searching in folders quite complicated. Also with version-control in mind, it would be easier to manage, if there is just a folder with the backed up files, which can be easily be deleted on demand. Currently, you need to filter all bak files and remove them, but this can also lead to problems if a developer maintains their own bak files. 

 

[Josh]

I think I am ready to call this finished. We've got rough and sharp reflections, it blends well with environment probes, and the probes are very effective at preventing light leaks. You'll notice these reflections don't spread out like previous shots did, but the framerate is so fast and I think normal maps will break up the reflection a lot. Once you start adding randomness / jitter into the reflections you create error, and that error has to be averaged out over a very large number of samples, with greatly diminishing returns.

Crytek did something similar in "Ryse":

[Josh]

RTX could easily be worked into a single shader that would provide offscreen reflections, running through the exact same filters as the SSR reflections. I am starting to think that ray tracing is just another tool to use in combination with probes and light mapping, rather than a total replacement of all lighting techniques. I mean, you could use ray tracing alone, but you would have extremely low limits on the scene poly count.

[klepto2]

If you want some basic syntax highlighting and error reporting for the shaders in visual studio I can recommend this:

https://github.com/danielscherzer/GLSL

Configuration to let it be compatible with Ultraengine and Vulkan:

The Expand includes is currently needed as the Compileprocess generates a temporary file under %temp% and so there is no direct access to the include files in the shader, but the error detection still works. it can't compile yet to spv files because the Arguments-System is a bit limited, but maybe we can change this

[Josh]

New command Camera::SetRayTracing:
https://www.ultraengine.com/learn/Camera_SetRayTracing