fibanocci on 1/8/2015 at 16:14
This is the error I get now and then. In some areas more often than in others.
Quote:
ASSERT: [PHMOD.CPP@879] !_isnan(locVec.x) && !_isnan(locVec.y) && !_isnan(locVec.z)
I saw an old thread with this topic
(
http://www.ttlg.com/forums/showthread.php?t=51923)
That error is said to have something to do with ropes and moving terrain.
So I deleted all ropes and moving terrains.
But the error still remains. What else could cause that isnan-error?
R Soul on 1/8/2015 at 22:25
Do you have a custom script object or receptron setting property values?
Also, try rebuilding the pathfinding database after deleting the lift.
Yandros on 2/8/2015 at 02:46
Not sure how to help, but I will surmise that "Isnan" stands for "Is not a number".
fibanocci on 2/8/2015 at 12:31
Quote Posted by R Soul
Do you have a custom script object or receptron setting property values?
Just some teleportations and tweq activations via receptrons. I deleted it all for testing.
Quote:
Also, try rebuilding the pathfinding database after deleting the lift.
Always
I've deleted about 700 objects in a certain area. I realized, the faulty object must be in this area, since the error went away.
The isnan-error only occurs, if I frob something in a completely different area that has nothing to do with the other area. It's like searching the needle in a haystack.
Quote Posted by Yandros
Not sure how to help, but I will surmise that "Isnan" stands for "Is not a number".
This has been assumed here
Quote Posted by xarax
the function isnan() appears to be testing for an IEEE floating point "NOT A NUMBER" condition. the expression is testing the co-ordinates X,Y,Z to determine whether all of the values are valid floating point numbers.
since we know that grid snapping resolves a great many sins regarding floating point rounding errors, we should ask whether all brushes have been correctly snapped to the grid.
search the forum for grid snap for more details on the issue of proper brush snapping.
But I don't know what that means. Everything is snapped to the grid. I wish the monolog was more specific.
LarryG on 2/8/2015 at 14:57
Quote Posted by fibanocci
I've deleted about 700 objects in a certain area. I realized, the faulty object must be in this area, since the error went away.
The isnan-error only occurs, if I frob something in a completely different area that has nothing to do with the other area. It's like searching the needle in a haystack.
Either keep going the way you are by sub-dividing and re-subdividing that area and deleting pieces until you have narrowed it down to the smallest area you can which when you delete it the problem goes away, and then carefully rebuild that small area, or go back to a save where it doesn't happen and compare that to the next save where it does to get a clue about the issue.
fibanocci on 3/8/2015 at 18:35
Looks like I found the problem (at least I hope so). I used 2 models that are rather bad.
1. A skeleton by sluggs (Toxicman)
2. A rat that I made
LarryG on 3/8/2015 at 20:45
Well, sheesh! Use my skeletons and my rat. They are both mission proven and gluten free. :cool:
