CFuncMoveLinear/notes: Difference between revisions
Jump to navigation
Jump to search
Note:The
Bug:There are bugs that may arise when parenting this entity to any of these: func_movelinear, momentary_door, func_lookdoor, func_water_analog. A func_door can be used as a workaround. See here for a code fix. [todo tested in ?]
(for notes that very likely apply to all CFuncMoveLinear entities) |
(errrr) |
||
Line 7: | Line 7: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
!Game:!{{ | !Game:!!{{as}}!!{{csgo}}!!{{css}}!!{{DODS}}!!{{HL2}}!!HL2:DM!!HL2:Ep1!!HL2:Ep2!!{{l4d}}!!{{l4d2}}!!{{portal}}!!{{portal2}}!!{{tf2}} | ||
|- | |- | ||
|Affects game:||?||No||?||?||?||?||?||?||?||?||?||?||? | |Affects game:||?||No||?||?||?||?||?||?||?||?||?||?||? | ||
|} | |} |
Revision as of 01:42, 9 September 2018

SetPosition
input and Start Position keyvalue do not perform any bounds checking, so values less than 0 and greater than 1 can be used. Negative values will move in the opposite direction to the movement direction, and values greater than 1 will move it in multiples of the set Move Distance. Moving past the opened/closed position does not trigger the OnFullyOpen
and OnFullyClosed
outputs.
Todo: List which games have the parenting bugs. The bugs were first noted in June 2006; it's possible they don't actually even exist anymore. It's also not clear what exactly the bugs are.
Game: | ![]() |
![]() |
![]() |
![]() |
![]() |
HL2:DM | HL2:Ep1 | HL2:Ep2 | ![]() |
![]() |
![]() |
![]() |
![]() |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Affects game: | ? | No | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |