Search Issue Tracker
By Design
Votes
1
Found in [Package]
4.0.1
Issue ID
1276037
Regression
No
[Pixel Perfect] Pixels are uneven when using different resolution than Pixel Perfect Component's Reference Resolution
How to reproduce:
1. Open attached "case1270952_NotPixelPerfect" project
2. Open Assets/Scenes/Sample Scene
3. Enter Play Mode
4. Open the Game View window
5. Set the screen resolution to 640x360
6 Observe the sprite in the Game View window
Expected result: All pixels are the same size
Actual result: Some pixels are smaller than the others
Reproducible with: 2.0.4(2019.4.8f1), 3.0.2(2020.1.4f1), 4.0.1(2020.2.0b1)
Can't test: 2018.4 (errors when importing the package)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blend Tree Slider does not adapt if outside allowed range on change of Threshold values
- Mesh Rendered GameObject using the SpriteLitDefault Material becomes invisible when animating with the URP Sprite-Lit-Default Shader
- Compilation errors occur when using PluginAPI headers in a C environment
- Profiler connects to a different opened Editor project when more than one project is open and building for WebGL with Autoconnect Profiler enabled
- Creating and then deleting the "Integration Update: Rotation" block breaks and makes unusable VFX Graph
Resolution Note:
There are two issues with how the repro project is set up:
1. The Pixel Perfect Camera in URP works only with the 2D Renderer, not the Forward Renderer.
2. Pixel Perfect Camera only supports orthographic camera, not perspective camera.