Reasons for -1.#IND ?

This forum is currently in read-only mode.

Replies Disabled

❤Follow Topic(3)

0 favourites

4 posts

From the Asset Store

Cross The Bridge

$19 USD

In this fun game you must try to complete the path for the car to pass before time runs out, agility and reasoning are a

R Games

- dkdoom
- - Joined 6 Dec, 2008
  - 24 topics • 171 posts
- 1
- 25 Mar, 2009
- Quote
hi,

i am wondering about the possible ways to (inadvertendly) set a private variable to -1.#IND (undefined, i presume). i've got some simple TimeDelta-related math in a project, and it occasionally results in objects becoming invisible when their angle property is being calculated as -1.#IND

since the math is really simple, i've got no idea where to start looking. does somebody know the possible causes of this error?

( the cap is here. click & drag to scratch. occasionally bugs out, especially in debug mode & with unlimited framerate )
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,392 posts
- 1
- 25 Mar, 2009
- Quote
It means you've done something mathematically impossible. Like divide by zero, take the square root of a negative number, et cetera. The object disappears if the angle, width, height, x or y is this value, because it is impossible to determine how to render the object.
- dkdoom
- - Joined 6 Dec, 2008
  - 24 topics • 171 posts
- 1
- 25 Mar, 2009
- Quote
superfast! thank you very much! i'm guessing it is divide by zero, i'll have a close look.
- jessejohhavoc
- - Joined 26 Feb, 2009
  - 5 topics • 36 posts
- 1
- 26 Mar, 2009
- Quote
A good way to fix a divide by zero is to ensure that the number you are dividing by is over 0 before performing the arithmetic operation by inserting a condition "Value to divide by > 0". This might be common sense, but this is a note for anyone else that gets stuck on this and can't figure it out.