Palette Tonemap settings aren't updating

Guest · Post by **Guest** » Tue Jan 22, 2019 5:09 am

The two cvars 'gl_paltonemap_powtable' and 'gl_paltonemap_reverselookup' aren't updating the palette lut even though I believe they are doing the calculations for it. I'm testing some new cvars which are actively taking longer to compute and it indicates to me that the fault may be happening somewhere after the UpdateTextures function from hw_postprocess.cpp.

EmperorGrieferus · Post by **EmperorGrieferus** » Fri Jan 25, 2019 11:03 am

Archie Binningbut wrote:The two cvars 'gl_paltonemap_powtable' and 'gl_paltonemap_reverselookup' aren't updating the palette lut even though I believe they are doing the calculations for it. I'm testing some new cvars which are actively taking longer to compute and it indicates to me that the fault may be happening somewhere after the UpdateTextures function from hw_postprocess.cpp.

Excuse me, but which palette exponent should be better for emulating software renderer in OpenGL mode?

Post by **Pixel Eater** » Tue Jan 29, 2019 1:06 am

EmperorGrieferus wrote: Excuse me, but which palette exponent should be better for emulating software renderer in OpenGL mode?

It's been my assumption that 2.2 is the intended value and 2.0 is the chosen default because it's faster. But seeing as it's only computed once and/or when a setting has changed I'm not sure why it would matter how fast it is. Does anyone one else know what it should be?

Post by **Rachael** » Tue Jan 29, 2019 5:56 am

Those values really are not intended to be played with. This is one of those things that I was told I had to put into the menu, even though they are really debugging CVARs that are meant to test the system and tweak it in order to produce better values.

Post by **Pixel Eater** » Wed Jan 30, 2019 4:36 pm

That's good to know, thanks

ZDoom