Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Re-indexation to images (GIMP)
#1
Hello!

Recently I edited lots of .bmp's and I re-indexated (I mean: image >> mode >> from RGB to indexed >> the proposed pallet) those images in GIMP, because I want become them thinner (less occupied memory).
Than I launch the game and LF don't changing BLACK to ALPHA CANNAL.

Why?


--------------------
SORRY FOR WRONG SECTION. I WAS STARED.
--------------------
Reply
Thanks given by:
#2
The RGB formation of the black color should be (0, 0, 0) or U can say 'pure' black. If the black color formation is for example (0, 0, 1), it will not be recognized as the color key.
[Image: signature.png]
A-Engine: A new beat em up game engine inspired by LF2. Coming soon

A-Engine Dev Blog - Update #8: Timeout

Reply
Thanks given by: Electric2Shock , Tobruk
#3
But why? RGB image was fine, and re-indexed not fine?
Reply
Thanks given by:
#4
Usually black gets changed to something else than #000000. While you're indexing check the palette of colors carefully to avoid this. Be sure, that black color won't be changed.
Reply
Thanks given by: Tobruk
#5
alternatively you can also index it, turn it rgb again, make the almost black real black and index it again.
Reply
Thanks given by: Tobruk
#6
That doesn't make sense. If you index it the real black will get changed.
Reply
Thanks given by: Tobruk
#7
well actually not. you replace all the almost black color with black, so there is no reason for the graphics program to convert it back to a color that doesnt exist in the image.

try it if you dont believe me :p

edit: @Gad below: weird... it works fine for me in photofilter :/
Reply
Thanks given by: Tobruk
#8
Somehow doesn't work for me.
Reply
Thanks given by: Tobruk
#9
An even simpler way than what bamboori suggests would be to show the "Colormap"-dialog (Windows>Dockable dialogs>Colormap), and simply change the color of the black to "000000" (it's the field saying "HTML notation").
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
Reply
Thanks given by: Tobruk




Users browsing this thread: 1 Guest(s)