Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Entitas 1.4.2: Visual Debugging does not work properly at Unity 2017.3.1

See original GitHub issue

@sschmid It throws me this error when I select the system game object to see the system debugging message and the time of Execute systems all become red.

KeyNotFoundException: The given key was not present in the dictionary.
System.ThrowHelper.ThrowKeyNotFoundException () (at <c95265f74fdf4905bfb0d5a4b652216c>:0)
System.Collections.Generic.Dictionary`2[TKey,TValue].get_Item (TKey key) (at <c95265f74fdf4905bfb0d5a4b652216c>:0)
DesperateDevs.Serialization.Properties.get_Item (System.String key) (at <099e51ab2dc047729b0674a5e3327d54>:0)
DesperateDevs.Serialization.Preferences.get_Item (System.String key) (at <099e51ab2dc047729b0674a5e3327d54>:0)
Entitas.VisualDebugging.Unity.Editor.VisualDebuggingConfig.get_systemWarningThreshold () (at <208de3a2d6014ccb96680dd370edf0de>:0)
Entitas.VisualDebugging.Unity.Editor.DebugSystemsInspector.OnEnable () (at <208de3a2d6014ccb96680dd370edf0de>:0)

Issue Analytics

State:
Created 6 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

sschmidcommented, Mar 13, 2018

When you open the Preferences, Entitas will automatically add missing keys. Make sure your properties contain these keys

Entitas.VisualDebugging.Unity.Editor.SystemWarningThreshold = 5
Entitas.VisualDebugging.Unity.Editor.DefaultInstanceCreatorFolderPath = Assets/Editor/DefaultInstanceCreator
Entitas.VisualDebugging.Unity.Editor.TypeDrawerFolderPath = Assets/Editor/TypeDrawer

0reactions

optimisezcommented, Mar 13, 2018

Maybe as a workaround (just guessing) add those keys also to the roslyn properties, maybe that helps

@sschmid Ya. Problem fixed after adding those keys to roslyn properties. I guess it still read roslyn properties file instead of UnityPreferences properties file.

Top Results From Across the Web

Entitas 1.4.2: Visual Debugging does not work properly at ...

I am using Windows 7 + Unity 2017.3.1p2 + Entitas 1.4.2. It is working fine.

Question - Unity freezes on Debugging with Visual Studio

Another possible option is try deleting the solution files and letting Unity regenerate them. Also make sure that VS is listed under preferences ......

Troubleshooting and known issues (VS Tools for Unity)

Read about troubleshooting in Visual Studio Tools for Unity. See descriptions of known issues, and learn about solutions to those issues.

Manual: Debug C# code in Unity

Most problems with the debugger occur because the code editor is unable to locate the Unity Editor or the Unity Player. This means...

Visual Studio loses ability to attach to Unity, why?

Reopen project with unity hub, edit one of script and all files will be generated and you will see Attach to Unity button...