2D Toolkit Forum

2D Toolkit => Support => Topic started by: TMK on December 26, 2012, 10:56:37 am

Title: Pixel-perfect on Bilinear on Device
Post by: TMK on December 26, 2012, 10:56:37 am
I'm having trouble getting pixel-perfect art on actual devices when using bilinear. It appears slightly blurry. It works perfect in the editor or PC/Mac standalone builds, it's 100% pixel perfect there, but on my iOS devices or Android devices its blurry.

Attaching a screenshot taken of my Galaxy Nexus (1280x720) of tk2d_demo 11, where you can see the hearts are blurry.

I've made sure of everything I know of that could effect this:
As the screenshot shows, it happens not just in my own projects, but also the tk2d demo projects.

I know that it should work to get things pixel perfect using bilinear, because it works fine in NGUI on devices (in my game I'm using NGUI for all GUI, while 2D Toolkit for game itself), but I'm having trouble getting it to work on devices in 2D Toolkit...

To reproduce it, I'm just opening tk2d_demo 11, making sure it looks pixel perfect in the editor, then building Android version and running it on my device, and using Android SDK's DDMS to take a screenshot from the device, and comparing it with the original PNG version of the heart.
Title: Re: Pixel-perfect on Bilinear on Device
Post by: unikronsoftware on December 26, 2012, 11:23:12 am
I've just tried it on an iPhone4S and it looks pretty exact to me - compared with photoshop using difference and can't see any diff.

Please drop me an email to support@unikronsoftware.com - I have something for you to check from the latest version (1.90). I think I may have fixed an issue which might have inadvertently sorted this out.
Title: Re: Pixel-perfect on Bilinear on Device
Post by: TMK on December 26, 2012, 02:01:07 pm
Thanks for the fast reply! Sent an email now :)
Title: Re: Pixel-perfect on Bilinear on Device
Post by: TMK on December 27, 2012, 11:17:24 am
Update: This was an issue that only happened on sprite atlases that are larger than 512x512, and was fixed by using the newest version 1.90. Thanks again for the fast fix! :D