SOLVED IT!!! (For me at least)

In case this helps anybody else out, here's what I did and it went away like magic!

I checked all my Rigidbodies, and ALL of them had Interpolation set to none, even the instantiated prefabs. So that wasn't the solution.

But then the STRANGEST thing...you know that quarky little check box that appears about "LINE ENDINGS"?? That thing that's different about MAC and Windows...apparently that was it for me.
The error appeared right from play start, so I opened my main player script for the first time on 5.6 and sure enough, the check box appeared. I hit ok, saved and poof, gone for player. But next I went in to a battle mode (mine is a indie Pokemon game) and I chose Pikachu and then it was causing the error. I exited playmode, did the same with him and poof!

So naturally I clicked on the drop down menu on Project window right next to the search bar and selected "scripts", selected all, hit enter to open fire on Visual Studio. It was a rapid succession of that silly Line Ending Windows CL..something showing up, me hitting yes. Good game.
Finally when the battles were won, I simply hit "Save All" on VS, closed it. Saved scene + project. Hit play, and the error was no more. The end :)
Again, this worked for me, the Rigidbody thing worked for other people. Worth a shot am I right?

I'm getting this error when the camera turns towards particle system objects

If you're using Steam VR, you'll need to edit line 167 on Throwable.cs

rb.interpolation = RigidbodyInterpolation.None;

Still an issue with 5.6.0f3 so this shouldn't be closed.

This is still an issue in 5.6.0f3

- Using SteamVR
- All rigidbodies interpolation set to none

Still happening in 5.6.0f3.

Not so bad in 5.6 (it was thousands and thousands in mere seconds), but still happening.

Still present for me in 5.6.0f3 Release.

Error still there in 5.6.0f3, I fixed it by setting all Rigidbody components' interpolation property to None, which is good practice anyway: https://docs.unity3d.com/ScriptReference/RigidbodyInterpolation.html

Still, the documentation suggests that Rigidbodies followed by the camera have ther interpolation set to Interpolate, which makes me wonder if the error will pop up again in that case.

Same for me on 5.6.0f3. Not a clear repro yet, no rigid bodies with interpolation so it is definitely something else.
With this issue closed, do we need to create a new one or is someone monitoring this still?

I have trouble with this too, please fix it properly!