Unity Pixel Perfect Preview Package

So currently every time we open Unity we have to change that line of code. Do you know how to make it so those changes persist in that file?

 

No clue, sorry. I imagine you'd only need to do it once for each project. You could probably just save a copy of the modified file to your assets folder and use that one directly?

 

It won't work. Can't find references to PixelPerfectCameraInternal or IPixelPerfectCamera even after including the using statements.

 

I've noticed that it makes UI elements, like buttons, very sensitive. For example, if I push down on a button, and move my finger/mouse a very small amount in any direction (but still on the button) the button doesn't stay pressed.

 

I would love a bug fix release for pixel perfect at some point for the classic render pipeline.

I'm not in a position to switch to URP yet

 

Thanks for the update!

Is that the same issue as the one I posted a little while back, here: https://forum.unity.com/threads/pixel-perfect-preview-package.533433/page-6#post-4818494 ?

Also, do you know if there's a rough ETA for 2019.3 release? I'm waiting on another major fix in that version too.

 

Great, thank you for the info.

 

Currently I'm using 2D Pixel Perfect package (preview 1.0.1) and works with classic renderer. I know that using LWRP/Universal there's the new 2D Renderer which includes 2D Pixel Perfect but that's not a solution to us since we use 3D cameras.

We've seen in the roadmap that 2019.3 includes 2D Pixel Perfect as Verified Package. The question: Is it talking about the preview package 1.0.1 that we are currently using and works with the classic renderer (and is separate of the 2D Renderer)? Or is it talking about the 2D Renderer with Pixel Perfect built-in?

 

Oh, awesome then! We were worried that focus would be on the 2D renderer, which would be a loss since the standalone package works with 3D for that PSX/Saturn era 3D look. Is there a change log available? Just curiosity, we can wait for the release

 

Actually, it's pretty straight forward. Just using the 2D Pixel Perfect Package:
- New scene
- Add a cube and rotate it to have some sides in an angle
- Add Pixel Perfect Camera to Main Camera (we are using a Unity 3D project with built-in renderer) with this settings:

- Disable antialiasing in Quality settings
- Run the scene

When using sprites they will snap to the pixels and when using 3D elements they are renderer at that reference resolution. I'll send you some examples to your private inbox.

We have noticed that Pixel Perfect Camera generates 368 B of garbage everyframe when running, created by GUIUtility.BeginGUI() as shown here:

If the Pixel Perfect Camera component is disabled, that GCAlloc disappear.

Also, when using LWRP the "Upscale render texture" option apparently doesn't work, showing 3D models in their full non-aliased glory (that's one of the reasons we are using the default renderer, the other being stacking multiple cameras)

 

All good points!
I'm using pixel perfect for a platformer with 3d backgrounds and 2d pixel art foregrounds.
I would like my 3d background to not have swimming pixels.

this asset does something similar

https://assetstore.unity.com/packages/tools/particles-effects/ferr-pixel-filter-85326

 

I also use this with 3D (and its my main reason for using this).
I generate some meshes that I want to have a pixelated look to match the rest of the game, and I've been using this package to help with that.

By the way, @yuanxing_cai, did you have time to look at that bug we talked about back in July? (https://forum.unity.com/threads/pixel-perfect-preview-package.533433/page-6#post-4607176)
I see it is still open on github

 

It gets even much worse when you use the Pixel Perfect component from the URP or LWRP package with a 2D render setup.
Even without a single light source in the scene or illumination, , disabling all lights/shadows in the URP render pipeline, and without any usage of the sprite lit material, it adds a whole bunch of GC to the pixel perfect generated GC.

Which makes you wonder if this is a sustainable path to take in production.

 

Pixel snapping which works perfectly with Non-filtered sprites and can be overriden with polygons and filtered sprites. That way we can have pixel perfect and crisp sprites when needed, but also smooth polygon movement and some smooth scaling effects and rotations when using some sprites.

I was suspecting that it was an editor only issue, thanks for clarifying.

I'm attaching at the end of this post a sample project using Unity 2019.2.10f1 and the latest version of LWRP (6.9.2 according to Package Manager) and the 1.0.1 preview of 2D Pixel Perfect (Library folder have been removed to reduce size). Open "SampleScene" and you will find the camera settings as follows:



Just hit run in Unity Editor and the cube will appear crisp and without aliasing, as if the Pixel Perfect Camera wasn't used at all, as seen here:



But, without stopping the execution of the scene, go to Project Settings -> Graphics and remove the LWRP Asset from the "Scriptable Render Pipeline Settings" field so the Default renderer is used, and the cube will instantly change to this:



Don't mind the pink color, that's because the material is for LWRP, but notice how when LWRP is disabled the pixel perfect upscaling is applied, with jagged borders on the cube corresponding to the resolution set in the Pixel Perfect Camera component.

 

second one looks more what you expect in pixel art games

 

That's the point. In the second one, once LWRP is disabled the cube is rendered using the default Unity renderer and thus the Upscale Render Texture option works correctly. With LWRP it doesn't work

 

Will the experimental 2D Renderer support camera stacking?

So I can have a 3d background with a pixel perfect foreground?

 

+1 for supporting Pixel Perfect for 3D. I recently tried to update a project to URP and 2019.3, but I was unable to get the new 2D Pixel Perfect to work with the Forward Renderer. Interestly enough, 3D objects can be rendered with the 2D Renderer(and work with Pixel Perfect), but only show up unlit.

 

I don't think I've seen anyone address this after reading through the thread and a few others trying to search it up, but I'd very much like access to the PixelCameraInternal zoom number. Or, far preferably, have the ability to set a minimum zoom level in the PixelPerfect camera. When my camera changes aspect ratio (landscape to portrait), I do not want to change pixel ratios along with it.

A bit of FOV difference across platforms and resolutions and resizeable windows is fine, but a player suddenly zoomed way out and able to see beyond the bounds of my map isn't what I'm looking for. Black bars on the sides are very much not the look I'm going for either.

Currently, I've got it handled via changing the hardcoded line 77 in PixelPerfectCameraInternal.cs from:

Code (CSharp):

1. zoom = Math.Max(1, Math.Min(verticalZoom, horizontalZoom));

to

Code (CSharp):

1. zoom = Math.Max(3, Math.Min(verticalZoom, horizontalZoom));

but obviously that's not gravy forever.

Anyway! If I've missed something somewhere, please let me know so I can use the preferred method, but I didn't see it come up. Thanks for the camera, though! I really like how much it simplifies the pain all the old solutions.