Virtual pofs.tbl - Revision history

Goober5000: note mutual exclusivity

2024-04-03T01:19:27Z

note mutual exclusivity

← Older revision		Revision as of 01:19, 3 April 2024
Line 219:		Line 219:

	====+Set Properties:====		====+Set Properties:====
	*'''Optional''': If set, modifies the POF properties of the subsystem		*'''Optional''': Mutually exclusive with '''+Append Properties:'''. If set, modifies the POF properties of the subsystem
	**Syntax: '''String'''		**Syntax: '''String'''

	====+Append Properties:====		====+Append Properties:====
	*'''Optional''': If set, appends properties to the existing POF properties of the subsystem		*'''Optional''': Mutually exclusive with '''+Set Properties:'''. If set, appends properties to the existing POF properties of the subsystem
	**Syntax: '''String'''}}		**Syntax: '''String'''}}
	----		----

Goober5000: add $Set Subsystem Data:

2024-03-30T19:47:11Z

add $Set Subsystem Data:

@@ Line 201: / Line 201: @@
 **Syntax: '''string'''
 ----
 ===$Set Subobject Data:===

Lafiel: Update path parent subsystem docs

2023-05-16T16:58:52Z

Update path parent subsystem docs

← Older revision		Revision as of 16:58, 16 May 2023
Line 187:		Line 187:

	====+Parent Submodel:====		====+Parent Submodel:====
	*'''Optional''': If set, will be the parent submodel of this path. Must be specified if the path had a parent submodel in the originating POF		*'''Optional''': If set, will be the parent submodel, or, if such a submodel does not exist, the parent subsystem of this path. Must be specified if the path had a parent submodel in the originating POF. Optional if the path had no parent or just a subsystem parent. Set to <tt><none></tt> to clear an existing subsystem parent.
	**Syntax: '''string''', name of the submodel on the new POF		**Syntax: '''string''', name of the submodel/subsystem on the new POF
	}}		}}
	----		----

Lafiel: Properly add min version blocks

2023-04-07T17:45:44Z

Properly add min version blocks

← Older revision		Revision as of 17:45, 7 April 2023
Line 121:		Line 121:

	----		----
			{{Table232\|
	===$Add Weapon Bank:===		===$Add Weapon Bank:===
	*This operation adds a weapon bank to the current POF.		*This operation adds a weapon bank to the current POF.
Line 139:		Line 140:
	*'''Optional''': If set, the number of the weapon bank to replace. If not set, this operation will append a new weapon bank to the POF		*'''Optional''': If set, the number of the weapon bank to replace. If not set, this operation will append a new weapon bank to the POF
	**Syntax: '''integer''', weapon bank number		**Syntax: '''integer''', weapon bank number
			}}
	----		----
			{{Table232\|
	===$Add Dock Point:===		===$Add Dock Point:===
	*This operation adds a dock point to the current POF.		*This operation adds a dock point to the current POF.
Line 166:		Line 168:
	*'''Optional''': If set, will be the parent submodel of this dock point. Must be specified if the dock point had a parent submodel in the originating POF		*'''Optional''': If set, will be the parent submodel of this dock point. Must be specified if the dock point had a parent submodel in the originating POF
	**Syntax: '''string''', name of the submodel on the new POF		**Syntax: '''string''', name of the submodel on the new POF
			}}
	----		----
			{{Table232\|
	===$Add Path:===		===$Add Path:===
	*This operation adds a path to the current POF.		*This operation adds a path to the current POF.
Line 186:		Line 189:
	*'''Optional''': If set, will be the parent submodel of this path. Must be specified if the path had a parent submodel in the originating POF		*'''Optional''': If set, will be the parent submodel of this path. Must be specified if the path had a parent submodel in the originating POF
	**Syntax: '''string''', name of the submodel on the new POF		**Syntax: '''string''', name of the submodel on the new POF
			}}
	----		----
	===<span id="RenameOperation"></span>$Rename Subobjects:===		===<span id="RenameOperation"></span>$Rename Subobjects:===

Lafiel: Update for Modular POF Features 2

2023-04-07T17:44:45Z

Update for Modular POF Features 2

@@ Line 119: / Line 119: @@
 *Specifies the submodel name the glowpoint will be attached to
 **Syntax: '''string''', submodel name
 ----

Lafiel: Add new Virtual POF features

2022-10-24T10:34:28Z

Add new Virtual POF features

@@ Line 38: / Line 38: @@
 ====+Copy Children:====
 *'''Optional''': If set to true, the subobject and all of its children will be copied. If false, only the single subobject is copied. Default is true.
 **Syntax: '''boolean'''
@@ Line 47: / Line 55: @@
 *The name of the subobject in the to-be-modified POF that will be the parent of the to-be-copied submodel
 **Syntax: '''string'''
 ----

TopAce: there's no need to repeat the title... right under the title

2022-09-03T17:26:03Z

there's no need to repeat the title... right under the title

