New Renderer (OpenGL 3.3)

The one I found best and used on all the images is the ground one. I also tested the misc one and the box one, but they either looked weird or too clean. For removing the dds artefacts I also found the one you use the best one yet. I will try different models/networks as soon I have time for it.

I noticed that you can mix models, so I ended up using a hybrid between the fallout weapons and ground textures models (you have to stay above 0.7, otherwise you will get colour shifts).

Also I developed an algorithm to automatically create roughness maps. The result can be seen in this video:
http://www.flnu.net/downloads/Fl1501.mp4

There are still some small issues left. One of them is, that somehow most of the time I find it too dark. Will be one of the next things I try to fix.

(Sorry for the long delay, was busy plus got a bad cold.)

Yeah, I see what you want to do, and I was hoping there was a way. I would use it for automatic height map creation. But for my understanding, you would need different neural network layouts for that. Btw. there is a network which creates normal maps in the wiki. I tested it, but it creates weird results (probably not good training data).

I already tried training my network with height map data, but the cnns I used seemed not to work with it. When I have the time I will try some more stuff, probably using ESRGAN.

Regarding the wrapper:

I was able to change the rendering pipeline to be nearly like: https://learnopengl.com/PBR/Theory
I don’t use any AO maps, since the bent normal maps already create a nice effect. I also changed the lights to be sphere lights and not point lights, since the suns are quite large. The latter is from UE4 engine presentation notes plus some annoying testing, since the general implementations I found seem to be incorrect and the notes are not clear on the equations.

In general I noticed most of the stuff I use now is from UE4 (if they still use the stuff).

Here is a video from a few days later back in January: http://www.flnu.net/downloads/Fl1901.mp4 In the end I disable the environment maps so that one can compare. It looks really good now in my opinion.

Basically I am now hunting the last bugs, which sadly are not that easy to find. Plus I don’t have that much time currently.

Looks interesting, but I think they still have a long way to go.

Last weekend I had time to test an idea I had for a while. Took me the whole Saturday to finish it, but the results are way better than I expected. Basically I use the generated normal maps to smooth the textures, so that I lose the details. This actually is correct, since the details are in the normal map. Before I had to downscale the impact of the normal maps, because it would look very weird. Now I can have stronger normal maps and it looks really good.

Here is a video of the result: http://www.flnu.net/downloads/fl1503.mkv

The codec is h265 this time, because with h264 it was about 250mb. Took me a while to find good settings, but now it only has about 120mb and looks quite the same.

Edit: Here is a second, shorter video, where you also can see the more 3D look of the textures:
http://www.flnu.net/downloads/fl1503_2.mp4

I don’t know what you mean with “gribles”. Can you elaborate?

Here is an example of the smoothing:
Before:

After:

As you can see, it only removes the smaller edges. That’s why I wasn’t expecting it to work as well as it does. Also I did write it more as a proof of concept. There is still some room for improvement.
For the larger ones I do have an idea for an algorithm, but this is for later when I have the time for it.

Yes, it already is batch processing along the normal map generation.

Do you have some example images of the greebles and how it looks in the game? It is difficult to image how it will look.

Also I made quite some progress. There are not many things left to do now. Here is a video of the current look:
http://www.flnu.net/downloads/fl0305.mp4
The shadow flickering issue will stay for the moment. I will look into it after the release as it is not that easy to fix.

Most of questions I already answered in this thread, but I give a short summary:
The material appearance is implemented like here:
https://learnopengl.com/PBR/Theory (except the ao maps - not needed. Example maps are at the end of the article). This should cover all the needed materials plus it is sort of a standard and should look the same in other PBR renderers. Additional height maps are also used for the pre baked extended normal maps (ssbump) and parallax mapping.

There is a json file where you can set default values (metalness and roughness) for all textures and also different values for specific texture names. But you also can use textures for both values instead (loaded by default if they exist). In my videos I use automatically generated roughness textures (that really creates a cool look) and a default metalness value. For the glass of the space domes I currently use settings of roughness 0 and and metalness 1 which gives perfect reflections. For the rest I did not have the time to create settings yet. This is why everything else is metal.

All the stuff FL can do is still supported. If it does not work I will fix it. There still is a shader for the old lighting, which I wrote to map all the states from D3D8 to OpenGL. You can see it in action here:
http://www.flnu.net/downloads/fl0405_options.mp4
It is still used for the GUI and other stuff (effects etc).

For bases the rendering is mixed (both new and old lighting). Although I did not upscale the textures yet, here is a image which looks quite nice:

So basically you want to replace part of the textures with real geometry, do I understand this correctly? It would help if there were any screenshots how it looks in FL, if you have some already.

P.S.: I am making quite good progress. Polishing just takes really a lot of time.

With polishing I meant getting it ready for everyday use. Like adding options, in game menu for those and getting rid of any annoying enough bugs I find. Also testing how the automatic texture upscaling / generation works for our custom models (for some surprisingly good, some have too bad base textures). So there is nothing really new to show currently. I still need to find a solution for duplicate texture names, like automatic renaming of them in the UTF file if they are not identical.

And yes, removing those additional details from the textures will really be hard. I did not try anything further for now.

I hope you did not lose a lot of data because of that crash. I actually currently use one of the heightmaps you did I just wonder whether it will look better than those parallax/normal maps I currently use.

P.S.: I finally renamed the topic, since the name originally was chosen by wodka back then when he split another topic into two threads. It should be more clear now.