anyone can explain:
Why when I create the interface, and when I push out, I merge the pixels?
Interface merge pixels
- paladin MAIK
- Posts: 339
- Joined: Mon Aug 06, 2012 12:31 am
- Location: (Russia)
- Contact:
- juliocpaes
- Posts: 1263
- Joined: Mon Feb 14, 2011 12:07 am
- Location: Madrigal - Brazil
- Contact:
Re: Interface merge pixels
The hot pixels in the image look like they might be caused by a color table mismatch between the collection and the imported bitmap. Are you using Oak? When you import the image, are you getting a warning about the color table?
- paladin MAIK
- Posts: 339
- Joined: Mon Aug 06, 2012 12:31 am
- Location: (Russia)
- Contact:
Re: Interface merge pixels
Yes, I use Oak.Melekor wrote:The hot pixels in the image look like they might be caused by a color table mismatch between the collection and the imported bitmap. Are you using Oak? When you import the image, are you getting a warning about the color table?
Naturally I get a warning about changing the color of the table, but even if the color coding table in Image Ready, and I like two images have the same color table, I still have it appear blur ...
I also used Tahoe - the same result ...
Re: Interface merge pixels
I just remembered, this could also happen if the image uses color index 0 or 1 for some of its pixels. Those indexes count as transparent in game in most situations.
Re: Interface merge pixels
Aye, as Mel says, make sure the first 2 colours in your colour table are completely unique (that is, those colours don't show up anywhere in the images you want to use for your collection), and then you shouldn't get any interference. You're definitely experiencing transparent pixels.
Most common settings for those 2 are (in order of Hue, Saturation, Brightness) 240, 100, 100 Blue, and 300, 100, 100 Pink.
Most common settings for those 2 are (in order of Hue, Saturation, Brightness) 240, 100, 100 Blue, and 300, 100, 100 Pink.