LOD - Revision history

Lou Montana: Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

2024-02-01T23:24:49Z

Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

← Older revision		Revision as of 01:24, 2 February 2024
Line 74:		Line 74:
	Geometry objects should have a thickness of at least 0.5 meters in order to work properly.		Geometry objects should have a thickness of at least 0.5 meters in order to work properly.

	{{Feature\|~~Informative~~\|Oxygen2/Objectbuilder can do ComponentXX naming automatically. [Structures->Topology->Find Components]}}		{{Feature\|informative\|Oxygen2/Objectbuilder can do ComponentXX naming automatically. [Structures->Topology->Find Components]}}

	'''{{arma3}}:'''		'''{{arma3}}:'''
Line 94:		Line 94:
	For tanks or other vehicles with turrets/ large cannons it is best practice not to include the cannon barrel or long protruding turret parts in the PhysX LOD. The rotation of turrets is not limited by forces, therefore the collision of a barrel with the environment will cause the tank or other PhysX objects to move (often very violently, causing serious glitches and flying tanks).		For tanks or other vehicles with turrets/ large cannons it is best practice not to include the cannon barrel or long protruding turret parts in the PhysX LOD. The rotation of turrets is not limited by forces, therefore the collision of a barrel with the environment will cause the tank or other PhysX objects to move (often very violently, causing serious glitches and flying tanks).

	{{Feature\|~~Informative~~\|		{{Feature\|informative\|
	* Requires Objectbuilder to be selectable in the LOD list. Oxygen2 does not have this capability.		* Requires Objectbuilder to be selectable in the LOD list. Oxygen2 does not have this capability.
	* {{GVI\|arma3\|1.00\|size= 0.75}} Grenades are currently PhysX objects, that means they do use this LOD instead of Fire Geometry.		* {{GVI\|arma3\|1.00\|size= 0.75}} Grenades are currently PhysX objects, that means they do use this LOD instead of Fire Geometry.
Line 162:		Line 162:
	[[Named Selection]]s that are used to define lights, vehicle entry points, etc., as well as control points for [[Animations]].		[[Named Selection]]s that are used to define lights, vehicle entry points, etc., as well as control points for [[Animations]].

	{{Feature\|~~Informative~~\|For memorypoint creation in an external modelling tool that has no export plugin, you can create a triangle in the external modeller. Place one or two vertices of the triangle where you need them. Import the triangle(s) into Oxygen2/Objectbuilder. Delete the obsolete point(s) of the triangle.}}		{{Feature\|informative\|For memorypoint creation in an external modelling tool that has no export plugin, you can create a triangle in the external modeller. Place one or two vertices of the triangle where you need them. Import the triangle(s) into Oxygen2/Objectbuilder. Delete the obsolete point(s) of the triangle.}}

	You can animate Memory LOD Selections via model.cfg just like any ordinary LOD. However, it is not guaranteed that this will work for the thing you intent to. Particles for example ignore animated memorypoints, they always use the default position from Objectbuilder. Same holds true for gun/cannon Memorypoints on vehicle turrets. Vehicle Reflector class lights however do animate properly.		You can animate Memory LOD Selections via model.cfg just like any ordinary LOD. However, it is not guaranteed that this will work for the thing you intent to. Particles for example ignore animated memorypoints, they always use the default position from Objectbuilder. Same holds true for gun/cannon Memorypoints on vehicle turrets. Vehicle Reflector class lights however do animate properly.

Lou Montana: Fix typos

2023-12-11T09:33:53Z

Fix typos

Lou Montana: Text replacement - "[[Image:" to "[[File:"

2023-11-20T22:11:33Z

Text replacement - "[[Image:" to "[[File:"

← Older revision		Revision as of 00:11, 21 November 2023
Line 4:		Line 4:
	\| LOD means Level of Detail, and is a method of defining, via different variations of a model, how high or low the viewable quality of the model should be, and how it should interact with the environment.		\| LOD means Level of Detail, and is a method of defining, via different variations of a model, how high or low the viewable quality of the model should be, and how it should interact with the environment.
	Note that having too many (30 or more) LODs in total could cause the binarize process to crash.		Note that having too many (30 or more) LODs in total could cause the binarize process to crash.
	\|style="text-align: right" \| [[~~Image~~:LODs.gif]]		\|style="text-align: right" \| [[File:LODs.gif]]
	\|}		\|}

Line 19:		Line 19:

	Proxies need to be included in every resolution LOD that they should appear in. The proxies switch LOD independantly of the main p3d's resolution LOD however. (Example: Tank has Commander Machinegun as a Proxy - the machinegun may switch to lowest poly LOD before Tank switches from resLOD 0 to resLOD 1).		Proxies need to be included in every resolution LOD that they should appear in. The proxies switch LOD independantly of the main p3d's resolution LOD however. (Example: Tank has Commander Machinegun as a Proxy - the machinegun may switch to lowest poly LOD before Tank switches from resLOD 0 to resLOD 1).
	\| [[~~Image~~:Truck-ResLOD.jpg\|right\|thumb\|160px]]		\| [[File:Truck-ResLOD.jpg\|right\|thumb\|160px]]
	\|}		\|}

