Cluttered objects

[Linker Split 0]

The topic name speaks itself:

I want to add for example my custom rocks via clutters, but GEO is not working.

How to have Geo working like BIS rocks?

please help.

I thought it was a problem of binarizing, since my models are MLOD.

Btw, my generic rock has this specs:

Quote[/b] ]RES LOD 0.000

RES LOD 0.100

RES LOD 1.000

RES LOD 2.000

RES LOD 3.000

RES LOD 4.000

SHADOW LOD 0.000

SHADOW LOD 10.000

GEOMETRY LOD (model convexed and with mass applied) with named properties:

class rock

dammage no

FIRE GEOMETRY LOD (model convexed)

[fasad 1]

The BIS clutter doesn't use any geo/fire. I'm quite sure this is an engine limitation (performance). Maybe ask one of the devs?

[Linker Split 0]

Sorry, wrong post

thanks Fasad for telling me

[fasad 1]

I don't really see the relevance of that?

Does your object's geometry work correctly when it is placed as a normal object?

[Linker Split 0]

I don't really see the relevance of that?

Does your object's geometry work correctly when it is placed as a normal object?

Of copurse yes, everything is fine... me and deanosBeano are making some researches...

now I'm trying to define the rock with the suffix clutter_

[fasad 1]

Okay, I guess I should re-phrase my post then: I believe that the ArmA engine does not use any geo/fire for clutter objects, even if the clutter objects have valid geo/fire LODs.

[Linker Split 0]

Okay, I guess I should re-phrase my post then: I believe that the ArmA engine does not use any geo/fire for clutter objects, even if the clutter objects have valid geo/fire LODs.

Ok, I got it, but I'm wondering if there's a way to have rocks working correctly if placed in Visitor (cause as you said, they have GEO not working while BIS ones yes)