Search Issue Tracker
Won't Fix
Votes
2
Found in
5.3.0f4
Issue ID
754167
Regression
Yes
{OSX}Event.current.use() causes error when used in OnDrawGizmosSelected() method.
Reproduction steps:
1) Run users project, and enter the test scene (on Mac!)
2) Selected "Select Me!" object in the hierarchy window.
3) Observe an error in the console.
"srcAttach < m_CurrentFramebuffer.colorCount && "We should always resolve only current RT""
Reproduced with: 5.3.0f4, 5.3.0f2, 5.3.0b1
Did not reproduce with: 5.2.3f1 5.2.2f1
Comments (5)
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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
dschwabe
Apr 24, 2017 17:08
Still happening in 5.5.2f1 on Mac. The suggested workaround by KELLYREYW does not work for me. I am using player settings for the camera and still see the error log.
The workaround suggested by OBOCINSKI I simply don't understand.
ina
Dec 06, 2016 07:08
This seems to also be an issue that happens with threading and linq
using System.Linq;
using System.IO;
using System.Threading;
williamian
Nov 30, 2016 23:18
I can confirm it shows up in 5.4.2f2 Personal as well.
kellyreyw
Nov 04, 2016 03:37
This suddenly started happening on my project. I was able to track down that it is happening when writing to a render target with aliasing turned on and the render path for the camera that is drawing to the render texture set to legacy. The easy fix is to set the camera to use player settings or set the render texture to not use aliasing.
Oblocinski
Feb 02, 2016 18:28
As of now there is a workaround to avoid using Repaint and Layout events (which is the cause of this issue):
if(Event.current.type != EventType.Repaint && Event.current.type != EventType.Layout) Event.current.Use();