Line 56:		Line 56:


	[[~~Image~~:Truck-GeoLOD.gif\|thumb\|150px]]		[[File:Truck-GeoLOD.gif\|thumb\|150px]]
	== Geometry ==		== Geometry ==

Line 212:		Line 212:
	== View - Cargo ==		== View - Cargo ==

	[[~~Image~~:Truck-View-Cargo.jpg\|thumb\|150px]]		[[File:Truck-View-Cargo.jpg\|thumb\|150px]]
	What a cargo passenger can see of the model.		What a cargo passenger can see of the model.

Lou Montana: Text replacement - "seperat" to "separat"

2023-05-25T14:02:20Z

Text replacement - "seperat" to "separat"

← Older revision		Revision as of 16:02, 25 May 2023
Line 192:		Line 192:

	The roadway LOD does not work if components are further away from the center of origin than approximately 36 meters (estimate value, it is dependent on map size/cell size and may be bigger or smaller between terrains).		The roadway LOD does not work if components are further away from the center of origin than approximately 36 meters (estimate value, it is dependent on map size/cell size and may be bigger or smaller between terrains).
	Therefore you can make 72m long bridges at most. If that is not sufficient for your object then you need to split your model into multiple smaller segments with a ~~seperate~~ .p3d modelfile each.		Therefore you can make 72m long bridges at most. If that is not sufficient for your object then you need to split your model into multiple smaller segments with a separate .p3d modelfile each.

	This LOD is used to determine the sound environment effects the player hears. The used environment effect are defined by the texture of the roadway LOD surface the player are standing on. The texture name corresponds to the file="<string>" property in CfgSurfaces classes.		This LOD is used to determine the sound environment effects the player hears. The used environment effect are defined by the texture of the roadway LOD surface the player are standing on. The texture name corresponds to the file="<string>" property in CfgSurfaces classes.

Lou Montana: Text replacement - "\[ (https?:\/\/[^ = ]+) +([^= ]+) \]" to "{{Link|$1|$2}}"

2023-04-28T14:08:29Z

Text replacement - "\[ *(https?:\/\/[^ = ]+) +([^= ]+) *\]" to "{{Link|$1|$2}}"

