Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0b3
Issue ID
989608
Regression
No
Discrepancy between render texture and camera dimensions
Steps to reproduce:
1. Open user attached project
2. Switch to 16:9 aspect ratio
3. "SetPixels32 called with invalid number of pixels in the array UnityEngine.Texture2D:SetPixels32(Color32[])" error will occur at this point, if it doesn't, change to other aspect ratios or increase/decrease the size of the game view
Expected result: "SetPixels32 called with invalid number of pixels in the array UnityEngine.Texture2D:SetPixels32(Color32[])" should not occur
Reproduced in: 2018.2.0a1, 2018.1.0b4, 2018.1.0a1
Fixed in: 2018.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment