Parenting info_targets

oWave

L1: Registered
Jan 27, 2014
10
4
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?)
 

Blinx

L69: Deviant Member
Mar 14, 2016
69
51
Info_teleport_destination would probably work just as well.
 

oWave

L1: Registered
Jan 27, 2014
10
4
An important question would be what you're trying to do with them. We might have a different solution than what you're trying.

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.

Info_teleport_destination would probably work just as well.
I'm guessing not. Please take a look at the above. Would I constantly need to teleport the info_targets to the teleport destinations?
https://gfycat.com/WarlikeParallelKillifish
 

worMatty

Repacking Evangelist
aa
Jul 22, 2014
1,257
999
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.

zuoHVF0.jpg


In practice you can use any parentable point entity you like, or the origin of any parentable brush entity.
 

Blinx

L69: Deviant Member
Mar 14, 2016
69
51
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.