Hi, I have an error that I cant seem to fix or find the cause and doesnt seem to always appear but doesnt seem to do anything weird when I run it in the editor.
Hi, Iâm having the same problem; when I start to get that error in the console my character starts falling through the ground and gets lost to infinityâŚ
Do you get any other odd behaviour in your game when you start to get those messages ? And⌠did you find a solution the the problem ?
I also filed a bug report to Unity but with no feedback.
Maybe if we exchange some info we can understand what is generating this problemâŚ
I donât know what you mean bytoo far away⌠The problem seems to happen only when the character moves on the Z axys and passes value 142 (more or less).
No odd behaviour when you move along the X axys (values 0 to 296).
The weird thing is that it seems that the whole physics system gets screwed up: I tried to place another plane with a collider below my normal playfield and the character falls through. It seems that from the moment you start getting those messages any collision is ignoredâŚ
I also have this problem. The error messages come in such vast quantities that the frame rate drops to about 10 FPS. It starts as soon as the scene is loaded (camera is in a fixed position staring at a wall with a few GUI options). We have no negative or infinite particle settingsâŚand none of the stack traces lead back to any of our scripts.
EDIT: Update, this also continues to happen after we have stopped playing the scene and are just looking into the editor.
FUTHER EDIT: Oh, changing the depth of the camera from -1 to 0 fixed the errors in editor mode, and we found the culprit for the others. Donât quite know the reason yet (something is bad about this piece of geometry since it also gaves invalidAABB errors) but will post more info later.
hi - iâm getting a constant console spam of this error message when using TextMesh (3D Text)
!IsFinite(outDistanceForSort)
!IsFinite(outDistanceAlongView)
UnityEditor.DockArea:OnGUI()
This problem with 3D text has been logged in a bug report. However, in the meantime, you may be able to fix it by using Unicode for the Character setting in the font importer and/or changing the font size from the importer rather than the TextMesh component.
Thatâs really not a good solution. I may be using that font at various sizes throughout the application and you donât want to have a texture specific to each size. That begins to eat up memory and inflate your gameâs size on disk, which can be a real problem for iOS apps trying to stay under 20mb. You generally want to make one texture, thatâs big enough so that the highest font size usage still looks good.
In our case the culprit was the ârich textâ checkbox of Text component (Unity >=5) using dynamic font, disabling it stopped these errors to appear.
In our case it was caused by a rect UV of (0,0,1,-1) on a RawImage, changing it to (0,0,1,1) (and flipping the texture externally) stopped the errors (thousands of them per frame).
Iâm in a project which has no text whatsoever, and get the errors isFinite(d), isFinite(outDistanceAlongView), isFinite(outDistanceForSort). They pop up when an instantiated rocket-prefab collides with a terrain object tagged âGroundâ, resulting in an instantiation of an explosion-particlesystem-prefab, and then Destroy() on the rocket.
Stuffing a small Destroy() script on the particlesystem stops the errors occurring as soon as the systemâs removed. Just wanted to add that to the list here, since nobody seems toâve bumped into it with a particlesystem