even though the script pointer is in the error description
Unity.Collections.NativeArray`1[T].Copy (T[ ] src, Unity.Collections.NativeArray`1[T] dst) (at <bad59441812943c7b8d5a5ba85795810>:0)
Unity.Collections.NativeArray`1[T].CopyFrom (T[ ] array) (at <bad59441812943c7b8d5a5ba85795810>:0)
BlissManagerOld.UpdateBlissTexture (System.Boolean force) (at Assets/BlissManagerOld.cs:280)
BlissManagerOld.Update () (at Assets/BlissManagerOld.cs:333)
+1
Been bitten by this one myself. It seems like since the console added the ability to click on the stack trace to go to the source (a good addition), it’s broken the console’s ability to go somewhere reasonable when you double click on the message.
I’ve noticed that if the top of the stack is in native code, it doesn’t try and take you to the uppermost C# line, but instead does nothing. The above is a perfect example of this – the top trace on the stack is a pointer to native code. If the top-most trace points to C# code, then double-clicking works.
QA couldn’t reproduce so we’re thinking there is another condition.
what do your errors look like?
Next time I run into a case that causes this, I will post the full stack trace here.
