Render feature override should not be limited to menu

Game Mods
1

@Enginya Why are render feature overrides limited to menu? Could this be removed?

kép

It is important to have certain overrides on night maps, as the lack of these overrides can break lighting on low end and minimum settings.

Thanks.

3 Likes
2

As I could see it’s supported everywhere, but you have to add values by yourself, which are:

microdetails:b=yes
clusteredLights:b=yes
fullDeferred:b=yes
contactShadows:b=yes
wake:b=yes
ripples:b=yes
downsampledShadows:b=yes

Are you sure you need those in levels?

Hmm… it’s really blocked not in menu. Must be required then. You can try add menu_level:tag to your custom level template as a workaround.

3 Likes
3

Yes, this is a solution and it does work.

Are you sure you need those in levels?

I had players report me that they had broken lighting from spot lights and these feature overrides fixed or improved their problems. Also i got the codes from one of the event scenes made by the developers themselves.

Overrides used:

"level__renderFeaturesOverrides:object"{
    microdetails:b=yes
    clusteredLights:b=yes
    fullDeferred:b=yes
  }

Bare minimum settings, without overrides:

kép
kép2560×1440 1010 KB

With overrides:

kép
kép2560×1440 1.05 MB

So not sure why limit this to menu scenes :thinking: (by default)

3 Likes
4

Is it only a problem in Bare minimum mode?

Because if it is, then you should understand that Bare minimum is designed to be fast at low-end graphics cards, except for menu scenes which contain limited amount of objects i.e. optimized enough even for low-ends, so that’s why it was coded this way I think.

5

If your scene is optimized enough for low-end graphic cards, then you may add menu_level:tag for now, I think. No guarantees this tag won’t be removed or used additionally for smth else in a future, though.

6

Is it only a problem in Bare minimum mode?

Just checked. Yes. Regular minimum setting doesn’t require the overrides for spot or omni lights.

Because if it is, then you should understand that Bare minimum is designed to be fast at low-end graphics cards, except for menu scenes which contain limited amount of objects i.e. optimized enough even for low-ends, so that’s why it was coded this way I think.

This makes sense. Although, performance hit between overrides on and off are negligible or non existent in my case. I also have a PC that can run the game comfortably at max settings so this may not be the case on lower end hardware:

overrideON
overrideON2560×1440 5.17 MB

ON

overrideOFF
overrideOFF2560×1440 4.33 MB

OFF

If your scene is optimized enough for low-end graphic cards, then you may add menu_level:tag for now, I think.

:+1:

No guarantees this tag won’t be removed or used additionally for smth else in a future, though.

As long as it’s not hardcoded and unmoddable, it shouldn’t matter.

1 Like