Description:
JKA maps loaded into JK2 have about 100% more brightness, this is caused by the default r_overBrightbits 0 JKA uses (also maps were designed with this setting in mind).
Images:
Manual solution:
For a player to fix this manually, it would require to put in the console r_overBrightbits 0; vid_restart; upon loading a JKA map in JK2mv, and then r_overBrightbits 1; vid_restart; upon loading back a JK2 map.**
Fix request
Since the current implementation of loading JKA assets is already aware of a map being from JKA, it would be good to have an automated way of doing just that, adjusting the overbrightbits back and forth when loading JKA/JK2 maps.
Might be a better (better than requiring a vid_restart upon loading a map) approach for this though, but this method at least makes it looks close enough to JKA brightness.
--
Thanks to mjt and Tom, otherwise I would've been wasting hours adjusting lightmaps, which was not the issue at all...
Description:
JKA maps loaded into JK2 have about 100% more brightness, this is caused by the default
r_overBrightbits 0JKA uses (also maps were designed with this setting in mind).Images:
Manual solution:
For a player to fix this manually, it would require to put in the console
r_overBrightbits 0; vid_restart;upon loading a JKA map in JK2mv, and thenr_overBrightbits 1; vid_restart;upon loading back a JK2 map.**Fix request
Since the current implementation of loading JKA assets is already aware of a map being from JKA, it would be good to have an automated way of doing just that, adjusting the overbrightbits back and forth when loading JKA/JK2 maps.
Might be a better (better than requiring a vid_restart upon loading a map) approach for this though, but this method at least makes it looks close enough to JKA brightness.
--
Thanks to mjt and Tom, otherwise I would've been wasting hours adjusting lightmaps, which was not the issue at all...