Closed Arakade closed 8 years ago
This looks fixable on my end. It looks the the crash is happening while fiSettings
is probing for any fiSettingsProcessors
. I'll get to it soonish, though it might take a bit longer to push out the trial update (currently it's pretty painful to the update the trial - I'm not sure of a good way to automate it).
This should be fixed and will be included in the next FI trial / update.
Great that you've fixed it :) Just checked and the trail seems unchanged (by MD5). Understand it's low priority -- NP -- roughly when do you think I might retry to confirm? Thanks.
Can you send me an email? Thanks.
Hi, I installed the FullInspector trial to evaluate it for Dictionary serialization. It's doing that part of the job brilliantly (I'm using and loving the Generics-based approach). However I also occasionally get a spurious error.
System.TypeInitializationException: An exception was thrown by the type initializer for FullInspector.fiSettings ---> System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded.
(and)System.TypeInitializationException: An exception was thrown by the type initializer for FullInspector.Internal.fiInstalledSerializerManager ---> System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded.
(full details below)I say spurious because restarting Unity resolves it. I wasn't having the issue before FI integration. FI appears in the errors. For these reasons, I suspect it is causal but I haven't determined why yet. I've only seen the error when starting Unity having uncompiled changes in my source. Unity shows its compiling and importing scripts dialogs then (erroneously) asks whether to load the default layout (the first indication that a compilation error has occurred). I know there isn't one because (a) I compiled successfully in Visual Studio, (b) looking through the errors, they aren't compilation ones and (c) restarting Unity shows it's all fine.
Unity 5.1.2f Indie on Windows 8.1
I've extracted log message below -- it contains tonnes of (A), a few (B) (BehaviorDesigner being one of many other assets in this project) then (C) which implicates Full Inspector. After these are the messages about loading a different layout.
Obviously the workaround is not to modify source while Unity isn't loaded but that's (a) not really viable for a multi-person version-control using team and (b) annoying to remember as a one-man!
Any thoughts on resolving would be greatly appreciated. Rupert.
A:
B:
C: