Grimrock

zimberzimber wrote:Attaching a model to a node for monsters with scaled down animations scales down the attached model, but the parent mesh gets resized to its original state
Rescaling models didn't help fixing it

minmay wrote:

zimberzimber wrote:Attaching a model to a node for monsters with scaled down animations scales down the attached model, but the parent mesh gets resized to its original state
Rescaling models didn't help fixing it

Can you rephrase that? I don't know what you are saying here. Do you mean that using the parentNode property on a ModelComponent is changing the parent model somehow?

zimberzimber wrote:scripts set the stairs to their location, stairs have invisible models and a custom location. However, I assume this'll be problematic if a player is to save/load a game.

Biggest issue is the stairs killing pillars/floors/ceiling.
Floor isn't a problem, can be added to the stairs up as their model, and set the material based on what you need,
Placing ceilings manually works fine.
Pillars though... I have no idea how to fix em without a custom model. I tried using a high pillar and just place them below/above the required location, but placing the upper one didn't work because it got removed by stairs_down. An impractical fix would be editing a pillars model to look like its where you need it, but its real location is on a lower height.

defineObject{
	name = "stairs_up_open_double_pillar",
	baseObject = "base_wall_decoration",
	components = {
		{
			class = "Model",
			model = "assets/models/env/dungeon_pillar.fbx",
			staticShadow = true,
			offset = vec(-1.5,0,0),
		},
		{
			class = "Model",
			name = "pillar2",
			model = "assets/models/env/dungeon_pillar.fbx",
			offset = vec(1.5,0,0),
			staticShadow = true,
		},
	},
	minimalSaveState = true,
	replacesWall = false,
}

nice trick with placing the stairs elsewhere, but I prefer using a wall decoration, and have the stairs placed and shown at his exact position.

For the pillars, I use some double pillars object defined as a wall_decoration:
its based on dungeon pillars model, so no new model, only a new object, with offset that pop them on each side of the wall.

bongobeat wrote:is there anything wrong with performance or something else if I put an occcluder on a wall decoration?

zimberzimber wrote:I have an ogre, that uses scaled down animations. (Like the micro ogres someone made for LoG1)
Attaching a model to a node on the model causes the attached model become smaller, and the model that gets the attachment becomes biger (normal sized)

minmay wrote:

zimberzimber wrote:I have an ogre, that uses scaled down animations. (Like the micro ogres someone made for LoG1)
Attaching a model to a node on the model causes the attached model become smaller, and the model that gets the attachment becomes biger (normal sized)

Okay, I see what you are saying, but I cannot reproduce the issue. I tried attaching a ModelComponent to a scaled node that has mesh data, and the node retained its scale. I think there's something funny about your animation. You aren't scaling local_srt or something like that are you?

Isaac wrote:In Blender, Import the ogre, select the armature, import the animation.

Change the pivot to the cursor
Center the cursor ( <shift> + S )
Then select the game_matrix object, and scale it down.
Then press <CRTL> + A to apply scale.

https://www.dropbox.com/s/r14f98w0flrhk ... k.avi?dl=0