Release: Advanced Renderer v. 1.1 beta 1

[Schmackbolzen]

Thanks I really hope so!

Regarding point 1:
It might actually be a good idea to link here. I will think about it. But currently it is up to you
As for point 2:
I added some more things I forgot to my original post. That includes instructions how to get the menu of the renderer open. Also I mentioned that the 1.1 patch is necessary. Do you have it installed? Plus I never tested whether SP works. Will do that later.

[SWAT_OP-R8R]

Thx for the quick reply.
I did not use the 1.1 patch. I’ll try that later tonight.
Maybe it would be worth to include the 1.1 patch right into the renderer download to simplify it for the players? Again, just an idea.
If I get it working with the 1.1 patch I probably can try to figure out why the modded game crashes as soon the mouse cursor moves. I’ll share the results as soon available. Maybe that might help others if they run into similar issues.

[IrateRedKite]

Amazing work! I plugged this into BMOD with zero configuration on either end and did a quick fly-through: https://www.youtube.com/watch?v=mzCYwa0ACuY

Out of the box it looks great. Looking forward to seeing how this develops further, incredible work

[SWAT_OP-R8R]

The 1.1 patch indeed did the trick with vanilla FL.
I also narrowed down the issue with the mod incompatiblity to two custom plugins. One plugin that altered some keymapping stuff (apparently conflicts with your keymapping code) -> in the end not a big deal. The other plugin is a custom anticheat version. This needs some further investigation.
In the end probably nothing that would cause troubles for other mods/players.

[Schmackbolzen]

That is good to know! Can you give me the name of the plugin with the keymapping problems? Maybe I can fix the issue. It probably is one from adoxa, right?

@IrateRedKite: Thanks! I am very happy myself that it works so easily. Was expecting it to be more difficult. Also watching videos from others using it is very interesting. Very curios what people will do with the renderer.

[SWAT_OP-R8R]

The keymapping plugin was a custom one, not created by adoxa. I don’t have the source code but I contacted the creator of the dll. It might take a few days to get a reply.

[NeoTendar]

@Schmackbolzen said in Release: Advanced Renderer public beta 2:

ids_name = your id (add entry in your resource dll)
ids_info = your id (add second entry in your resource dll)

I would like to know how to add entries in my ressource dll

Btw an amazing renderer you made here ! I installed it in SP and everything seems to be fine.

EDIT: Nevermind I left the ids blank and the shortcut work !

[A Former User]

Some surfaces are very bloomy (overbright) - how to mute them down? (Gamma won’t work)

[SWAT_OP-R8R]

Probably by creating fitting specular maps (MetalnessMaps)

[Schmackbolzen]

Yes, if a constant value is not enough, then you need to craft special roughness/metalness maps. Otherwise just create a new entry in materials.json or use an existing one which is working for that.

Since a lot people asked about that (especially custom planet textures) I added some text about it to my release post.

@NeoTendar: Thanks! Yeah you can leave them empty if you do not need any text.

[A Former User]

So only metal textures having overbloom effect?

[Schmackbolzen]

For PBR rendering this also depends on your light source. With old lighting, the light intensity was in range from 0-1. With PBR you can have 0-infinite (or rather max float, due to hardware limitations). This is why I added tonemapping. It makes it look more like film (yes, analog film) would behave. I will try to explain this later in more detail in my documentation.

In short if you don’t want to have it so bright:

• Change roughness of material
• Reduce light color intensity of light source or reduce its range

Note that the viewing angle also plays a role.

[A Former User]

I use vanilla FL - not modded. Yes. Old lightning works well.
Why not to release these short answers directly for vanilla?

Tried other settings: much better

[Schmackbolzen]

The default settings in materials.json are more a rough orientation. They are used in our mod, where I have proper roughness and normal maps.
Note that I released the beta also so that people can understand better how PBR works. You will have to adapt your mod if you want to use it.
Also what you disabled there is the tonemapping, which just caps the maximum light value to 1. It is not a fix.
There will be another factor you can change soon: It is the exposure value, which already is used and currently set to a fixed value. I did not add this on purpose yet, because I am afraid people will use it wrong.
The idea is that you can change it in the config, or that I allow a value to be set per system. I also will experiment with automatic exposure control later.

[A Former User]

Used recommendations!
All Materials.json settings just not more than 0.2

Materials.json
Config.json

As you can see - no more overexposure (over local contrast).
P.S. Btw i have used graphically patched freelancer.exe before - sooooorry

[A Former User]

About photography - there is fun feature at Reshade = LUT.
You may use LUTs from Photoshop, Lightroom, etc
Might do add something similar to tonemapping option?

[A Former User]

Final variant for Vanilla Freelancer:

"Roughness" : 0.6
"Metalness" : 0.2

config.cfg
materials.json

Now there is no local overexposure at all.

[A Former User]

Light sources and headlight are not working at my mod.
And i have only Directional lightsources.

With: https://i.imgur.com/JnVNG1J.png
Without: https://i.imgur.com/VX1MzAd.png

[IrateRedKite]

@HeIIoween Looks like point light sources aren’t actually in just yet! I suspect they’re on the to-do list, these are also something I am eagerly awaiting

[Schmackbolzen]

To make this more clear I added it to the known issues list.
I disabled the point lights because vanilla FL uses them in many systems for fake planet ambient light reflections, which look weird without shadows. Also if those lights have shadows enabled they are too close to objects and the shadows break.

I will add a developer menu soon where you will be able to enable them. But if you don’t change the system inis lighting will be weird then at those places.

I never tested spot lights, so I will have to enable them and see if it works. They will for now not have shadows, though. If they work I will enable them by default.

I will add some other useful stuff to this menu, like reloading all textures (only in FLARDATA\textures), reloading the materials.json, reloading shaders and I also think about adding adoxa’s hook for reloading the system in case it also reloads the models (not tested yet). This should really help for live testing stuff.

Also as I already wrote in discord chat to @HeIIoween, you should not reduce metalness too much if the material is metal. I just write it here again so that people do not get bad advice. You can see here, what happens if you do that (it behaves more like e.g. plastic or ceramic).

I also added some more PBR links to the documentation (more to come).