Latest release candidate + latest V2 Post from github = bug!

Huge colour wheels and error log spam.

ReflectionTypeLoadException: The classes in the module cannot be loaded.
System.Reflection.Assembly.GetTypes () (at <9c9f068c46c64ffd91fda7af157b4d15>:0)
UnityEditor.Rendering.PostProcessing.EffectListEditor.<Init>m__0 (System.Reflection.Assembly a) (at Assets/Plugins/PostProcessing/Editor/EffectListEditor.cs:43)
System.Linq.Enumerable+SelectManySingleSelectorIterator`2[TSource,TResult].ToList () (at <11c1c8f1ba1046b191f565f88728429e>:0)
System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <11c1c8f1ba1046b191f565f88728429e>:0)
UnityEditor.Rendering.PostProcessing.EffectListEditor.Init (UnityEngine.Rendering.PostProcessing.PostProcessProfile asset, UnityEditor.SerializedObject serializedObject) (at Assets/Plugins/PostProcessing/Editor/EffectListEditor.cs:48)
UnityEditor.Rendering.PostProcessing.PostProcessProfileEditor.OnEnable () (at Assets/Plugins/PostProcessing/Editor/PostProcessProfileEditor.cs:13)

Known issue?

2 Likes

Don’t have time to post a bug report number sorry :frowning: Wish I did.

Problem was with .NET 4.6 Equivalent sctipting Runtime Version. Selecting 3.5 makes all the pain go away.

3231022--247967--upload_2017-9-23_15-32-0.png

We’ll have a look at this. To be clear, are you using the code from GitHub - Unity-Technologies/PostProcessing: Post Processing Stack?

Yep!

1 Like

@hippocoder How do I get to the screen from the original screenshot? I’m trying to repro it, but I’m not an expert in the post processing. I was trying the Color Grading at Post-Processing Profile (from Create > Post-processing profile), but it didn’t show the issue.

Just click the newly created V2 post processing profile. In it’s non buggy state it looks like this:

Of course you will have to add all the effects one by one. If you guys are still coming up blank I’ll get a repro going sometime in the week.

@hippocoder Neither I nor the guys who develop the post-processing were able to reproduce the issue. So it is not a straightforward thing.
If you still encounter it, we’ll greatly appreciate if you’ll submit a bug report with repro steps.