Rend2 - A Modern Renderer

[SomaZ]

Another progress video on the refraction shading. Some stuff is still missing, but i think it looks quite nice right now.

https://www.youtube.com/watch?v=rLCSrBlEU3Q

[Futuza]

I think the effect, at least for the bubbles might still be a bit too severe.  Force Push/Pull seems fine though.

[SomaZ]

I think the effect, at least for the bubbles might still be a bit too severe.  Force Push/Pull seems fine though.

Hm, problem is, that the vanilla refraction is hard coded for the objects. There are no individual refraction parameters for e.g. the invincibility shpere or the force pull. I will lower the effect strenght and see if thats better.

[Xycaleth]

There's a few parameters that the game sets. Check tr_main.cpp

[SomaZ]

Ok i found what vanilla does. Its in tr_shadows. So game actually sets some stuff, but nothing really useful for an actual refraction. They simply take a part of the rendered picture (the size and middle point of the cut out are defined) and put it on the "refractive" surface. Then they have a variable to strech it. It's basicly zooming in and out with some blend modes. There is one variable which is usefull for my current implementation. It's the alpha of the refraction. But i will add the wobble/stretch effect of the vanilla render.

[ensiform]

They also use image or shader "-2" to signify that its something that needs to be refracted, no?

[minilogoguy18]

I check this thread every time I sit at my computer, so glad it's being worked on again.

 

Gonna wait til the next build when supposedly some things are going to be fixed before I download and start testing models that use displacement maps.

[SomaZ]

They also use image or shader "-2" to signify that its something that needs to be refracted, no?

The only thing i know is that there is an entity flag RF_DISTORTION. And this is manually set in the game aka hardcoded. Also the vanilla renderer rendered stuff refractive only with that flag. I'm not sure what you mean with image or shader "-2". You mean in the old id3 shader files? I will investigate if the renderer sets the flag, but right now i doubt it.

[Tempust85]

@@minilogoguy18

 

Afaik, displacement maps either aren't supported or do not work correctly on models. The only place they work is maps.

[SomaZ]

@@minilogoguy18

 

Afaik, displacement maps either aren't supported or do not work correctly on models. The only place they work is maps.

As far as I know the only engine that implemented parallax displacement on animated models is CryEngine. They called it the secret toad tech in a trailer.

[Tempust85]

Even if player models had displacement maps working, it'd have to be used very carefully or you won't get a decent result. Tbh, normal maps suffice.

[AshuraDX]

As far as I know the only engine that implemented parallax displacement on animated models is CryEngine. They called it the secret toad tech in a trailer.

not parallax - actual vertex displacement + ridiculous tesselation

[SomaZ]

not parallax - actual vertex displacement + ridiculous tesselation

 

You are right, they called it the "Top secret tesselated toad tech". Damn, i need to check my facts before i post something here.

[Tempust85]

Ohhh, I was thinking parallax.

 

Also a bug carried from ioquake3's rend2 is parallax textures meeting at a wall join/corner produces a gap in the brushwork. Not sure if this can be fixed at all, but worth mentioning.

[Xycaleth]

New build with dlights turned back on

[SomaZ]

Ohhh, I was thinking parallax.

 

Also a bug carried from ioquake3's rend2 is parallax textures meeting at a wall join/corner produces a gap in the brushwork. Not sure if this can be fixed at all, but worth mentioning.

its called parallax occlusion mapping with silhouettes. I guess that would be the problem solver for this particular problem. But it comes quite costly. And i think it never was really usable. The tesselation stuff with displacement replaced that immediately.

 

 

New build with dlights turned back on

nice, i will totally check that out.

[ensiform]

Are there any maps etc that have rend2 features to test available?

[Silverfang]

Are there any plans for PBR?

[ensiform]

I thought there was talk of looking into it but he's not focused on adding any new features right now.

[Xycaleth]

Are there any plans for PBR?

rend2 already supports PBR to an extent. I just need to review it to make sure it's doing everything correctly.

 

Are there any maps etc that have rend2 features to test available?

Not at the moment.

[Xycaleth]

Sorry there's not been any updates so far. I've been fixing the fall out from my latest optimizations I'm planning to get back to adding fog/weather system when I've done that.

[Xycaleth]

Been doing some research on PBR workflows. As far as I can tell there is a metallic and a specular workflow. Those of you who have experience with both, which do you prefer or think is better? From my point of view, the metallic seems to be better since it's more difficult to get wrong and uses less texture memory. Thoughts anyone?

[SomaZ]

I prefer the metal roughness over the gloss specular workflow. You can pack roughness and metal in one texture (only 2 grayscale layers and 2 are still free for eg. height), so its less textures to worry about. Since I work with Substance Painter its kind of irrelevant for me, because you can make custom texture exports. Also you won't need two colored pictures (color & specular) which kind of tells you the same stuff in PBR. Marmoset has a page with pro and contras https://www.marmoset.co/toolbag/learn/pbr-conversion (down at "Metalness Workflow vs Specular Workflow"). I hope that helps a bit.

[Scerendo]

Been doing some research on PBR workflows. As far as I can tell there is a metallic and a specular workflow. Those of you who have experience with both, which do you prefer or think is better? From my point of view, the metallic seems to be better since it's more difficult to get wrong and uses less texture memory. Thoughts anyone?

 

I prefer metallic personally, but I use quixel and substance so it doesn't make too much of a difference.

[Archangel35757]

Been doing some research on PBR workflows. As far as I can tell there is a metallic and a specular workflow. Those of you who have experience with both, which do you prefer or think is better? From my point of view, the metallic seems to be better since it's more difficult to get wrong and uses less texture memory. Thoughts anyone?

Since this engine and game art used the traditonal Diffuse/Albedo & Specular maps... I think the transition would be easier to maintain a PBR Specular Workflow (with the additional AO, Cavity, and Normal maps). That will also likely produce better results (avoiding edge artifacts at material borders) with existing models/textures when converting them to PBR Specular in your code.