Talk:Keyframe rope: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (Nesciuse moved page Talk:Multipage Base Pages Temp Storage/Keyframe rope to Talk:Keyframe rope without leaving a redirect: Moving back to proper place)
 
Line 5: Line 5:


What does the Speed keyvalue ''exactly'' do? Does it change the movement speed of the wind affecting the rope, or something else? --[[User:Pandaboy|Pandaboy]] 21:24, 3 November 2011 (PDT)
What does the Speed keyvalue ''exactly'' do? Does it change the movement speed of the wind affecting the rope, or something else? --[[User:Pandaboy|Pandaboy]] 21:24, 3 November 2011 (PDT)
:Nothing; it's due to the FGD being set up to inherit from a BaseClass that's also used by unrelated animation entities.<br/>— [[User:SirYodaJedi|SirYodaJedi]] ([[User_talk:SirYodaJedi|talk]]) 16:39, 25 November 2025 (PST)


== Merge this and move_rope ==
== Merge this and move_rope ==

Latest revision as of 16:39, 25 November 2025

Is there a way to make custom rope textures? --Beasty Billy 06:09, 18 February 2011 (UTC)

I don't see why not. Have you tried making it the same way you make any material (and basically copying the cable or rope material parameters)? --MossyBucket (formerly Andreasen) 06:53, 18 February 2011 (UTC)

Keyvalue: Speed

What does the Speed keyvalue exactly do? Does it change the movement speed of the wind affecting the rope, or something else? --Pandaboy 21:24, 3 November 2011 (PDT)

Nothing; it's due to the FGD being set up to inherit from a BaseClass that's also used by unrelated animation entities.
SirYodaJedi (talk) 16:39, 25 November 2025 (PST)

Merge this and move_rope

keyframe_rope and move_rope are not different entities, they're both linked to the same class CRopeKeyframe. This is from SDK 2013:

LINK_ENTITY_TO_CLASS( move_rope, CRopeKeyframe );
LINK_ENTITY_TO_CLASS( keyframe_rope, CRopeKeyframe );

In-game testing in various different branches further supports this: a rope chain does not have to start with a move_rope and have every following ent as a keyframe_rope. It can be made entirely of keyframe_ropes, entirely of move_ropes, alternate between the two, etc. and it still appears and works exactly the same. We don't have separate pages for dynamic_prop and prop_dynamic, so why should this be any different? I'd suggest using move_rope as the combined page, since that entity has more keyvalues in the default FGD. It'd still note that keyframe_rope is an alternate classname. - Luke18033 (talk) 13:57, 9 May 2021 (PDT)