So I made a few stacks of boxes (all one box type)
and sometimes the player will collide with the boxes (and sometimes not)
actually usually not. I never stacked up a bunch of boxes before much,
so I don't know if anyone else can pinpoint this anomaly?

All the setting are the same on the box, I don't know the collision shape,
but the box is >Boxes / 'wooden crate Reskin B'.
Is Immobile = yes
Physics on = yes

Are you saying you made a stack of boxes as one model and imported it as a single entity? Or are you stacking lots of one entity within Game Guru to make the stack?

What does the collisionmode in the fpe say? Here are what the collision modes are (courtesy of T-Bone):

0 = box shape (default)
1 = polygon shape
2 = sphere
3 = cylinder
9 = convex hull reduction shape
11 = no physics
12 = no physics but can still be detected with IntersectAll command
21 = player repel feature (for characters and other beasts/zombies)
40 = collision boxes (defined in Import Model feature)
41-49 = reserved (collision polylist, sphere list, cylinder list)
50 = generate obstacle and cylinder from 1/64th up from base of model
51 = generate obstacle and cylinder from 1/32th down from base of model
52 = generate obstacle and cylinder from 8/16th up from base of model
53 = generate obstacle and cylinder from 7/16th up from base of model
54 = generate obstacle and cylinder from 6/16th up from base of model
55 = generate obstacle and cylinder from 5/16th up from base of model
56 = generate obstacle and cylinder from 4/16th up from base of model
57 = generate obstacle and cylinder from 3/16th up from base of model
58 = generate obstacle and cylinder from 2/16th up from base of model
59 = generate obstacle and cylinder from 1/16th up from base of model
1000-2000 = only one limb has collision Box Shape (1000=limb zero,1001=limb one,etc)
2000-3000 = only one limb has collision Polygons Shape (2000=limb zero,2001=limb one,etc)

AE

Yeah, put a whole bunch down singles and stacked and they all work fine here.

I Checked the FPE Settings for the crate, should work out of the box (lol)
- Collision is set to 0, which is correct for a box.
- Material index is 2 which is Metal, should be 3 for wood, but given that they explode is irrelevant

Textures need some tweeaking - super shiny for me. Looks like they just had a bucket of lacquer pored over them
Explosion is pretty cool but not all that realistic tbo.

OldFlak....

Okay, thanks. Must be something strange on my end. I walk right through
them most of the time, and have to find just a perfect spot to get collision.

BTW I noticed many of the PBR in GG now has that lacquer look. I wonder
when or how that project will be complete?

Thats due to the wrong material index being assigned, nothing wrong with GG here. Open the setup.ini and check what number is set to material index. here is the list:

0 = GenericSoft
1 = Stone
2 = Metal
3 = Wood
4 = Glass
5 = Liquid Splashy Wet
6 = Cloth / Flesh / Soft Absorbant (blood effect)
7 = Hollow Drum Metal
8 = Small High Pitch Tin
9 = Small Low Pitch Tin
10 = Silly Material
11 = Marble
12 = Cobble
13 = Gravel
14 = Soft Metal
15 = Old Stone
16 = Old Wood
17 = Shallow Water
18 = Underwater

You will notice that a lot of classics models are set to "glass" for some reason. Easy fix.

I always thought the material just affected it's sound properties?

@DVader: used to be, but since the PBR update it assigns the way the engine interprets how to render it. Its quite neat actually and lets you save on shader maps.

Material index affects PBR visuals, impact sounds and also debris decal emission.

Ah, not been following GG like I used to. These changes passed me by. Sounds a cool addition Never attempted making PBR stuff as Mindtex only supports DNS. Saw a cool looking utility since though that does, so might have another look.

Mindtex 2 does … I just seemed to get that free when they stopped Mindtex ..
Check your library ?

@Wolf
I noticed the other day that even the desert terrain texture ends up looking like glass unless I wind Sun down to zilch. Now I do not think that is down to materialindex, but while I'm on the subject . . .

The shortcut misuse of Materialindex for 3 different purposes is something that really needs to be undone.

It's not neat. Like every other quick fix it just introduces other problems.

Materialsound
Specularity
Emissiontype

are what is needed.

Drat. I am having trouble recreating the glossy terrain now. When (if) I do, I'll post the details.

The reason for glossy terrain is because a specular map hasn't been used and it's using a default, with terrain textures it doesn't have a separate specular map, you have to add it to the alpha channel of the diffuse texture. Some of the older terrain textures from the old 4 texture system didn't get updated so are missing the specular channel.

Ah. Thanks Belidos. I don't suppose there's a list somewhere is there, or a way to identify which ones to avoid?