Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Map FrostyCove v1.5

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
7/18/2019 11:35:59 AMEErankAdminAnarchid before revert after revert
Before After
1 Compilers can be sneaky in their application of compression. 1 Compilers can be sneaky in their application of compression.
2 \n 2 \n
3 No compression param may mean "use default compression". 3 No compression param may mean "use default compression".
4 Putting compression strength to zero may still have it generate mipmaps for DDS texture segments. Or compress things it think will be "lossless". 4 Putting compression strength to zero may still have it generate mipmaps for DDS texture segments. Or compress things it think will be "lossless".
5 \n 5 \n
6 For example, SpringMapConvNG will decide whether two tiles are identical (and one can be compressed away entirely) without comparing the alpha channel, which nastily breaks any attempt to use `voidground` with that compiler. 6 For example, SpringMapConvNG will decide whether two tiles are identical (and one can be compressed away entirely) without comparing the alpha channel, which nastily breaks any attempt to use `voidground` with that compiler.
7 \n
8 TL;DR recompile the map using different compilers, upload all versions, then have affected people see if any of those are not bork.