← Older revision		Revision as of 17:26, 3 September 2022
Line 5:		Line 5:
	The new table format to specify virtual POF-models, created modularly from other POF files.		The new table format to specify virtual POF-models, created modularly from other POF files.
	}}		}}

	~~=#Virtual POFs=~~

	The POFs defined here can be used from all other parts of the engine as if they were real, existing POF-files.		The POFs defined here can be used from all other parts of the engine as if they were real, existing POF-files.
Line 90:		Line 88:
	**Syntax: '''Vector''', three ''floats'', x, y, z respectively. All values must be larger than those specified in <tt>+Minimum:</tt>		**Syntax: '''Vector''', three ''floats'', x, y, z respectively. All values must be larger than those specified in <tt>+Minimum:</tt>

	=Example=		==Example==

	<pre>		<pre>

Lafiel: Add Virtual_pofs.tbl

2022-09-03T13:14:05Z

Add Virtual_pofs.tbl

New page

{{SCP_table}}
{{Tables}}

{{Table224|
The new table format to specify virtual POF-models, created modularly from other POF files.
}}

=#Virtual POFs=

The POFs defined here can be used from all other parts of the engine as if they were real, existing POF-files.
It can / will be able to be used for a variety of different purposes:
* Variety without copying models, by having one base model POF with the variations defined as virtual POFs
* Better dependency on other assets, by being able to modify existing models of depending mods instead of needing a full modified copy of the model.
* To modify models in a mod without having to redefine the ship classes
* To semi-dynamically generate certain types of models, like ships with modular hardpoints for certain turrets or other parts, or large structures like asteroid fields.

==$POF:==
*The virtual filename of this POF.
**If a POF of this filename already exists, this virtual POF will replace it. Virtual POFs can replace other virtual POFs as well, including those that already replace other POFs themselves.
**Accessing a POF with the same name from this definition will use the POF to-be-replaced.
**(Example: Virtual POF A overwrites the real A.pof. Accessing A.pof within the definition of the virtual POF A will yield the original A.pof. Accessing A.pof from the engine will yield virtual POF A)

==+Base POF:==
* The filename of the base POF to be modified.

==Operations==
*Here, the actual modification operations are specified. The operations that are defined here, need to be a list with elements made out of the following:

===$Add Subobject:===
*This operation adds a subobject from a different POF to the current POF to be modified.

====+POF to Add:====
*The filename of the POF from which the new subobject is to be copied.
**Syntax: '''string''', filename

====+Source Subobject:====
*The name of the subobject in the to-be-added POF that should be copied
**Syntax: '''string'''

====+Copy Children:====
*'''Optional''': If set to true, the subobject and all of its children will be copied. If false, only the single subobject is copied. Default is true.
**Syntax: '''boolean'''

====$Rename Subobjects:====
*'''Optional''': Can be used to rename the copied subobjects. This is optional, except if the resulting model would have two subobjects of the same name. This is not allowed, a model must always have unique submodel names.
**Syntax: [[#RenameOperation|See <tt>$Rename Subobjects:</tt>]]

====+Destination Subobject:====
*The name of the subobject in the to-be-modified POF that will be the parent of the to-be-copied submodel
**Syntax: '''string'''

----
===<span id="RenameOperation"></span>$Rename Subobjects:===
*This operation renames subobjects. The following two entries can be repeated as often as needed
====+Replace:====
*The name of the subobject to be renamed
**Syntax: '''string'''

====+With:====
*The new name of the subobject
**Syntax: '''string'''

----
===$Set Subobject Data:===
*This operation can be used to modify a specific subobject.

====+Subobject:====
*The name of the subobject to be modified
**Syntax: '''string'''

====+Set Offset:====
*'''Optional''': If set, modifies the offset of the subobject, relative to the center of its parent
**Syntax: '''Vector''', three ''floats'', x, y, z respectively

----
===$Set Header Data:===
*This operation can be used to modify the header data of a model

====+Set Radius:====
*'''Optional''': If set, modifies the radius of the model. The model can only collide with parts that lie within this radius, measured from the model center
**Syntax: '''float'''

====$Set Bounding Box:====
*'''Optional''': If set, modifies the bounding box of the model. The model can only collide with parts that lie within this bounding box
=====+Minimum:=====
*The corner of the bounding box with lower coordinates
**Syntax: '''Vector''', three ''floats'', x, y, z respectively
=====+Maximum:=====
*The corner of the bounding box with higher coordinates
**Syntax: '''Vector''', three ''floats'', x, y, z respectively. All values must be larger than those specified in <tt>+Minimum:</tt>

=Example=

<pre>
#Virtual POFs

$POF: Fighter01.pof
+Base POF: Fighter01.pof
$Add Subobject:
+POF to Add: Fenris_FS2.pof
+Source Subobject: detailbox_engines
+Destination Subobject: detail0
$Add Subobject:
+POF to Add: Fenris_FS2.pof
+Source Subobject: radar01a-dish
$Rename Subobjects:
+Replace: radar01a-dish
+With: radar
+Destination Subobject: detail0
$Set Subobject Data:
+Submodel: detailbox_engines
+Set Offset: 0, 0, -15
$Set Subobject Data:
+Submodel: radar
+Set Offset: 0, 10, 0

#End
</pre>
[[Category:Tables]]
[[Category:Source Code Project]]