Parenting info_targets

Discussion in 'Mapping Questions & Discussion' started by oWave, Jul 11, 2016.

  1. oWave

    oWave L1: Registered

    Messages:
    10
    Positive Ratings:
    3
    I'm trying to parent info_targets around a rotating cube (using 2 func_rot_button).
    After a day of attempting to find out what's wrong, I found out that info_targets get removed when parented to something.

    Is there any way to achieve this? Since the rotation is important, phys_constraint or logic_measure_movement would probably not work (or am I completely wrong with that?)
     
    • Like Like x 1
  2. Blinx

    Blinx L69: Deviant Member

    Messages:
    69
    Positive Ratings:
    39
    Info_teleport_destination would probably work just as well.
     
  3. Crash

    aa Crash func_nerd

    Messages:
    3,191
    Positive Ratings:
    5,017
    An important question would be what you're trying to do with them. We might have a different solution than what you're trying.
     
    • Agree Agree x 1
  4. oWave

    oWave L1: Registered

    Messages:
    10
    Positive Ratings:
    3
    I'm in the process of making a dodgeball map, which is why the rotation of the info_targets is important.
    This is how it's supposed to work/look.

    I'm guessing not. Please take a look at the above. Would I constantly need to teleport the info_targets to the teleport destinations?
     
  5. worMatty

    aa worMatty Repacking Evangelist

    Messages:
    1,072
    Positive Ratings:
    836
    Hi, there.

    I had this trouble when I was trying to make rope entities move with a falling wooden platform, using logic_measure_movement (since rope entities don't support being parented in TF2). Instead of info_target, which as you have discovered, disappears when told to be a child, I used env_spark as the point entity to follow, since it could be parented to things and would move with them fine.

    [​IMG]

    In practice you can use any parentable point entity you like, or the origin of any parentable brush entity.
     
    • Thanks Thanks x 1
  6. Crash

    aa Crash func_nerd

    Messages:
    3,191
    Positive Ratings:
    5,017
    In the past I've just made a tiny nodraw block func_brush as a replacement for parenting an info_target. It'll use the origin point of that.
     
  7. Blinx

    Blinx L69: Deviant Member

    Messages:
    69
    Positive Ratings:
    39
    Just building on what Crash said, I'm pretty sure you could use almost any kind of point or brush based entity for parenting purposes, the only thing that needs to be read is the rotation and origin, which almost all entities have, but obviously if info_target dislikes being a child, then some other non obtrusive entity like an info_teleport_destination (which despite it's name, can be used for more than just a teleport destination, info_target can even be used as a teleport destination) would need to be used.