#648 Privateer: PU - sprite corruption on XUbuntu 12.10?
On XUbuntu 12.10, anything that isn\'t a DDS or a PNG in RGBA format makes the VS engine go kookoo with the Privateer: Parallel Universe assets (but not with the native VS assets, strangely enough). On Fedora OTOH, there isn\'t a hint of trouble. From a cursory analysis, the only difference is that XUbuntu 12.10 uses libpng1.2, whereas Fedora 17 uses libpng1.5.
I figure that there\'s a higher probability that people who want to build VS will be using Ubuntu rather than Fedora, so this is intended to be the tracker issue for this rather strange phenomenon, which nonetheless is bound to have a logical explanation. I hope.
See also this forum thread: http://forums.vega-strike.org/viewtopic.php?f=35&t=18478&sid=67d75f324ce7bec1ed7ccc2d67669c61
Discussion
Anonymous
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
I've tried to attach image files, but SF won't accept files larger than 256k. I'm assigning this to klauss, as he has been my point of contact for this particular issue. I hope that is ok. =)
Last edit: Anonymous 2014-03-26
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
The crux of the issue is that It turns out that if there is no alpha channel (standard for JPEG, optional for PNG) in the sprite in question, it will show up corrupted on my screen under XUbuntu (but not under Fedora, which uses a newer libpng as previously mentioned).
As soon as I convert the sprite question to RGBA PNG, everything looks fine on XUbuntu as well.
Does the VS engine do some magic probing for the format of a sprite before loading it? Could it be that, under XUbuntu, this probing routine mis-identifies JPGs and PNGs with no alpha channel and uses the wrong library to render the sprite in question?
Are you building PU with the latest VS code or the code from the PU repo?