Attaching cables to something.. There appears to be a bug of some sort.

I attached 6 seperate entities to a box, and 3 others elsewhere.. but it didn't work

func_physbox (box) name: box

move_rope (pos. 1) : ropeholder1, next keyframe: rope1

move_rope (pos. 2): ropeholder2, next keyframe: rope2

move_rope (pos. 3): ropeholder3, next keyframe: rope3

keyframe_rope (box): rope1, parent: box

keyframe_rope (box) - 2: rope2, parent: box

keyframe_rope (box) - 3: rope3, parent: box

phys_lengthsconstraint (box, origin @ ropeholder1): constraint1, entity 1: box

phys_lengthsconstraint (box, origin @ ropeholder2): constraint2, entity 1: box

phys_lengthsconstraint (box, origin @ ropeholder3): constraint3, entity 1: box

it is MEANT to be moving crazy.

My problem: the move_rope ropes, although they are (in hammer) looking
to be connected to the others, in the game ALL connect at the center
point.. e.g. in hammer is EXACT center.

I have made a new map, same situation, no go..

Anyone?

I have a similar problem. I made 3 swinging lights, which do by the way swing perfectly, because I followed the tutorial exactly... EXCEPT there's one problem:

...you see cables that run from the point of attachment all the way to exact center, origin (0,0,0). The cable that actually holds the light is invisible. It looks weird. I cannot seem to get around this problem. I tried deleting and re-adding the entities-- no luck. I tried changing every attribute I could think of-- no luck there either.

Let me know if you find the solution to this. It may be an editor bug with no work-around. Hopefully Valve will fix this in a new release of Hammer.

Where is your func_physbox when this happens? And does it work fine without the lengthconstraints?

It's a bug in CS:S. This sort of thing works fine in HL2 and HL2DM, but
any rope with a position parented to something ends up pointing to
0,0,0 in CS:S.

There's a workaround using logic_measure_movement, but it's not pretty. See

here
(end of thread) for my solution.

This is a well-known bug in CS:S. It happens when you try to
parent a keyframe_rope to something. I think you can just switch
your entities around (parenting the move_rope to the moving object
instead of the keyframe_rope), but if that doesn't work, there's
another solution using logic_measure_movement described in these two
threads (search is your friend!).

http://www.chatbear.com/board.plm?a=viewthread&b=4989&t=738,1104483021,32326&s=0&id=765763#1

http://www.chatbear.com/board.plm?a=viewthread&t=609,1102946880,18626&id=752855&b=4989&v=flatold