Door Entities - Revision history

Fire-hound at 09:21, 2 May 2020

2020-05-02T09:21:15Z

Fire-hound: /* Flowgraph Doors */

2019-08-18T17:25:56Z

‎Flowgraph Doors

Fire-hound at 17:57, 13 February 2018

2018-02-13T17:57:10Z

Fire-hound: /* Advanced Doors */ seem to be broken?

2018-02-13T17:46:38Z

‎Advanced Doors: seem to be broken?

Fire-hound: /* Flowgraph Doors */

2018-02-06T10:07:43Z

‎Flowgraph Doors

Fire-hound: /* Flowgraph Doors */ images worth 1000's of words ;)

2018-02-03T17:40:55Z

‎Flowgraph Doors: images worth 1000's of words ;)

Fire-hound: /* Doors */ the initial text

2018-02-03T17:26:25Z

‎Doors: the initial text

Fire-hound: initial page

2018-02-03T16:50:21Z

initial page

New page

== Doors ==

← Older revision		Revision as of 09:21, 2 May 2020
Line 1:		Line 1:
−		+	{{ Stub }}
	== Working Doors Types ==		== Working Doors Types ==

← Older revision		Revision as of 17:25, 18 August 2019
Line 44:		Line 44:

	If You scale the group, it might stop working - or even worse yet - become erratic in operation.		If You scale the group, it might stop working - or even worse yet - become erratic in operation.
		+
		+	Non uniform scaling (scaling along just one axis) of objects makes them stop interacting with physics.

	{{Navbox Mapping}}		{{Navbox Mapping}}

← Older revision		Revision as of 17:57, 13 February 2018
Line 44:		Line 44:

	If You scale the group, it might stop working - or even worse yet - become erratic in operation.		If You scale the group, it might stop working - or even worse yet - become erratic in operation.
		+
		+	{{Navbox Mapping}}

@@ Line 8: / Line 8: @@
 === Advanced Doors ===
-Doors that can have more complex interaction with the environment, can only pivot around their Z axis.
+Doors that can have more complex interaction with the environment, can only pivot around their Z axis. Reportedly don't work in multiplayer.
 === Animated Doors===

← Older revision		Revision as of 10:07, 6 February 2018
Line 16:		Line 16:

	=== Flowgraph Doors ===		=== Flowgraph Doors ===
		+	big fat warring: Flowgraph can seriously de-sync during an server load spike.
		+
	Thanks to the flowgraph editor, just about any entity can be made to interact with the player or the surrounding.		Thanks to the flowgraph editor, just about any entity can be made to interact with the player or the surrounding.

@@ Line 22: / Line 22: @@
 In the default setup it won't behave anything different than a simple door entity.
-/TODO/ images of the settings
+[[File:RigidBodyEx_Settings.png]]
 Once tweaked, however, they become immune to the bug.
@@ Line 29: / Line 29: @@
 Make it as in the following image:
-/TODO/ flowgraph image
+[[File:Sliding_Doors_Flowgraph.png]]
 Then make sure You place the TagPos helpers found in the AI menu on the proper locations.
 Now connect all with the flowgraph (assign proper entities to proper flowgraph nodes)

← Older revision		Revision as of 17:26, 3 February 2018
Line 1:		Line 1:

−	== Doors ==	+	== Working Doors Types ==
		+
		+	=== Doors ===
		+	The simple normal doors. Versatile, reliable, but sadly, broken to the MW:LL BA grenade impact (not the explosion). Once hit they leave their position and begin to travel wildly.
		+
		+	Can both pivot or slide around an arbitrary axis
		+
		+	=== Advanced Doors ===
		+	Doors that can have more complex interaction with the environment, can only pivot around their Z axis.
		+
		+	=== Animated Doors===
		+	Animated doors, while already defined and not tweakable in the Sandbox2 editor, allow for most freedom outside it - in the 3d art moddeling suite of choice.
		+
		+	The SA arena doors in MW:LL are an example - reliable operation and appearance
		+
		+	=== Flowgraph Doors ===
		+	Thanks to the flowgraph editor, just about any entity can be made to interact with the player or the surrounding.
		+
		+	For the doors to be immune to the BA grenades, the '''RigidBodyEx''' entity has been proven to be good.
		+
		+	In the default setup it won't behave anything different than a simple door entity.
		+
		+	/TODO/ images of the settings
		+
		+	Once tweaked, however, they become immune to the bug.
		+
		+	For them to be actuated, it all begins from the ProximityArea Trigger - create an flowgraph assigned to it.
		+	Make it as in the following image:
		+
		+	/TODO/ flowgraph image
		+
		+	Then make sure You place the TagPos helpers found in the AI menu on the proper locations.
		+
		+	Now connect all with the flowgraph (assign proper entities to proper flowgraph nodes)
		+
		+	In order to make it practical for moving or re-using, have all the entities grouped together.
		+
		+	To have access to their properties, select the group and open it - this way they still move together (if the group is selected), but each can be adjusted by it's own.
		+
		+	If You scale the group, it might stop working - or even worse yet - become erratic in operation.