OpenXcom Forum
OpenXcom Forks => OpenXcom Extended (OXCE) => OXCE Support => Topic started by: Keth01 on April 21, 2018, 08:24:33 am
-
Hi all,
I've recently moved my modding over to OXCE+ and have encountered a weird issue where a BigObject image shows normally (i.e with appropriate transparency) in OpenXcom but the exact same file displays with a black box in OXCE+.
GIMP reports that the transparency is set up right to the best of my limited knowledge and it runs fine under OpenXcom soI am at a bit of a loss as to what to do.
Please find image attached for reference.
-
Meridian has an explanation of the issue here (https://openxcom.org/forum/index.php/topic,2915.msg93065.html#msg93065) - the gist is that OXCE's scripts that can alter bigobs aren't as forgiving on GIF transparency as OXC. You shouldn't use GIF transparency on item or unit sprites, fill with color index 0 instead.
-
Besides, .gif images don't work well on Macs (apparently these exist and people play games on them), so best solution is to just use .png instead.
-
Converting to .png sounds like the easiest fix then, I'll give it a shot. Thanks!
-
Converting to PNG solves the Mac issue... it doesn't solve the transparency issue.
The only way to solve transparency issue is use color 0 as transparent. If you use other color, game will ignore it, regardless if it's gif or png.
-
Hmmm... Why would anyone use any other colour for transparency? O_o
That's the problem with all my advice, it always fails to predict weird choices from modders. :P
-
Well, I converted to .png and it *did* solve the issue, so I don't know what to tell you there :P
-
Well, I converted to .png and it *did* solve the issue, so I don't know what to tell you there :P
--- posts merged. Yellow card :P ---
...actually, the conversion process probably re-indexed the transparent layer to something sensible, now that I consider it.
Anyhow, I've converted all 150+ images currently in the mod over to .png and have adopted it as the standard going forward, so no more issues there hopefully.
-
Yeah, that's what I did myself.
As an added bonus, I no longer have to worry about defining a wrong file type declaration in the ruleset. :P