Official Pixel Perfect Preview Package

I am being Spammed with Errors in Console (Unity Ver 2018.3.7f1). The errors are for the following methods:
PixelPerfectCamera.RoundToPixel
PixelPerfectCamera.OnPreRender
PixelPerfectCamera.OnPostRender
PixelPerfectCamera.OnGUI

Setup:
I am using several UI elements and TM Pro elements as I am designing a in game Email browser using UI. In the scene there is noting except UI images and text. PP Camera comp is attached to single main camera.

When:
This doesn't happen regularly so it is difficult to pin point the cause of the error. It happens only sometimes but most of the times it works well. The last time it happened when I minimised Unity while in Play mode and after 5 minutes I maximised and the console was being spammed with errors every frame. Below is the screenshot

Image link: https://imgur.com/j1XMg94

 

I may be having the same issue. Everything is fine but when I added text to my map, upscaling destroyed the font.

 

I updated to 2019.2 and I started using the LWRP version of Pixel Perfect Camera but I'm unable to get it working with Cinemachine this time. The non-LWRP version works with an Orthographic Override script I found via the project's GitHub page.

Any pointers on this?

 

I updated to 2019.2 and when I press upscale to render texture and maximize game window. My game will appear on the bottom left and everything else black. Is this a bug?, how can I keep showing pixel perfect?

This can be solved if I increase the reference resolution, but then my character for example will show up really small. Im looking to achieve something similar to hyperlight drifter resolution

 

Hello there!

Is there any update on the zooming feature? The code changed a bit since the solution you mentioned a few pages back, any idea how to implement this in a simple way?

Thanks for reading.

 

It was a problem with post-process effect I only moved the script up for the post effect volume in the game oobject menu and it solved the problem

 

Is it possible this issue could be fixed in a future version? https://forum.unity.com/threads/pixel-perfect-preview-package.533433/page-4#post-4032814

 

Can someone try to get sprite masks to work when stretch fill is disabled on the pixel perfect camera? It's a bug and I filed a report but they keep ignoring it for months because I won't send in my personal project.

 

@yuanxing_cai hey, it seems the Pixel Perfect package is no longer in packages.unity.com. Was it deprecated for good now?

 

Hi @yuanxing_cai - I've put together a simple package that shows a few issues I've encountered with the pixel perfect camera when the camera is at a subpixel position. In this example, I have PPU set to 100, and the camera animating with a toggle between (0,0) and (0.005, 0.005). To be fair, some of these are just general subpixel position issues, but the ppc performs a lot better on sprites than it does on UI elements. I am mainly interested in improving UI rendering.



There seem to be two main issues:

1. Sprites with odd-numbered widths or heights will be distorted. The fix to this seems to be to put sprites on even-sized canvases, and set Mesh Type to Full Rect, since otherwise the mesh could still be odd-sized. Unfortunately this increases overdraw, but I can live with that.
2. Sprites which run up to the edge of their canvas will be stretched or clipped along those edges. The fix I've used to avoid this is to give sprites a 1px border of transparent canvas space on all edges.

Putting sprites on an atlas can help, since atlases are always POT textures, but issue #2 can still occur with atlased sprites, and padding doesn't seem to help. These issues also have implications for fonts, because individual character meshes are not guaranteed to be the same size (unless maybe you're using a monospace font). It's not so easy to perform the above fixes on a character-by-character basis, so I'm hoping for some solution to font rendering.

EDIT: I had a few more thoughts. The UI issues mainly seem to occur when setting the canvas to Screen Space - Camera. By design, when the camera is moved, the canvas position is also moved to follow the camera. So, when a camera is at (0.005, 0.005) for example, the canvas will also end up at a subpixel position. PixelPerfectCamera calls PixelSnap() which in turn uses m_Camera.worldToCameraMatrix to override the camera's rendering position, so that it uses the rounded values instead of the camera's actual transform. I'm assuming this was done to avoid the issues you typically get when directly setting an object's transform (smoothness/jitter). However, the transform is still at a subpixel position, so other things that use the camera's transform will have issues.

Some solutions might include a) provide a new canvas render mode that behaves like Screen Space - Camera except it uses rounded values or b) set canvas render mode to World Space and update the canvas position manually, using the pixel-rounded camera's transform (in other words, create our own script that does the same thing option a would). Note that in my case at least, Screen Space - Overlay is not an option, since then camera post-processing effects won't be applied to the UI. Would appreciate hearing any thoughts you have on this issue!

 

I have another small request if possible.

It seems like even with the upscaled render texture option there's some amount of pixel "snapping" going on. Due to transform hierarchy and rotations in our game the resulting position can end up being + or - some really tiny delta (like 0.0001 territory) but that's enough to cause the pixel to "snap" back and forward between positions, giving it really bad visual jitter.

As far as I can tell if you're already rendering at a low resolution and upscaling, the lower resolution rendering should basically have some "built-in" level of pixel rounding which doesn't necessarily require the algorithmic snapping.

I've commented out this line in PixelPerfectCamera::OnPreRender

Code (CSharp):

1. Experimental.U2D.PixelPerfectRendering.pixelSnapSpacing = m_Internal.unitsPerPixel;

That stops the snap jitter, and doesn't appear to otherwise do much to affect the pixel rendering/quality in our project.

Is it possible to either have an option to disable the pixel snapping entirely if we're using the upscaled render texture, or potentially a way to add some kind of epsilon to the snapping so that the tiniest transform calculation errors aren't enough to cause a sprite to jump to an entirely different pixel?

If this has been addressed in the newer 2019.2/LWRP versions then awesome! We're still on the 1.0.1 preview.

