!dest.m_MultiFrameGUIState.m_NamedKeyControlList

Unity Engine
1

I am getting these errors randomly when enabling or disabling scripts or some gadgets(camera, gui layer, flare layer ect.)

Is this a unity 4 bug, or is there something wrong with the code that does not show as warrning? :expressionless:

2

I’ve just got the same bug, it reproduced everytime.

I have a custom editor, and i have an object property on it, here is a part of code

UFTAtlasMetadata newMeta= (UFTAtlasMetadata) EditorGUILayout.ObjectField((Object)atlasMetadata,typeof(UFTAtlasMetadata),false);

So, when i open this editor, choose this object, new window appeared (where i can choose any UFTAtlasMetadata from my assets), and when i switch back to the scene editor (without closing object chooser dialog) i’m getting this error.

Also i found, that it happens only if editor is docked to the unity application, if it is a floating window, this error doesn’t appeared.

Submitted this bug to unity.

1 Like
3

yep, i am getting this too

4

I was having this too, but it just desapeared by itself after a while.

5

Anyone find a solution for this?

Thanks :slight_smile:

6

Same here

7

got this after I remapped some controls

8

i get this every time i press a keyboard button.

9

I had this bug too.
I noticed it doesn’t happen during the part of my game when I have some GUI Labels on the screen.
So I added a dummy Label to my scene and the error message never shows any more.
Hope this helps the developers nail down the bug.

10

Oops, looks like this slipped through the net. We’ve seen it internally too, and in my experience it doesn’t do any harm other than being very annoying.

11

yes. it only is annoying on my end.

12

I got it too in Unity 4.0.0f7

13

I have this problem to. No GUI on the screen and it happens when I do a raytrace to detect a hit on a object.

14

same problem when I use GUI.SetNextControlName…

15

That’s great except when you’re hooking Unity’s error handling via RegisterLogCallback in order to print error messages to the screen - in which case it pops up immediately. Is there any workaround or reliable reproduction notes for this?

16

Best I can do after a bit of messing about is - it seems to be related to calling SetActive(bool) on the GameObject containing the GUI code. However - the result is different depending on the context.

  • Disable GUI object in Start() of another object: error happens immediately
  • Same but yield a frame in Start(): same result
  • Disable GUI object in Update() of another object: error happens immediately
  • Disable GUI object via Inspector: error happens immediately
  • Disable GUI object via non-MonoBehaviour code later in game’s lifecycle: works until you strike a key on the keyboard then error occurs
1 Like
17

I had the same issue with calling GUI.SetNextControlName. I made it to go away (so far…) by removing the script that had this call in it, and then adding it back into my scene. I do not know why this worked, but it has so far.

Hope it helps you as it did me!

~Tim

EDIT: It has come back, so this workaround didn’t work. :cry:

18

So has this been fixed yet?

19

I am not even using Unity Gui at all in my app - but i added a plugin from the unity asset store that does, then I moved the script with that plugin to a different (not the ‘title’ scene where I had first put it) and now in the title scene only I get these messages every time I click anywhere on the title screen.

I"ve never run into this before today because I’ve been using EZGui.

just passing this along if it helps.

20

Oddly enough, the next time I saved my project to asset server, then shut down Unity (don’t really know if shutting it down makes a difference) - the next day these dumb messages were gone.