← Older revision		Revision as of 16:08, 28 April 2023
Line 41:		Line 41:
	To demonstrate the complexity of the LOD selection, and the effect the resolution name has on LOD switching, a series of tests have been documented here: [[Operation_Flashpoint:_Resolution_LOD_Samples\|Resolution LOD Samples]]		To demonstrate the complexity of the LOD selection, and the effect the resolution name has on LOD switching, a series of tests have been documented here: [[Operation_Flashpoint:_Resolution_LOD_Samples\|Resolution LOD Samples]]

	The modelgeometry in each LOD needs to be below a "maximum polygoncount". This "maximum polygoncount" varies depending on how your model looks. The actual limit is based off [http://wiki.polycount.com/wiki/VertexNormal vertex normals]. The total amount of triangles you can use therefore depends on the [http://www.ericchadwick.com/examples/provost/byf2.html#wts Smoothing splits and UV splits] in your model. According to some tests and documentation of DirectX9 the limit appears to be 2^15 = 32768 vertex normals in ArmA, Arma 2 and early Arma 3 (where DirectX9 is used). In a recent (Q1/2016) update, the .p3d format in Arma 3 was updated to version 70 and now has a higher limit (above 2^16 vertex normals). If you exceed the vertex normal limit, loading your model may crash the game or it simply won't display it. You can check it in Objectbuilder by loading up Bulldozer - if the LOD is not displayed, you are above the limit. Modern 3D modelling tools also offer native or user created tools to check the amount of vertex normals. Please remember that this is the absolute maximum you can use - this does not mean you should fully utilize it on every object.		The modelgeometry in each LOD needs to be below a "maximum polygoncount". This "maximum polygoncount" varies depending on how your model looks. The actual limit is based off {{Link\|http://wiki.polycount.com/wiki/VertexNormal\|vertex normals}}. The total amount of triangles you can use therefore depends on the {{Link\|http://www.ericchadwick.com/examples/provost/byf2.html#wts\|Smoothing splits and UV splits}} in your model. According to some tests and documentation of DirectX9 the limit appears to be 2^15 = 32768 vertex normals in ArmA, Arma 2 and early Arma 3 (where DirectX9 is used). In a recent (Q1/2016) update, the .p3d format in Arma 3 was updated to version 70 and now has a higher limit (above 2^16 vertex normals). If you exceed the vertex normal limit, loading your model may crash the game or it simply won't display it. You can check it in Objectbuilder by loading up Bulldozer - if the LOD is not displayed, you are above the limit. Modern 3D modelling tools also offer native or user created tools to check the amount of vertex normals. Please remember that this is the absolute maximum you can use - this does not mean you should fully utilize it on every object.

	{{Feature\|warning\|'''Do not''' just make identical copies of your res LOD. This is pointless, leads to errors and increased model size (→ increased loading time and memory footprint) - and no performance is gained.}}		{{Feature\|warning\|'''Do not''' just make identical copies of your res LOD. This is pointless, leads to errors and increased model size (→ increased loading time and memory footprint) - and no performance is gained.}}

Lou Montana: Text replacement - "{{ExternalLink|" to "{{Link|"

2023-01-04T15:23:14Z

Text replacement - "{{ExternalLink|" to "{{Link|"

← Older revision		Revision as of 17:23, 4 January 2023
Line 82:		Line 82:
	* The default [[Named Properties\|Named Properties]] for the Geometry LOD are: {{hl\|1= canocclude = 0}} and {{hl\|1= canbeoccluded = 1}} (for Vehicles, Characters and Weapons)		* The default [[Named Properties\|Named Properties]] for the Geometry LOD are: {{hl\|1= canocclude = 0}} and {{hl\|1= canbeoccluded = 1}} (for Vehicles, Characters and Weapons)

	When creating terrain objects that have to be navigated or used by infantry, it is good to keep the {{~~ExternalLink~~\|link= https://forums.bistudio.com/topic/201408-info-infantry-metrics/\|text= infantry metrics}} in mind.		When creating terrain objects that have to be navigated or used by infantry, it is good to keep the {{Link\|link= https://forums.bistudio.com/topic/201408-info-infantry-metrics/\|text= infantry metrics}} in mind.

Leopard20: fix typo (broken wiki syntax)

2022-03-30T16:26:04Z

fix typo (broken wiki syntax)

← Older revision		Revision as of 18:26, 30 March 2022
Line 96:		Line 96:
	{{Feature\|Informative\|		{{Feature\|Informative\|
	* Requires Objectbuilder to be selectable in the LOD list. Oxygen2 does not have this capability.		* Requires Objectbuilder to be selectable in the LOD list. Oxygen2 does not have this capability.
	* [[GVI\|arma3\|1.00\|size= 0.75}} Grenades are currently PhysX objects, that means they do use this LOD instead of Fire Geometry.		* {{GVI\|arma3\|1.00\|size= 0.75}} Grenades are currently PhysX objects, that means they do use this LOD instead of Fire Geometry.
	}}		}}

Lou Montana: Some wiki formatting + 0..99 → 0..2048 selection limit

2022-02-27T23:25:18Z

Some wiki formatting + 0..99 → 0..2048 selection limit

Show changes

Lou Montana: Add character collision Geometry note thx to exocet & HorribleGoat

2022-01-05T14:48:24Z

Add character collision Geometry note thx to exocet & HorribleGoat

← Older revision		Revision as of 16:48, 5 January 2022
Line 55:		Line 55:
	Should be '''very''' simple, and has to fulfill the following criteria in order to work:		Should be '''very''' simple, and has to fulfill the following criteria in order to work:
	* Object must be [[Named Selection \| named]] ComponentXX (where XX is a consecutive number between 01 and 99).		* Object must be [[Named Selection \| named]] ComponentXX (where XX is a consecutive number between 01 and 99).
	* Must have 'Mass' (Alt-M).		* Must have 'Mass' (Alt-M). A minimum of 10 is required for character collision.
	* Must be closed and convex. Always validate your Geometry LOD. ([[Validating Geometries]]).		* Must be closed and convex. Always validate your Geometry LOD. ([[Validating Geometries]]).
	* Some object types require that every component must have some mass assigned in order to work properly. Does not apply to vehicles.		* Some object types require that every component must have some mass assigned in order to work properly. Does not apply to vehicles.

Lou Montana: Text replacement - "\[ (https?\:\/\/.+\.bistudio\.[^ ]+) ([^ ]+) \]" to "{{ExternalLink|link= $1|text= $2}}"

2021-07-26T12:18:11Z

Text replacement - "\[ *(https?\:\/\/.+\.bistudio\.[^ ]+) ([^ ]+) *\]" to "{{ExternalLink|link= $1|text= $2}}"

← Older revision		Revision as of 14:18, 26 July 2021
Line 75:		Line 75:
	* The default [[Named Properties\|Named Properties]] for the Geometry LOD are: ''canocclude=0'' and ''canbeoccluded=1'' (for Vehicles, Characters and Weapons)		* The default [[Named Properties\|Named Properties]] for the Geometry LOD are: ''canocclude=0'' and ''canbeoccluded=1'' (for Vehicles, Characters and Weapons)

	''When creating terrain objects that have to be navigated or used by infantry, it is good to keep the [https://forums.bistudio.com/topic/201408-info-infantry-metrics/ infantry metrics] in mind''		''When creating terrain objects that have to be navigated or used by infantry, it is good to keep the {{ExternalLink\|link= https://forums.bistudio.com/topic/201408-info-infantry-metrics/\|text= infantry metrics}} in mind''

	<br clear="all">		<br clear="all">

← Older revision		Revision as of 11:33, 11 December 2023
Line 67:		Line 67:
	* It must be smaller than the size limit.		* It must be smaller than the size limit.

	If the geometry LOD is larger ~~then~~ the size limit, it gets glitchy (collision does not work for example and the object may disappear at certain view angles).		If the geometry LOD is larger than the size limit, it gets glitchy (collision does not work for example and the object may disappear at certain view angles).
	The exact value of the limit is not yet known, but it is somewhere around 50-60 meter from the center of origin (meaning that your object can be 100m wide/long at max if it is symmetrical to the center of origin).		The exact value of the limit is not yet known, but it is somewhere around 50-60 meter from the center of origin (meaning that your object can be 100m wide/long at max if it is symmetrical to the center of origin).
	According to reports there is no limit skywards, so you could make a tower of 200m height.		According to reports there is no limit skywards, so you could make a tower of 200m height.
Line 90:		Line 90:

	The same criteria like for the Geometry LOD apply. The difference is that Geometry Phys does not (should not) contain Mass information.		The same criteria like for the Geometry LOD apply. The difference is that Geometry Phys does not (should not) contain Mass information.
	The detail should be even lower ~~then~~ in the Geometry LOD if possible, as PhysX collisions are computationally more expensive.		The detail should be even lower than in the Geometry LOD if possible, as PhysX collisions are computationally more expensive.
	For helicopters, cut the blades and any non critical structures out of the PhysX LOD, otherwise the rotor blades can cause critical failure.		For helicopters, cut the blades and any non critical structures out of the PhysX LOD, otherwise the rotor blades can cause critical failure.
	For tanks or other vehicles with turrets/ large cannons it is best practice not to include the cannon barrel or long protruding turret parts in the PhysX LOD. The rotation of turrets is not limited by forces, therefore the collision of a barrel with the environment will cause the tank or other PhysX objects to move (often very violently, causing serious glitches and flying tanks).		For tanks or other vehicles with turrets/ large cannons it is best practice not to include the cannon barrel or long protruding turret parts in the PhysX LOD. The rotation of turrets is not limited by forces, therefore the collision of a barrel with the environment will cause the tank or other PhysX objects to move (often very violently, causing serious glitches and flying tanks).
Line 133:		Line 133:
	* {{arma3}} has many materials that can be used directly or as base for custom materials, they can be found in "...\arma3\addons\data_f.pbo\penetration\"		* {{arma3}} has many materials that can be used directly or as base for custom materials, they can be found in "...\arma3\addons\data_f.pbo\penetration\"
	* {{arma3}} Plate materials are usually 30mm thick. Armour plate materials are the only ones with different thicknesses.		* {{arma3}} Plate materials are usually 30mm thick. Armour plate materials are the only ones with different thicknesses.
	* The penetration system does not work reliably for modelled plate thicknesses below 10mm. If you want plate thicknesses smaller ~~then~~ 10mm, model firegeometry with at least 10 to 20 mm but apply custom plate materials for decreased thickness.		* The penetration system does not work reliably for modelled plate thicknesses below 10mm. If you want plate thicknesses smaller than 10mm, model firegeometry with at least 10 to 20 mm but apply custom plate materials for decreased thickness.
	* If you have a case where 2 armor plates (or other Firegeometry) are ontop of each other, they should be modelled as 1 piece. Otherwise the second plate might get ignored by a bullet due to close proximity, which is caused by limited bullet simulationstep and therefore limited bullet simulation accuracy. Might be fps dependant.		* If you have a case where 2 armor plates (or other Firegeometry) are ontop of each other, they should be modelled as 1 piece. Otherwise the second plate might get ignored by a bullet due to close proximity, which is caused by limited bullet simulationstep and therefore limited bullet simulation accuracy. Might be fps dependant.
	}}		}}