Thanks again for the package though, it's otherwise great.

 

Is there a way to have the pixel perfect camera be upscaled, while using a seperate camera for UI that is full resolution? Seems right now they both get rendered as low resolution.

 

I'd like to just add a +1 to UI support. To get a game looking pixel perfect and nice and sharp, EVERYTHING needs to look uniform. If anything doesn't conform to the resolution it sticks out like a sore thumb, or it just looks 'off' somehow. I would love a solution for UI that's as easy as the regular sprite renderers

 

Hey folks, I just started getting this error the first time I hit Play in editor. After that everything works fine.

NullReferenceException: Object reference not set to an instance of an object

UnityEngine.U2D.PixelPerfectCamera.PixelSnap () (at Library/PackageCache/com.unity.2d.pixel-perfect@1.0.1-preview/Runtime/PixelPerfectCamera.cs:111)

UnityEngine.U2D.PixelPerfectCamera.OnPreCull () (at Library/PackageCache/com.unity.2d.pixel-perfect@1.0.1-preview/Runtime/PixelPerfectCamera.cs:151)

I'm using the latest version of pixel perfect (1.0.1) and Unity 2019.1.10f1.


Also... I also noticed that my screen shake behaviour from the Pro Camera 2D plugin has changed even though the values have remained the same -- camera shake seems more violent now. No idea why this has suddenly changed or if it's related to the error above, but I noticed it around the same time as this error appeared. *shrug*

 

Thanks for the info! For the record, what I ended up doing is using a world space canvas, and updating the position manually using the camera's pixel-snapped positions.

 

Thanks for the update and the patch @yuanxing_cai ! I tried overwriting the script in my project but unfortunately I still get the error.

 

First time I hit Play after I launch Unity. If I stop then play again, no error. If I quit Unity, restart and hit play, I get the error again, first time only.

It's an existing project from January and Pixel Perfect has been in there pretty much since day 1. Never had this problem until about a week ago... I think around when I upgraded Unity to 2019.1.12 although I'm not 100% certain. I was on 2019.1.10 before that.

 

Another thing I've discovered this weekend: Raycast2D gives wildly inaccurate results if you're using Pixel Perfect. It seems like the raycast position is scaled by some value? I can't figure out what.

I'm using 2019.2 for this project. Found out the hard way half way through the Game Maker's Toolkit game jam that my 2D sniper game is going to be a lot of hard work and debugging :/

If anyone has a quick solution they can help me out with ASAP I'd be really grateful. Right now I'm totally stumped with about 28 hours to go for the jam.

Vector2 rayStart = Camera.main.ScreenToWorldPoint(Input.mousePosition);

RaycastHit2D hit = Physics2D.Raycast(rayStart, Vector2.zero, 0f, charLayer);

My raycast attempts all seem to fire in a rect that's about 5 times the size of my actual camera viewport.

 

Something that would be nice is a toggle to choose whether to display the GUI warnings in editor for invalid resolutions, etc. I'm working on a side project that has a base resolution with an odd height, and every time I open the project I have to comment out lines 234-243 of the main script. I guess Unity stores the package inside Library instead of Assets, and reverts any changes on startup.

 

Hi,

Is there a way to use "don't clear" when upscaling the render texture (ie keep it transparent)?

In my game, I don't want the whole game to be upscaled because I need smoother scrolling (snapped to the screen's pixels, not the pixelart pixels), but I want to upscale certain cameras that render layers with particle effects, to make them the same resolution as the pixel art....

So basically, I want to use the upscale feature on certain cameras, but when I do that, they hide the cameras behind them.

 

For this project I'm using the LWRP one.

 

Wonderful, thank you @yuanxing_cai ! Please keep us posted with any updates in this thread. I'd love to bring Pixel Perfect back into this project if I can.

 

Hi,

I've been working with the pixel perfect preview package, and for the most part I'm happy with it.

Just today, I was exploring putting a minimap in my game. I was roughly following this guide https://blog.theknightsofunity.com/implementing-minimap-unity/ that suggests using a Render Texture.

It sort of worked, but I got a warning in the console:

Render to texture is not supported by Pixel Perfect Camera.

UnityEngine.U2D.PixelPerfectCamera:Awake()

It seems that the Pixel Perfect camera doesn't support this. I do notice it isn't pixel perfect as the minimap camera moves.

Are there any suggestions you have right now for doing a pixel perfect minimap?

 

Hi @yuanxing_cai , thanks for the reply.

When you say the Universal RP version, is that the one in the Lightweight RP package? I could still see that warning in version 6.9.1. Are you talking about an upcoming update?

 

@yuanxing_cai would you be able to tell me when it's likely to be available. I'm trying to decide whether or not to include a minimap in my game which is only a few months away from completion.

Alternatively, is there any code I could use now?

 

Ah, you are awesome. Thanks alot @yuanxing_cai

 

Hey @yuanxing_cai , I thought I would share how it went. I took those changes and applied them to a copy of the old pixel perfect package's camera script, and the result is pretty good. Thanks for your help again.

Before and after ^^^

 

This issue (Using 2D Renderer (Experimental) in an LWRP Asset causes UI/mouse events to become inaccurate) has been plaguing our team for weeks. Today I made as minimal of an example project as possible demonstrating the issue. I hope it is fixed swiftly!
https://fogbugz.unity3d.com/default.asp?1180324_ps8f9sl6ob2ns5r8

 

I managed to solve this, I posted a fix here: https://issuetracker.unity3d.com/is...-y-makes-it-difficult-to-click-on-ui-elements

 

Thank you! That's an issue I opened as well. I opened at least 4 about this.
I'll try your fix!