usePieceCollisionVolumes on features doesn't appear to work

[Forboding Angel]

Ami doinitrong?

Code: Select all

-----------------------------------------------------------------------------
--  Espire1
-----------------------------------------------------------------------------
local featureDef	=	{
	name				= "Espire1",
	blocking			= true,
	category			= "rocks",
	damage				= 4000,
	description			= "Energy Spire",


  energy = 0,
-- energy				= 200,
	flammable			= 0,
	footprintX			= 2,
	footprintZ			= 2,
	height				= "31",
	hitdensity			= "5",
	metal = 0,
--metal				= 10,
	object				= "features/lathan/Espire1.s3o",
	reclaimable			= true,
	autoreclaimable		= true, 	
	world				= "All Worlds",
	usePieceCollisionVolumes = true,
	customparams = { 
		 author 	 = "Lathan", 
		 category 	 = "spire", 
		 set 		 = "Lathan's Energy Spires", 
 
		randomrotate		= "true", 
	}, 
}
return lowerkeys({[featureDef.name] = featureDef})

[8611z]

learn to write report bugs more detailed than "it doesnt work" and learn to read the wiki.

[Forboding Angel]

This is a question, not a bug report. The wiki is unclear as to whether you can use per piece collision volumes on features, hence this thread.

A question... Ya know... Like:

Ami doinitrong?

Surely you can figure that out all on your own, you're a big boy.

[8611z]

"Ami doinitrong?" is not a question but meaningless gibberish if you do not tell what "it" is, what the expected behaviour is, and what happens instead.

The wiki is unclear as to whether you can use per piece collision volumes on features

Now that is almost a proper question.
In wiki two places mention "usePieceCollisionVolumes" and both are pretty clear.
If you habe suspicion that this is a case of docu being inaccurate then you have to give yet more details if it is meant to be taken serious.

[gajop]

Please don't escalate or warnings & more for the both of you.
@forb: What is *not* working? Can you post screenshots when you try /DebugColVol? Are they completely disabled or simply off?
@knorke: Collisions can be confusing (see Gravitas) and they certainly aren't simple in Spring. If you think some posts contain limited info, give a brief answer it deserves and ask for more (see line above). No need to go *bawl* just because forb posted.

[8611z]

and there is another user who did not look at wiki.

[Kloot]

If you think some posts contain limited info, give a brief answer it deserves and ask for more

Nah, the only answer that zero-effort threads generally deserve is a lock. The onus is not on readers to slowly extract more info post by post.

collisions ... certainly aren't simple in Spring

While most times you indeed have to be very specific about what you mean by "collision" since it can refer to multiple types of object interaction that are not uniformly handled, the wiki contains more than enough clear information (certainly for someone with self-proclaimed reading comprehension level over 9000) to infer the answer to *this* question, and experience has shown it is useless to give a straight one to *this* poster anyway.

[FLOZi]

Doesn't apply to features, hence missing in wiki page.

Isn't readily changeable, either; https://github.com/spring/spring/blob/1 ... r.cpp#L102

Goodnight.

[FLOZi]

P.S. kloot doesn't understand the meaning of "Isn't readily changeable"

https://github.com/spring/spring/commit ... c1162e674b