The Parts and Whole: Overview - Revision history

Geep: /* Other Techniques that Affect Both DR and TDM */ add link to Inlining topic

2022-04-26T22:07:35Z

Other Techniques that Affect Both DR and TDM: add link to Inlining topic

← Older revision		Revision as of 22:07, 26 April 2022
Line 128:		Line 128:
	* Combining Models		* Combining Models
	* [[The_Parts_and_Whole:_Func_Group\|Func Group]]		* [[The_Parts_and_Whole:_Func_Group\|Func Group]]
	* Inlining		* [[Inlining]]
	]		]

Geep: /* Other Techniques that Affect Both DR and TDM */ add link to func_group

2022-04-05T02:14:17Z

Other Techniques that Affect Both DR and TDM: add link to func_group

← Older revision		Revision as of 02:14, 5 April 2022
Line 127:		Line 127:
	* Multiple Instances Combined with SEED		* Multiple Instances Combined with SEED
	* Combining Models		* Combining Models
	* Func ~~Groups~~		* [[The_Parts_and_Whole:_Func_Group\|Func Group]]
	* Inlining		* Inlining
	]		]

Geep: Link to new Entity with Primitives page

2022-04-02T19:57:12Z

Link to new Entity with Primitives page

← Older revision		Revision as of 19:57, 2 April 2022
Line 121:		Line 121:

	==Other Techniques that Affect Both DR and TDM==		==Other Techniques that Affect Both DR and TDM==
	[PLANNED]~~[Coverage to include~~:		[PLANNED coverage, except as linked]:

	* Conversion from/to Worldspawn		* Conversion from/to Worldspawn
	* ~~Entities~~ with Primitives		* [[The_Parts_and_Whole:_Entity_with_Primitives\|Entity with Primitives]]
	* Multiple Instances Combined with SEED		* Multiple Instances Combined with SEED
	* Combining Models		* Combining Models

Geep: Add Cloning Object section. Tweak prefab

2022-01-29T21:53:35Z

Add Cloning Object section. Tweak prefab

← Older revision		Revision as of 21:53, 29 January 2022
Line 81:		Line 81:
	\|[[The_Parts_and_Whole:_DR_Selection_Sets\|Selection Set]]\|\| \|\|X\|\| \|\|Dozens\|\|		\|[[The_Parts_and_Whole:_DR_Selection_Sets\|Selection Set]]\|\| \|\|X\|\| \|\|Dozens\|\|
	\|}		\|}
			==Cloning Objects - The Basics==
			As you know, one or more selected objects are duplicated in DR simply by hitting the Space bar. They appear atop their source objects (or slightly displaced, if the "Offset cloned objects by 1 grid unit to the right and downwards" button is so toggled). Name conflicts are automatically resolved. You then drag the clones to where you need them.

			Space bar is effectively a shortcut for Copy/Paste. Furthermore, you can use Copy in one DR instance and Paste in another; the duplicates will arrive at the source's map coordinates. Then you drag.

			You could Copy from DR, Paste into a text editor, and save to disk. Then later reverse the process. Prefabs, next, formalizes that process, and spares you the post-paste dragging.
	==Prefabs==		==Prefabs==
	A Prefab is a set of map objects stored as a disk file, for re-use. The set is typically of moderate size and diverse but with a unifying theme, e.g.:		A Prefab is a set of map objects stored as a disk file, for re-use. The set is typically of moderate size and diverse but with a unifying theme, e.g.:
Line 87:		Line 92:
	* a corridor with wall modules		* a corridor with wall modules
	* a few AI characters and their paths, with some adjoining furniture and knick-knacks.		* a few AI characters and their paths, with some adjoining furniture and knick-knacks.
			A Prefab file has much the same syntax and content as a Map file, but is meant for DR alone; it cannot be DMAP’d.

	Upon import into DR, a Prefab is converted to its constituent objects, ~~optionally grouped~~. ~~So, once~~ inside DR, there is no longer a prefab per se~~. A Prefab file has much the same syntax and content as a Map file, but is meant for DR alone; it cannot be DMAP’d~~.		Upon import into DR, a Prefab is converted to its constituent objects. During this, two checkboxes provide automatic options for the objects: to re-position them around the current map insertion point, and to place them in a Group. Once inside DR, there is no longer a prefab per se.

	Stock Prefabs are an important asset distribution method for TDM. Or you can make your own custom ones. It is one way to promulgate duplicates throughout your current FM, or be part of a private asset archive for all your FMs. Or shared. Prefabs may be helpful while crafting new modular architectures.		Stock Prefabs are an important asset distribution method for TDM. Or you can make your own custom ones. It is one way to promulgate duplicates throughout your current FM, or be part of a private asset archive for all your FMs. Or shared. Prefabs may be helpful while crafting new modular architectures.
Line 100:		Line 106:
	\|[[The_Parts_and_Whole:_Prefab_Import\|Import Prefab (or RMB Insert Prefab)]]		\|[[The_Parts_and_Whole:_Prefab_Import\|Import Prefab (or RMB Insert Prefab)]]
	\|Inspect available prefabs (either stock TDM ones, or custom), and place in your project		\|Inspect available prefabs (either stock TDM ones, or custom), and place in your project
	\|Pros: Can preview prefabs. On import, can ~~Group if~~ desired~~; or not, to tweak relative placements~~.<br />		\|Pros: Can preview prefabs. On import, can control insertion and/or auto-group as desired.<br />
	Cons: Only map objects are contained in a prefab; other assets may be needed. If importing duplicates, each instance adds to map filesize and (typically) entity count.		Cons: Only map objects are contained in a prefab; other assets may be needed. If importing duplicates, each instance adds to map filesize and (typically) entity count.
	\|-		\|-

Geep: /* Prefabs */

2022-01-27T19:46:50Z

Prefabs

