POFCS2Help/HelpHome - Revision history

Col. Fishguts at 16:42, 9 January 2022

2022-01-09T16:42:54Z

← Older revision		Revision as of 16:42, 9 January 2022
Line 44:		Line 44:

	==Max Radius==		==Max Radius==
	This is the maximum distance between any point on the craft and the craft's center. ~~<!-- center of mass? pivot point? -->~~		This is the maximum distance between any point on the craft and the craft's center.
	It is used ~~to determine ship-to-ship collisions~~ for ~~small craft (where model geometry is ignored)~~.		It is used for scaling subspace effects and default scaling in the tech room and target view.
	PCS2 automatically calculates this value based on model geometry.		PCS2 automatically calculates this value based on model geometry.

Col. Fishguts at 16:37, 4 January 2022

2022-01-04T16:37:13Z

← Older revision		Revision as of 16:37, 4 January 2022
Line 88:		Line 88:
	=SubObjects=		=SubObjects=
	This shows a list of all the subobjects present in the POF, including the hierarchy.		This shows a list of all the subobjects present in the POF, including the hierarchy.
	The layout/hierarchy is defined from the source model that you imported into PCS2. You can delete/copy individual subobjects and re-arrange the hierarchy by dragging/dropping ~~subobjets~~ in the navigation pane. See also: https://wiki.hard-light.net/index.php/Tutorial_-_PCS2_Kitbashing		The layout/hierarchy is defined from the source model that you imported into PCS2. You can delete/copy individual subobjects and re-arrange the hierarchy by dragging/dropping subobjects in the navigation pane. See also: https://wiki.hard-light.net/index.php/Tutorial_-_PCS2_Kitbashing

	Some remarks about the required hierarchy:		Some remarks about the required hierarchy and naming conventions:
	*All "parent" objects (= the main model object for each LOD) need to be at the top-level		*All "parent" objects (= the main model object for each LOD) need to be at the top-level
	*All debris chunks need to be at the top level		*All debris chunks need to be at the top level
	*Subobjects that are sub-models (e.g. turrets or any other submodel) need to be children of their respective main model		*Subobjects that are sub-models (e.g. turrets or any other submodel) need to be children of their respective main model
	*Turret arms of multi-part turrets needs to be children of their respective turret base, which in turn need to be children of their respective main model		*Turret arms of multi-part turrets needs to be children of their respective turret base, which in turn need to be children of their respective main model
	*Subobjects that represent destroyed versions of a subobject (they have the same name but with "-destroyed" appended) need to be in the same level as their intact counterpart. The game will switch to the -destroyed subobject if the ~~repsective~~ subsystem gets destroyed		*Subobjects that are children of one of the main LOD models (detail0, detail1, detail2, detail3) should have names ending in "a" (for detail0), "b" (for detail1), "c" (for deteail2) and "d" (for detail3). So if "turret01a" is attached to detail0, its counterpart on detail1 should be named "turret01b", on detail2 "turret01c" and on detail3 "turret01d". This naming tells the game that those subobjects are representing the same subsystem on different LODs and will act accordingly (this is relevant for collision checks and subobjects animations)
			*Subobjects that represent destroyed versions of a subobject (they have the same name but with "-destroyed" appended) need to be in the same level as their intact counterpart. The game will switch to the -destroyed subobject if the respective subsystem gets destroyed

	[[File:SubObjects.png]]		[[File:SubObjects.png]]

Col. Fishguts at 16:26, 4 January 2022

2022-01-04T16:26:34Z

← Older revision		Revision as of 16:26, 4 January 2022
Line 88:		Line 88:
	=SubObjects=		=SubObjects=
	This shows a list of all the subobjects present in the POF, including the hierarchy.		This shows a list of all the subobjects present in the POF, including the hierarchy.
	The layout/hierarchy is defined from the source model that you imported into PCS2. You can delete/copy individual subobjects and re-arrange the hierarchy by dragging/dropping subobjets in the navigation pane.		The layout/hierarchy is defined from the source model that you imported into PCS2. You can delete/copy individual subobjects and re-arrange the hierarchy by dragging/dropping subobjets in the navigation pane. See also: https://wiki.hard-light.net/index.php/Tutorial_-_PCS2_Kitbashing

	Some remarks about the required hierarchy:		Some remarks about the required hierarchy:

