Grimrock

minmay wrote:You should use world rotation (setWorldRotationAngles) instead of facing.

THOM wrote:I start to understand, but some things are still uncertain:

In your egsample, Isaac, "spinner" ist the ID, yes? i.e. "altar_1"

But what is "anim_1"?

And BTW is ist possible to call/replace a material of a model, that consists of more than one material?
In an objectdefinition you can use "material = "xyz"", but what, if you want to exchange just one of two materials in use? Or if you want to spin it in this case here.

-- Animation script, called by a timer to update position.


-- I used the castle_floor_01, scaled up via GMT; with texture assigned in the model; renamed to castle_floor_02.

spinner:setPosition(spinner.x, spinner.y,0,-0.19,1)


--spinner.model:setMaterial("vortex") -----------Optional if not specified in the model file.
x = 0


function ersatzAnimator()
	x=x-1%360
	spinner:setWorldRotationAngles(0, x, 0)
end

defineObject{
	name = "castle_floor_02",
	baseObject = "base_floor",
	components = {
		{
			class = "Model",
			model = "mod_assets/models/env/vortex.fbx",
			staticShadow = true,
		},
		{
			class = "Occluder",
			model = "mod_assets/models/env/vortex.fbx",
		},
		
		{
			class = "Platform"
		},
		
		
	},
	minimalSaveState = true,
}

defineMaterial{
	name = "vortex",
	diffuseMap = "mod_assets/textures/vortex.tga",
	--specularMap = "mod_assets/textures/vortex_spec.tga",
	--normalMap = "mod_assets/textures/vortex_norm.tga",
	doubleSided = false,
	lighting = false,
	alphaTest = false,
	blendMode = "Translucent",
	textureAddressMode = "Wrap",
	glossiness = 60,
	depthBias = 0,
}

Isaac wrote:

minmay wrote:You should use world rotation (setWorldRotationAngles) instead of facing.

Even better, but are you sure it does not use the same thing under the hood? Though the Facing method also works with LoG1, unlike setWorldRotationAngles. Also, you have to change the increment from 0.02%4 to 1%360

Isaac wrote:

Code: Select all

function ersatzAnimator()
   x=x-1%360
   spinner:setWorldRotationAngles(0, x, 0)
end

function ersatzAnimator()
   x=(x-60*Time.deltaTime())%360
   spinner:setWorldRotationAngles(0, x, 0)
end

minmay wrote:

Isaac wrote:

minmay wrote:You should use world rotation (setWorldRotationAngles) instead of facing.

Even better, but are you sure it does not use the same thing under the hood? Though the Facing method also works with LoG1, unlike setWorldRotationAngles. Also, you have to change the increment from 0.02%4 to 1%360

It does not use the same thing under the hood, and this is easily testable. Setting facing to a non-integer value sets the GameObject's facing field to a non-integer value. Changing the object's world rotation (really just changing its transformation matrix) does not.

I'm pretty sure non-integer facing will screw up around half the components in the game; in general I would strongly recommend you avoid using non-integer values for x, y, facing, elevation, and level. Almost everything useful you can accomplish with non-integer values in those can be accomplished much better by using world coordinates or subtileOffset instead.

Isaac wrote:

Code: Select all

function ersatzAnimator()
   x=x-1%360
   spinner:setWorldRotationAngles(0, x, 0)
end

This is a terrible way to do it, the rotation speed will then depend on the framerate (also that modulo operation will do nothing since 1%360 always evaluates to 1). Do this instead:

Code: Select all

function ersatzAnimator()
   x=(x-60*Time.deltaTime())%360
   spinner:setWorldRotationAngles(0, x, 0)
end

Then the speed will be framerate independent.

Isaac wrote:*How does it always evaluate to 1? When I test it, it always evaluates to 360 minus x, and the texture rotates just fine.

Isaac wrote:I'd only use it for facing, which seems to work fine in both games ~for decorations. I certainly wouldn't use it for a monster, or interactive object. It'll crash if used on the party ~and the player tries to interact with anything.

Isaac wrote:Cool, I will use it then... But how would this affect the animation in a room that caused markedly different frame-rates depending on where you looked? (Meaning smoothed, or choppy increments?)

minmay wrote:...

THOM wrote:And BTW is ist possible to call/replace a material of a model, that consists of more than one material?
.

         class = "Model",
			model = "assets/models/env/forest_blocker_stone.fbx",
			materialOverrides = { ["forest_wall"] = "sx_winter_forest_wall", ["vegetation_atlas"] = "sx_winter_vegetation_atlas" },
			staticShadow = true,
			dissolveStart = 5,
			dissolveEnd = 7,

Skuggasveinn wrote: materialOverrides = { ["forest_wall"] = "sx_winter_forest_wall", ["vegetation_atlas"] = "sx_winter_vegetation_atlas" },