Just seen this error again in runtime. There have been all sorts of ‘did this and fixed it’ answers over the years for this error but I have not seen any source for the Actual cause of it - at least at runtime (some maths code in the Unity engine or legacy input system? - when?)
Anyone have an answer?
OK this has been moved by someone to General Graphics from scripting forum… Is this correct? Because I imagined it is a result of a scripting function call.
Does the person who moved it think it is a graphics bug?!
Is related to graphics i assume, as is in the stage of camera tranforms before rendering.
The issue still exists and i assume will never be fixed, as is so many years now.
Usually is when camera rotation approaces zero for my cases.
Moved by someone, but not answered… If the moderator is sure it is graphics related, not API call, please provide evidence