I keep having the odd particle with speeds of
-1.#IND
and
1.#INF
that keep nodes from cooking properly. How do I deal with these freaks? I tried an if() expression but to no use.
-1.#IND and 1.#INF
3008 4 0- Soothsayer
- Member
- 861 posts
- Joined: Oct. 2008
- Offline
- edward
- Member
- 7724 posts
- Joined: July 2005
- Offline
- Soothsayer
- Member
- 861 posts
- Joined: Oct. 2008
- Offline
I thought so too but it comes right from a standard attribute as far as I can work out and I'm a bit puzzled by the “1.” which made me wonder if it is only the decimal expansion that's infinite, which would be kind of strange.
I thought there might be an expression that handles exceptions and errors, but yep I better keep searching for things that attempt strange divisions.
I thought there might be an expression that handles exceptions and errors, but yep I better keep searching for things that attempt strange divisions.
--
Jobless
Jobless
- mark
- Staff
- 2592 posts
- Joined: July 2005
- Offline
SoothsayerYou may also get these numbers if you are doing things like taking the square root of a negative number, creating a number which is too large to represent (i.e. exp(1000)), or doing other bad math things (i.e. pow(-3.5, 1.7))
I thought so too but it comes right from a standard attribute as far as I can work out and I'm a bit puzzled by the “1.” which made me wonder if it is only the decimal expansion that's infinite, which would be kind of strange.
I thought there might be an expression that handles exceptions and errors, but yep I better keep searching for things that attempt strange divisions.
Look at how your attributes are being created. Try disabling certain POPs/SOPs to try to find the culprit.
- Soothsayer
- Member
- 861 posts
- Joined: Oct. 2008
- Offline
-
- Quick Links