The Parts and Whole: Func Group - Revision history

Geep: /* Introduction */

2022-04-05T03:49:44Z

Introduction

← Older revision		Revision as of 03:49, 5 April 2022
Line 3:		Line 3:
	==Introduction==		==Introduction==

	Wish you could name a grouping of one or more worldspawn items (i.e., brushes and patches), for convenience in DR? ~~That’s~~ what func_group is for. ~~Here’s how~~:		Wish you could name a grouping of one or more worldspawn items (i.e., brushes and patches), for convenience in DR? That's what func_group is for.

			First, set a global spawnarg "moveFuncGroups 1" (i.e., on any piece of worldspawn that will NOT be converted to func_group). Then:

	* Select your worldspawn objects of interest		* Select your worldspawn objects of interest
	* Begin the conversion with:		* Begin the conversion with:

Geep: /* Use Case */

2022-04-05T03:30:15Z

Use Case

← Older revision		Revision as of 03:30, 5 April 2022
Line 28:		Line 28:
	* ''By Export of the Ensemble as a Reusable Model.'' This is similar to func_group in some regards. Before export, you first have to convert the brushes from worldspawn into entities. And turning imported instances back to worldspawn later, besides losing the naming, can have problems (e.g., with grid alignment; but see the cautions with func_group as well).		* ''By Export of the Ensemble as a Reusable Model.'' This is similar to func_group in some regards. Before export, you first have to convert the brushes from worldspawn into entities. And turning imported instances back to worldspawn later, besides losing the naming, can have problems (e.g., with grid alignment; but see the cautions with func_group as well).

	Another perceived advantage of func_group is as a method to drastically decrease entity counts inflated by architectural pieces, allowing for a lot more leeway when it comes to modular building. But the expanded entity limit in TDM 2.14 means that careful management of entity count is no longer required. Still, entities have a drawcall penalty compared to worldspawn, so there may be performance benefits.		Another perceived advantage of func_group is as a method to drastically decrease entity counts inflated by architectural pieces, allowing for a lot more leeway when it comes to modular building. But the expanded entity limit in TDM 2.10 means that careful management of entity count is no longer required. Still, entities have a drawcall penalty compared to worldspawn, so there may be performance benefits.

	==Cautions==		==Cautions==

Geep: /* Introduction */

2022-04-05T03:08:35Z

Introduction

← Older revision		Revision as of 03:08, 5 April 2022
Line 13:		Line 13:

	During DMAP, the group members are turned back into worldspawn!		During DMAP, the group members are turned back into worldspawn!

			''Be aware that early Doom/Quake editors used "func_group" with a different meaning, like the current DR Group feature.''

	==Use Case==		==Use Case==

Geep: /* Use Case */

2022-04-05T02:46:17Z

Use Case

← Older revision		Revision as of 02:46, 5 April 2022
Line 26:		Line 26:
	* ''By Export of the Ensemble as a Reusable Model.'' This is similar to func_group in some regards. Before export, you first have to convert the brushes from worldspawn into entities. And turning imported instances back to worldspawn later, besides losing the naming, can have problems (e.g., with grid alignment; but see the cautions with func_group as well).		* ''By Export of the Ensemble as a Reusable Model.'' This is similar to func_group in some regards. Before export, you first have to convert the brushes from worldspawn into entities. And turning imported instances back to worldspawn later, besides losing the naming, can have problems (e.g., with grid alignment; but see the cautions with func_group as well).

	~~At one time, another~~ perceived advantage of func_group ~~was~~ as a method to drastically decrease entity counts inflated by architectural pieces, allowing for a lot more leeway when it comes to modular building. But the expanded entity limit in TDM 2.14 means that careful management of entity count is no longer required.		Another perceived advantage of func_group is as a method to drastically decrease entity counts inflated by architectural pieces, allowing for a lot more leeway when it comes to modular building. But the expanded entity limit in TDM 2.14 means that careful management of entity count is no longer required. Still, entities have a drawcall penalty compared to worldspawn, so there may be performance benefits.

	==Cautions==		==Cautions==

Geep: create this article

2022-04-05T02:32:54Z

create this article

New page

''by Geep 2022, based on posts by Spooks''

==Introduction==

Wish you could name a grouping of one or more worldspawn items (i.e., brushes and patches), for convenience in DR? That’s what func_group is for. Here’s how:
* Select your worldspawn objects of interest
* Begin the conversion with:
** In DR 3.0+, RMB and "Convert to Entity..."
** In earlier versions of DR, RMB and "Convert to func_static". Then, in the Entity Inspector, use the "Choose Entity Class..." button
* Choose the classname "func_group", found under "Internal", not "Funcs"
* Give the group a name
* Don’t bother giving the func_group any additional spawnargs (because it’s useless; func_group entities will not spawn)

During DMAP, the group members are turned back into worldspawn!

==Use Case==

''Adapted from [https://forums.thedarkmod.com/index.php?/topic/17864-the-functionality-of-func_group/#comment-387979 a forum thread by Spooks]''

The biggest advantage is func_static-like naming flexibility in the editor.

Suppose you have four different brushes as an ensemble, and want to clone them 100 times around the map while still being able to select each one of those 100 ensembles, particularly by name. Drawbacks to other methods are:

* ''With Layers.'' The Layers viewer offers only a flat view (not hierarchal or folder-based), and 100 Layers is unmanageable.
* ''With Selection Sets.'' Also unwieldy with 100 items, but even worse, since you have to go through a typed list and there's no way to delete an individual selection set. And sets don’t persist across sessions
* ''By Export of the Ensemble as a Reusable Model.'' This is similar to func_group in some regards. Before export, you first have to convert the brushes from worldspawn into entities. And turning imported instances back to worldspawn later, besides losing the naming, can have problems (e.g., with grid alignment; but see the cautions with func_group as well).

At one time, another perceived advantage of func_group was as a method to drastically decrease entity counts inflated by architectural pieces, allowing for a lot more leeway when it comes to modular building. But the expanded entity limit in TDM 2.14 means that careful management of entity count is no longer required.

==Cautions==

Because the func_group name is not retained after DMAP, you can’t usefully reference it at run time, e.g., as a target or in a TDM script function.

Be careful about moving a func_group, because it will not be constrained by the grid, and so when DMAP’d back to worldspawn, may be off-grid and thus prone to causing rendering anomalies.

In DR’s Filters, a func_group will be treated as just another entity. Thus, it will disappear with the "All entities" filter. If you are using that filter to visualize where your sealing worldspawn is, you may be misled, overlooking worldspawn converted during compilation from func_group.

==See Also==
[[The Parts and Whole: Overview]]

{{editing}}