Home   Help Search Login Register  

Author Topic: BoundingBox  (Read 1157 times)

0 Members and 1 Guest are viewing this topic.

Offline Mr.Peanut

  • Former Staff
  • ****
  • urp!
BoundingBox
« on: 06 Jun 2007, 03:24:56 »
BoundingBox. It conjures up images of a vast plain where the boxes roam wild and free.

For some reason the following does not work:
Code: [Select]
_unit = _this select 0;
_bar = nearestObjects[_unit,["STATIC"],20];
for [{_j = 0},{_j < count _bar},{_j = _j + 1}] do
{
   _c = boundingBox (_bar select j);
   hint format ["%1\n%2",(_bar select _j), _c];
   sleep 5;
};

_c comes out as a null array. Any suggestions?   
urp!

Offline h-

  • OFPEC Site
  • Administrator
  • *****
  • Formerly HateR_Kint
    • OFPEC
Re: BoundingBox
« Reply #1 on: 06 Jun 2007, 18:53:27 »
You have not spotted it yet?

I'll give you a hint:
Quote
_
;)
Project MCAR   ---   Northern Fronts   ---   Emitter 3Ditor
INFORMATIVE THREAD TITLES PLEASE. "PLEASE HELP" IS NOT ONE..
Chuck Norris can divide by zero.

Offline Mr.Peanut

  • Former Staff
  • ****
  • urp!
Re: BoundingBox
« Reply #2 on: 06 Jun 2007, 19:07:15 »
oops, better delete my post in BIS forums before it makes me look even more the idiot....  :shhh:
« Last Edit: 06 Jun 2007, 19:12:46 by Mr.Peanut »
urp!

Offline Mandoble

  • Former Staff
  • ****
    • Grunt ONE and MandoMissile suite
Re: BoundingBox
« Reply #3 on: 06 Jun 2007, 19:13:24 »
LOL

Offline h-

  • OFPEC Site
  • Administrator
  • *****
  • Formerly HateR_Kint
    • OFPEC
Re: BoundingBox
« Reply #4 on: 06 Jun 2007, 19:54:06 »
 :D :D

That happens a lot, especially when you are coding long and complex sets..
Sometimes, although very rarely, a typo causes no immediate visible problems and you only spot when you go over the code not having touched it (the code) in weeks..
Project MCAR   ---   Northern Fronts   ---   Emitter 3Ditor
INFORMATIVE THREAD TITLES PLEASE. "PLEASE HELP" IS NOT ONE..
Chuck Norris can divide by zero.