Search Issue Tracker
Fixed in 5.0.X
Votes
27
Found in
4.1.2f1
Issue ID
542949
Regression
No
!dest.m_MultiFrameGUIState.m_NamedKeyControlList when pressing any key
Steps to reproduce :
- import the project attached
- open the scene cheat-menu
- press play and start typing on the keyboard
- notice the errors in the console
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
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
Marble
May 23, 2015 18:23
Still an issue in 5.0.2.
theSoenke
Apr 19, 2015 13:11
Still not fixed in 5.0.1p1
Smileysmiles
Mar 04, 2015 22:23
Yep this is getting old real fast.
twobob
Feb 21, 2015 16:36
EDIT: Restarting the editor has made the errors go away. Will keep an eye on it.
twobob
Feb 21, 2015 16:24
4.6.3f1 regression
Just started happening again. After upgrade today.
FVANtom
Feb 12, 2015 15:43
Error is still present in 5.0.0b18
Samuraisa
Dec 08, 2014 12:43
4.6.0 f3
The same problem. Occurs when "Game" editor window is separated from the main editor window.
nlafarge
Nov 20, 2014 23:24
This issue is *not* resolved - I'm still having the issue in 4.5.5f1
clowncrew-bernie
Nov 19, 2014 16:56
This error occurs when when I use the new scrollrect in Unity 4.6 RC 1 and Unity 4.6 RC 2. When I move my scrollable text the console gets 35 to 40 log entries with this error - per second.
I wish I understood what this error actually means and how to avoid it since this error seems forgotten by the Unity devs.
In forum discussion about this error some claim this bug is nothing more then an annoyance. I disagree. Performance suffers and for anyone logging errors ... well. It raises the question if it is possible to log unhandled exceptions in Unity at all? Warning can be ignore, but errors? What Unity dev thought it is okay to throw an error if something is "annoying"?
If there is no time to solve this issue - then at the very least change this to a warning! That got to be a 2 minute hack, tops.
LSPressWorks
Sep 12, 2014 07:48
No idea where dude learned about the OnGUI dummy thing but it did the trick. Once this error was triggered in the highscores scene, it would randomly pop up in game and DESTROY performance. This isn't fixed. Any chance you devs could take a second look?