← Older revision		Revision as of 19:46, 27 January 2022
Line 90:		Line 90:
	Upon import into DR, a Prefab is converted to its constituent objects, optionally grouped. So, once inside DR, there is no longer a prefab per se. A Prefab file has much the same syntax and content as a Map file, but is meant for DR alone; it cannot be DMAP’d.		Upon import into DR, a Prefab is converted to its constituent objects, optionally grouped. So, once inside DR, there is no longer a prefab per se. A Prefab file has much the same syntax and content as a Map file, but is meant for DR alone; it cannot be DMAP’d.

	Stock Prefabs are an important asset distribution method for TDM. Or you can make your own custom ones. It is one way to promulgate duplicates throughout your current FM. Or ~~share~~. It may be helpful while crafting new modular architectures.		Stock Prefabs are an important asset distribution method for TDM. Or you can make your own custom ones. It is one way to promulgate duplicates throughout your current FM, or be part of a private asset archive for all your FMs. Or shared. Prefabs may be helpful while crafting new modular architectures.

	{\| class="wikitable"		{\| class="wikitable"

Geep: /* Prefabs */ add link

2022-01-27T19:37:00Z

Prefabs: add link

← Older revision		Revision as of 19:37, 27 January 2022
Line 98:		Line 98:
	! Pros & Cons		! Pros & Cons
	\|-		\|-
	\|[[The_Parts_and_Whole:~~_Import_Prefab~~\|Import Prefab (or RMB Insert Prefab)]]		\|[[The_Parts_and_Whole:_Prefab_Import\|Import Prefab (or RMB Insert Prefab)]]
	\|Inspect available prefabs (either stock TDM ones, or custom), and place in your project		\|Inspect available prefabs (either stock TDM ones, or custom), and place in your project
	\|Pros: Can preview prefabs. On import, can Group if desired; or not, to tweak relative placements.<br />		\|Pros: Can preview prefabs. On import, can Group if desired; or not, to tweak relative placements.<br />

Geep: add link

2022-01-26T22:50:29Z

add link

← Older revision		Revision as of 22:50, 26 January 2022
Line 103:		Line 103:
	Cons: Only map objects are contained in a prefab; other assets may be needed. If importing duplicates, each instance adds to map filesize and (typically) entity count.		Cons: Only map objects are contained in a prefab; other assets may be needed. If importing duplicates, each instance adds to map filesize and (typically) entity count.
	\|-		\|-
	\|[[The_Parts_and_Whole:~~_Export_Prefab~~\|Export Selected as Prefab]]		\|[[The_Parts_and_Whole:_Prefab_Export\|Export Selected as Prefab]]
	\|Make a custom prefab, to re-use in current or future FMs, or share with others.		\|Make a custom prefab, to re-use in current or future FMs, or share with others.
	\|Pros: Creates custom asset for import, e.g., duplicates in your FM<br />		\|Pros: Creates custom asset for import, e.g., duplicates in your FM<br />

Geep: /* Prefabs */ created content

2022-01-26T22:11:48Z

Prefabs: created content

@@ Line 36: / Line 36: @@
 |-
 |[[The_Parts_and_Whole:_DR_Filters|Filter]]
-|Toggle visibility based on class name or other attributes (i.e., spawnargs)
+|Toggle visibility based on class name or other attributes (i.e., spawnargs).
 |Pros: Good selection of built-in filters. Quick to use & needs no management. Custom filters possible.<br />
 Cons: Custom filters require programming.
@@ Line 82: / Line 82: @@
 |}
-==Special Case: Prefabs==
+==Prefabs==
-[PLANNED][Also update of existing Prefab article]
+A Prefab is a set of map objects stored as a disk file, for re-use. The set is typically of moderate size and diverse but with a unifying theme, e.g.:
-==Techniques that Affect Both DR and TDM==
+Upon import into DR, a Prefab is converted to its constituent objects, optionally grouped. So, once inside DR, there is no longer a prefab per se. A Prefab file has much the same syntax and content as a Map file, but is meant for DR alone; it cannot be DMAP’d.
 [PLANNED][Coverage to include:

Geep: At top, link to forum thread for suggestions

2022-01-23T20:13:28Z

At top, link to forum thread for suggestions

← Older revision		Revision as of 20:13, 23 January 2022
Line 1:		Line 1:
	''By Geep 2022''		''By Geep 2022''

	"The Parts and Whole" ~~series~~ explores map objects being brought together into higher-level assemblies... their creation, navigation, manipulation, and benefits. Dark Radiant provides a number of techniques to control the visibility, selectability, and association of multiple objects. Some also can improve game performance. Here's a quick overview. Follow individual links ~~[WIP]~~ for lots more.		''This is a work in progress. To give feedback or suggestions, see the forum thread [https://forums.thedarkmod.com/index.php?/topic/21256-the-parts-and-whole-discussion/ The Parts and Whole: Discussion]''

			As a broad theme, "The Parts and Whole" explores map objects being brought together into higher-level assemblies... their creation, navigation, manipulation, and benefits. Dark Radiant provides a number of techniques to control the visibility, selectability, and association of multiple objects. Some also can improve game performance. Here's a quick overview. Follow individual links for lots more.

	==Techniques that Affect DR Only==		==Techniques that Affect DR Only==

Geep: /* In a Nutshell */ typo

2022-01-23T18:48:06Z

In a Nutshell: typo

← Older revision		Revision as of 18:48, 23 January 2022
Line 45:		Line 45:
	\|-		\|-
	\|[[The_Parts_and_Whole:_DR_Selection_Sets\|Selection Set]]		\|[[The_Parts_and_Whole:_DR_Selection_Sets\|Selection Set]]
	\|~~Clusters~~ objects together temporarily, with naming.		\|Cluster objects together temporarily, with naming.
	\|Pros: Consider for one-time complex editing tasks.<br />		\|Pros: Consider for one-time complex editing tasks.<br />
	Cons: Lacks the persistence and fine-grained control of Groups and Layers.		Cons: Lacks the persistence and fine-grained control of Groups and Layers.