Help:VE189 - Revision history

Pcas1986: Added link to HowTo/Configure a spline for collsions

2026-09-05T03:36:36Z

Added link to HowTo/Configure a spline for collsions

← Older revision		Revision as of 03:36, 5 September 2026
Line 10:		Line 10:

	3. Using the [["mesh-table" container#collision-mesh\|collision-mesh tag]] to specify a separate lower-detail mesh to use for collision purposes. This approach offers the ultimate in manual control at the expense of having to maintain an additional mesh purely for collision purposes.		3. Using the [["mesh-table" container#collision-mesh\|collision-mesh tag]] to specify a separate lower-detail mesh to use for collision purposes. This approach offers the ultimate in manual control at the expense of having to maintain an additional mesh purely for collision purposes.

			'''Additional Help''': See also this article about splines and collision data: [[HowTo/Configure a spline for collisions]]

	[[Category:Validation Errors]]		[[Category:Validation Errors]]

Windwalkr at 03:02, 30 December 2017

2017-12-30T03:02:48Z

← Older revision		Revision as of 03:02, 30 December 2017
Line 1:		Line 1:
	'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.'''		'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.'''

	The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset, and emits undesirable warning messages. ~~The creator should override~~ the [["mesh-table" container#collision-data-generation-mode\|collision generation settings]] for the mesh-table entry in question to select a more efficient method~~, or use~~ the [["mesh-table" container#collision-mesh\|collision-mesh tag]] to specify a lower-detail mesh to use for collision purposes.		The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset, and emits undesirable warning messages.

			Resolving this message may involve one or more of:

			1. Lowering the amount of detail in the mesh in question. If this can be achieved without degrading the visual quality of the asset, then this is a win both from the perspective of removing the collision data problems, and also from the perspective of rendering performance. This approach is not recommended if visual detail needs to be sacrificed.

			2. Overriding the [["mesh-table" container#collision-data-generation-mode\|collision generation settings]] for the mesh-table entry in question to select a more efficient method. This is suitable in scenarios where a simplified collision data technique can be used on the mesh without compromising physical responses (such as PFX collisions) to any significant degree. This does not have any effect on the visuals.

			3. Using the [["mesh-table" container#collision-mesh\|collision-mesh tag]] to specify a separate lower-detail mesh to use for collision purposes. This approach offers the ultimate in manual control at the expense of having to maintain an additional mesh purely for collision purposes.

	[[Category:Validation Errors]]		[[Category:Validation Errors]]

Windwalkr at 02:54, 30 December 2017

2017-12-30T02:54:35Z

← Older revision		Revision as of 02:54, 30 December 2017
Line 1:		Line 1:
	'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.'''		'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.'''

	The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset. The creator should override the collision generation settings for the ~~asset~~ to select a more ~~appropriate~~ method.		The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset, and emits undesirable warning messages. The creator should override the [["mesh-table" container#collision-data-generation-mode\|collision generation settings]] for the mesh-table entry in question to select a more efficient method, or use the [["mesh-table" container#collision-mesh\|collision-mesh tag]] to specify a lower-detail mesh to use for collision purposes.

	[[Category:Validation Errors]]		[[Category:Validation Errors]]

Windwalkr at 00:15, 11 October 2017

2017-10-11T00:15:16Z

← Older revision		Revision as of 00:15, 11 October 2017
Line 2:		Line 2:

	The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset. The creator should override the collision generation settings for the asset to select a more appropriate method.		The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset. The creator should override the collision generation settings for the asset to select a more appropriate method.

			[[Category:Validation Errors]]

Windwalkr: Created page with "'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.''' The asset contains complex geometry for which th..."

2017-10-11T00:14:53Z

Created page with "'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.''' The asset contains complex geometry for which th..."

New page

'''Collision data exceeds 64KB and has been simplified. Consider using a different generation method or a simplified mesh.'''

The asset contains complex geometry for which the selected (or default) collision geometry generation technique generated excessively complex results. This would increase memory usage and decrease performance, and as such is prevented by the game- a simplified collision geometry is used instead. This may be harmless, but it also may result in collision detection behaviour from differing from the creator's expectations. Either way, it costs unnecessary performance when installing or validating the asset. The creator should override the collision generation settings for the asset to select a more appropriate method.