Col. Fishguts at 18:38, 3 January 2022

2022-01-03T18:38:04Z

← Older revision		Revision as of 18:38, 3 January 2022
Line 13:		Line 13:
	PCS2 can be used to define/edit all meta data (as in non-model data) needed to get a usable POF file.		PCS2 can be used to define/edit all meta data (as in non-model data) needed to get a usable POF file.
	If in doubt, look at an original Volition POF file for reference on how to set up your model.		If in doubt, look at an original Volition POF file for reference on how to set up your model.

			PCS2 shows 3 panes/sections:
			*On the left side you have a navigation pane showing all the elements stored in the POF.
			*In the middle is a 3D-view of the POF that you can rotate/pan/zoom with the mouse.
			*On the right side you can see all the editable values of the currently selected element.


	The x/y/z coordinate system in a POF file (and therefore PCS) is probably different from what you're used in your modelling tool. In relation to the forward-direction of the model:		The x/y/z coordinate system in a POF file (and therefore PCS) is probably different from what you're used in your modelling tool. In relation to the forward-direction of the model:
Line 25:		Line 31:

	=Header=		=Header=
	The Header group contains the LOD and Debris list which points to which model as being the respective LOD and debris (The models themselves are contained in the [[#SubObjects \| SubObjects]] group). The Header group also contains physical values (such as mass and moment of inertia) and other assorted values.		The Header group contains the LOD and Debris list which points to which model as being the respective LOD and debris (The models themselves are contained in the [[#SubObjects \| SubObjects]] group). The Header group also contains physical values (such as mass and moment of inertia) and other assorted values, all shown on the right editing pane.
	==Bounding Box Min/Max==		==Bounding Box Min/Max==
	*'''Bounding Box Min''' is the minimum (i.e. lower rear left-hand corner if you where facing the same direction as the object) X, Y, Z coordinate of the bounding box.		*'''Bounding Box Min''' is the minimum (i.e. lower rear left-hand corner if you where facing the same direction as the object) X, Y, Z coordinate of the bounding box.
Line 81:		Line 87:

	=SubObjects=		=SubObjects=
	~~==Name==~~		This shows a list of all the subobjects present in the POF, including the hierarchy.
	~~Description~~		The layout/hierarchy is defined from the source model that you imported into PCS2. You can delete/copy individual subobjects and re-arrange the hierarchy by dragging/dropping subobjets in the navigation pane.
	~~==Rotation Axis==~~
	~~Description~~		Some remarks about the required hierarchy:
	=~~=Offset==~~		*All "parent" objects (= the main model object for each LOD) need to be at the top-level
	~~Description~~		*All debris chunks need to be at the top level
	~~==Properties==~~		*Subobjects that are sub-models (e.g. turrets or any other submodel) need to be children of their respective main model
	~~Description~~		*Turret arms of multi-part turrets needs to be children of their respective turret base, which in turn need to be children of their respective main model
	~~===Draw BSP Debug Info===~~		*Subobjects that represent destroyed versions of a subobject (they have the same name but with "-destroyed" appended) need to be in the same level as their intact counterpart. The game will switch to the -destroyed subobject if the repsective subsystem gets destroyed
	~~Description~~
	~~==Subobject Info==~~		[[File:SubObjects.png]]
	~~===Poly Count===~~
	Description		For each subobject, the below listed values are shown on the right side:
	~~===Child Poly Count===~~		*Name: Description
	Description		*Rotation Axis: Description
	~~===Total===~~		*Offset: Description
	Description		*Bounding Box Min: Description
	~~===~~Bounding Box Min~~===~~		*Bounding Box Max: ooo
	Description		*Max Radius: ddd
	~~===~~Bounding Box Max~~===~~		*Properties: Description
	~~Description~~		*Subobject Info: Shows stats about the geometry of this subobject
	~~===~~Radius~~===~~
	Description
	~~===Parent submodel===~~
	~~Description~~

	=Textures=		=Textures=

Col. Fishguts at 18:07, 2 January 2022

2022-01-02T18:07:00Z

← Older revision		Revision as of 18:07, 2 January 2022
Line 31:		Line 31:
	Note that the game only checks for weapon collisions with the model inside the bounding box. Model geometry outside of the bounding box is ignored (becoming non-shootable).		Note that the game only checks for weapon collisions with the model inside the bounding box. Model geometry outside of the bounding box is ignored (becoming non-shootable).
	PCS2 automatically calculates this value based on the min/max dimensions of the parent object (detail0). So the problem of non-shootable geometry only applies to SubObjects that protrude outside of the bounding box.		PCS2 automatically calculates this value based on the min/max dimensions of the parent object (detail0). So the problem of non-shootable geometry only applies to SubObjects that protrude outside of the bounding box.

	The values can be edited/saved if needed. Use the "Reset" button to recalculate the value based on model geometry.		The values can be edited/saved if needed. Use the "Reset" button to recalculate the value based on model geometry.

Line 39:		Line 40:
	This is the maximum distance between any point on the craft and the craft's center. <!-- center of mass? pivot point? -->		This is the maximum distance between any point on the craft and the craft's center. <!-- center of mass? pivot point? -->
	It is used to determine ship-to-ship collisions for small craft (where model geometry is ignored).		It is used to determine ship-to-ship collisions for small craft (where model geometry is ignored).
	PCS2 automatically calculates this value based on model geometry. The values can be edited/saved if needed. Use the "Reset" button to recalculate the value based on model geometry.		PCS2 automatically calculates this value based on model geometry.

			The values can be edited/saved if needed. Use the "Reset" button to recalculate the value based on model geometry.

	==Mass==		==Mass==
Line 52:		Line 55:
	From the POF data notes: "mass is an area mass conversion: area_mass=4.65(vol_mass^2/3); also scale moment_inertia by vol_mass/area_mass () if there is no cross_section data, num_cross_sections is -1 instead of 0, as one would expect."		From the POF data notes: "mass is an area mass conversion: area_mass=4.65(vol_mass^2/3); also scale moment_inertia by vol_mass/area_mass () if there is no cross_section data, num_cross_sections is -1 instead of 0, as one would expect."
	==LOD==		==LOD==
	~~===~~Select~~===~~		Define Level-of-detail models from LOD1 (used up close) to LOD4 (used far away). Define/edit the number of LOD levels with the new/edit/delete buttons in the "Select" list.
	~~Description~~		Volition models have 4 LODs as standard, but you can use less (with fs2_open also more) than that.
	~~===~~Model#~~===~~		*Select: Define/edit the number of LOD levels with the New/Copy/Delete buttons, select a particular LOD level from the drop-down list
	~~Description~~		*Model#: Select the corresponding subobject in the drop-down list
			If your model naming scheme follows the PCS2 standard (detail0 for LOD1, detail1 for LOD2, detail2 for LOD3, detail3 for LOD4) PCS2 will automatically assign the subobjects to the respective LOD level. The suboject names can be anything (as seen when looking at Volition POFs), the standard naming is only a shortcut to let PCS2 do the LOD assignment automatically during model import.
			Note that the distance at which the LOD changes is defined in ships.tbl
	==Debris==		==Debris==
	~~===~~Select~~===~~		Define debris chunk models (which are spawned when the ship is destroyed).
	~~Description~~		*Select: Define/edit the number of debris chunks with the New/Copy/Delete buttons, select a particular debris chunk from the drop-down list
	~~===~~Model#~~===~~		*Model#: Select the corresponding subobject in the drop-down list.
	~~Description~~		If your model naming scheme follows the PCS2 standard (debris01, debris02, etc.) PCS2 will automatically assign them as debris chunks.
	==Cross Sections==		==Cross Sections==
	~~===Select===~~		A list of points used to scale the explosion effects during the death-roll/explosion animation of capital ships.
	~~Description~~		Each point has a "Depth" value and a "Radius" value.
	~~===~~Radius~~===~~		*Depth corresponds to the coordinate in the Z-axis
	~~Description~~		*Radius corresponds roughly to the ship radius (measured from the Z-axis) at that depth value
	==~~=Depth=~~==		Volition POFs of capital ships typically have a list of 25 cross-section values.
	~~Description~~		Note that if this is not set, the game will use default values instead.
	~~==Moment~~ of ~~Intertia=~~=		==Moment of Inertia==
			A symmetrical 3x3 matrix that defines the moment of inertia (or rotational inertia) for an object. This defines how much torque is needed for a desired angular acceleration about a rotational axis. This property is given by the shape and mass of an object (specifically by how much mass is located how far away from a given rotation axis), see also https://en.wikipedia.org/wiki/Moment_of_inertia

			In FS2 this is used for physics calculations when ships are hit by beam weapons. Beams impart a force that "pushes" on a ship, and if the beam does not hit exactly the center of a ship, this force creates a torque (=moment) on the ship (causing it to rotate). Note that the values seem to define an inverted value for the MOI, meaning that smaller values correspond to higher MOI. Setting all values to 0 results in a POF that does not rotate when hit by beams.

			PCS2 offers the option to "Recalculate" the MOI based on model geometry. And while it claims to not be very good at it, the results are usually usable (but typically lower than on Volition models). If more accurate values are needed, it's best to copy the values from a similarly sized/shaped Volition POF.

	=SubObjects=		=SubObjects=

Col. Fishguts at 18:52, 1 January 2022

2022-01-01T18:52:02Z

Show changes

Z64555: Filled out some of the page. It was just begging for it!

2012-06-15T19:39:09Z

Filled out some of the page. It was just begging for it!

← Older revision		Revision as of 19:39, 15 June 2012
Line 1:		Line 1:
	This is the stub page for the PCS2 Help Cooperative authoring. Please add all pages to the PCS2 Cooperative Authoring category.		----
			:'''''This is the stub page for the PCS2 Help Cooperative authoring. Please add all pages to the PCS2 Cooperative Authoring category.'''''

			:'''''Once this project is finished, it will be exported and included with PCS2 releases as the official help.'''''''
			----


			The POF Constructor Suite 2 (PCS2) allows modification of existing .pof's as well as creation of new ones from OpenCOLLADA .dae's. The geometry, texturing, and UV mapping is done by modeling software such as Blender or 3DSmax, while PCS2 focuses on a process called "rigging."

			There are numerous tutorials on rigging for FSO using PCS2: <!-- list several active tutorials here -->

	~~Once this project is finished, [[User:Kazan\|Kazan]] will export and include it with PCS2 releases as the official help.~~

	=Header=		=Header=
			The Header group contains the LOD and Debris list which points to which model as being the respective LOD and debris (The models themselves are contained in the [[#SubObjects \| SubObjects]] group). The Header group also contains physical values (such as mass and moment of inertia) and other assorted values.
	==Bounding Box Min==		==Bounding Box Min==
	~~Description~~		This is the minimum (i.e. lower rear left-hand corner if you where facing the same direction as the object) X, Y, Z coordinate of the bounding box.

			This value is pre-determined by the modeling software, and cannot be modified in PCS2.
			Units: Meters
	==Bounding Box Max==		==Bounding Box Max==
	~~Description~~		This is the maximum(i.e. upper forward right-hand corner if you where facing the same direction as the object) X, Y, Z coordinate of the bounding box.

			This value is pre-determined by the modeling software, and cannot be modified in PCS2.
			Units: Meters

	==Center of Mass==		==Center of Mass==
	~~Description~~		This value determines the center of mass of the object, and is namely used as a pivot point by the game engine to turn/rotate it during movement and collisions.

			''Format'' <!-- Need a better font formatting here, maybe use a .tbl as a reference? -->

			(float) X, (float) Y, (float) Z
			Units: Meters

	==Max Radius==		==Max Radius==
	~~Description~~		This is the maximum distance between any point on the craft and the craft's center. <!-- center of mass? pivot point? -->

			This value is pre-determined by PCS2, and cannot be modified.

			Units: Meters

	==Radius Override==		==Radius Override==
	Description		Description

SypheDMar: Very Basic (But Much-Needed) Update to this page.

2011-12-03T17:49:49Z

Very Basic (But Much-Needed) Update to this page.

← Older revision		Revision as of 17:49, 3 December 2011
Line 2:		Line 2:

	Once this project is finished, [[User:Kazan\|Kazan]] will export and include it with PCS2 releases as the official help.		Once this project is finished, [[User:Kazan\|Kazan]] will export and include it with PCS2 releases as the official help.

			=Header=
			==Bounding Box Min==
			Description
			==Bounding Box Max==
			Description
			==Center of Mass==
			Description
			==Max Radius==
			Description
			==Radius Override==
			Description
			==Mass==
			Description
			==LOD==
			===Select===
			Description
			===Model#===
			Description
			==Debris==
			===Select===
			Description
			===Model#===
			Description
			==Cross Sections==
			===Select===
			Description
			===Radius===
			Description
			===Depth===
			Description
			==Moment of Intertia==

			=SubObjects=
			==Name==
			Description
			==Rotation Axis==
			Description
			==Offset==
			Description
			==Properties==
			Description
			===Draw BSP Debug Info===
			Description
			==Subobject Info==
			===Poly Count===
			Description
			===Child Poly Count===
			Description
			===Total===
			Description
			===Bounding Box Min===
			Description
			===Bounding Box Max===
			Description
			===Radius===
			Description
			===Parent submodel===
			Description

			=Textures=
			==Select==
			Description
			==Texture==
			Description

			=Weapon Points=
			==Gun Points==
			Description
			===Bank===
			Description
			===Select===
			Description
			==Point==
			===Select===
			Description
			===Point===
			Description
			===Normal===
			Description
			==Missile Points==
			Description
			===Bank===
			Description
			===Select===
			Description
			==Point==
			===Select===
			Description
			===Point===
			Description
			===Normal===
			Description

	{{Stub}}		{{Stub}}

BlueFlames: Catagorizing & grammar.

2009-03-09T02:42:15Z

Catagorizing & grammar.

← Older revision		Revision as of 02:42, 9 March 2009
Line 1:		Line 1:
	This is the stub ~~start~~ page for the PCS2 Help Cooperative authoring.~~.. please create~~ all pages ~~in POFCS2Help/<pagename>~~		This is the stub page for the PCS2 Help Cooperative authoring. Please add all pages to the PCS2 Cooperative Authoring category.

	~~once~~ this project is ~~done and arranged I~~ will export ~~this all~~ and include it with PCS2 releases as the official help.		Once this project is finished, [[User:Kazan\|Kazan]] will export and include it with PCS2 releases as the official help.

	~~Pages~~:		{{Stub}}
	[[~~POFCS2Help/BlenderToPOFConversions~~]]
			[[Category:Modding]]
			[[Category:PCS2 Cooperative Authoring]]

Kazan at 16:15, 8 March 2009

2009-03-08T16:15:06Z

← Older revision		Revision as of 16:15, 8 March 2009
Line 2:		Line 2:

	once this project is done and arranged I will export this all and include it with PCS2 releases as the official help.		once this project is done and arranged I will export this all and include it with PCS2 releases as the official help.

			Pages:
			[[POFCS2Help/BlenderToPOFConversions]]