Redoing map levelshots #3416
Description
We may want to redo map levelshots, because of many improvements or bug fixes:
- fixed black lines in mipmapped CRN (affected vega levelshot)
- fixed shader remap (affected thunder levelshot)
- implemented linear color blending (affected all maps, require rebuild of maps), also needing:
- (not implemented yet) alternate alpha blending in linear color blending (affects maps like plat23)
- (not merged yet) relief mapping scale and bias, also needing:
- (not done at all) reimport original height maps using scale and bias (affects maps with height maps)
Because our levelshots are displayed full screen in map loading screen, we are now used to distribute them in 4K, to save file space, we store them as WebP in repository, but, if I'm right, in lossless mode to avoid piling WebP artifacts under CRN ones.
Because levelshots take a lot of space in repositories, we better avoid redoing it every now and then so we better redo them on important milestones. Thunder levelshot with wrong lightnings (dure to broken shader remap) or Vega levelshots with wrong screens (due to bad mipmapped CRN) are used for a long time, it's not a big deal if we keep them as is for the time we have more enhancement to show in such levelshots.
For reference, here are the viewpos I used to make the current levelshots:
antares -1013 -378 130 -47 -32
chasm -1866 -457 296 40 0
forlorn 2243 2217 348 125 -8
parpax 497 -2242 485 0 27
perseus 2592 -504 339 90 0
plat23 -229 2360 70 -59 -5
spacetracks 420 -1928 638 -31 -16
station 15 1168 -1240 114 124 -15
thunder 491 -808 -159 -65 -12
vega 1472 -1792 176 -180 0
yocto -2604 969 459 0 0
Related issues
Related topics
-
The possibility to create a specific entity to store the map levelshot viewpos in the map itself for making easier to redo the levelshot.
-
The opportunity to use lossy WebP for storing levelshots in repository.
As we know, WebP lossy artifacts are far less problematic than JPEG ones:
