1
\$\begingroup\$

The image below is representative of my client's experience running the released version of an app I created for him on his Windows XP Machine.

I built it using Unity 4.5. The messed up buttons are the product of a png import to a sprite render all done using the Unity editor. I created the sprites at a resolution of 1024X96 and scaled them down using the editor. I have the applications default resolution set up for 800X600 windowed and the user can resize the game window.

I cannot seem to recreate the problem using the editor or a release on my local machine. He said it worked fine on his Windows 7 Machine, though he said the text looked blurry. Any thoughts?

Screen Tearing Example

\$\endgroup\$

closed as off-topic by Josh Dec 22 '14 at 19:31

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions about debugging a problem in your project must present a concise selection of code and context so as to allow a reader to diagnose the issue without needing to read all of your code or to engage in extensive back-and-forth dialog. For more information, see this meta thread." – Josh
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    \$\begingroup\$ That looks more like corruption than "tearing" which could be due to a driver or even physical hardware problems. Updating drivers might fix the problem. \$\endgroup\$ – MooseBoys Nov 26 '14 at 18:33
  • \$\begingroup\$ @MooseBoys, corruption does sound better than "tearing" - I couldn't think of a better way of describing it. Let me talk to my client about updating the drivers. THANKS, for the feedback! \$\endgroup\$ – OverCodingUnderSleeping Nov 26 '14 at 18:56
  • \$\begingroup\$ I am going to try to scale the images so that they are less than 800 PX wide and release again. I figure there might be some logic error occurring involving the aspect ratio that the XP machine is running on. It is odd that these graphics are the only ones that are corrupted... \$\endgroup\$ – OverCodingUnderSleeping Nov 27 '14 at 19:04
0
\$\begingroup\$

It seems that scaling the images for the buttons from 1024X96 to 798X75 while targeting a default resolution of 800X600 solved the graphics corruption. I wish I knew why this was the case, but I will take a win any day. Thanks to all who have contributed.

\$\endgroup\$

Not the answer you're looking for? Browse other questions tagged or ask your own question.