Grimrock

Ok thanks!

Hello all. Quick question about the momentum of thrown objects through teleporters. I have a teleporter set up with a script that moves the teleport target location every second or so as part of a puzzle. But the momentum of items thrown through is finicky. Throwing weapons (like shuriken) work fine (as do missile weapons), but other items thrown manually with the mouse just plop the item on the floor at the teleporter target's exact location when thrown through - the momentum isn't maintained. The puzzle can still be solved with throwing weapons/missile weapons as I mentioned, but it seems a bit buggy that manually thrown items don't work. Is this normal? Is there a way to fix it? Aside from this everything works fine so its not game-breaking, it just looks like something isn't working right. Cheers.

Can anyone explain why the torch light goes through walls on the following picture? (but not pillars!)
Is there a way to fix it?

Two possibilities:
1. The ModelComponent for the wall the torch is on is missing staticShadow = true (or, less likely, the model or material has shadow casting disabled entirely)

2. The models are set up fine, but the light source is too close to the wall the torch is on -> shadowmap doesn't catch that wall (its resolution is too low) -> shadowmap doesn't catch the other wall because the triangles are one-sided -> light makes it through both walls without casting a shadow. The pillar has some distance from the light source, so it shows up in the shadowmap.

Judging by the shadow of the pillar, it looks like the light source has decent distance from the wall, so it's probably option 1.

Thanks! I found my mistake from those clues; in fact I merged the torch and wall definitions in one object for convenience. Doing this excludes the object itself from the shadow map calculation... I fixed it by spawning a separate wall object at the torch object initialisation instead!

AndakRainor wrote:Thanks! I found my mistake from those clues; in fact I merged the torch and wall definitions in one object for convenience. Doing this excludes the object itself from the shadow map calculation... I fixed it by spawning a separate wall object at the torch object initialisation instead!

Now I'm curious, because that shouldn't make a difference. Can I see the original object definition?

the old one: the new one (fixes light through walls): That said, I have seen it next to secret doors, and it looks like the light does not update when the secret door opens. I guess it comes from staticShadows = true ?

please can someone explain how to increase damage of a projectile with its base magic skill? I want that the projectile gain 25% damage for each arcane skill.

I've tried with but that don't work, the tiledamager is not recognized trough the projectile.

here is the spell:

AndakRainor wrote:the old one:

Code: Select all

defineObject{
  name = "ud_wall_torch",
  baseObject = "base_wall",
  components = {
    {
      class = "Model",
      model = "mod_assets/vb/models/models_under_d/env/ud_wall_torch.fbx",
      staticShadow = true,
    },
    {
      class = "Light",
      offset = vec(0, 1.4, -0.42),
      range = 8,
      color = vec(1.3, 0.68, 0.35),
      brightness = 3,
      castShadow = true,
      shadowMapSize = 64,
      staticShadows = true,
      staticShadowDistance = 0, -- use static shadows always
      onUpdate = function(self)
        local noise = math.noise(Time.currentTime()*3 + 123) * 1 + 1.5
        self:setBrightness(noise * 6)
      end,
    },
    {
      class = "Particle",
      particleSystem = "ud_fire02",
      offset = vec(0, 1.2, -0.42),
    },
    {
      class = "Sound",
      sound = "ud_fire_small",
    },
    {
      class = "Model",
      name = "wall",
      model = "mod_assets/vb/models/models_under_d/env/ud_wall01_a.fbx",
      staticShadow = true,
      onInit = function(self)
        local tab = {"a", "b", "c"}
        self:setModel("mod_assets/vb/models/models_under_d/env/ud_wall01_"..tab[math.random(#tab)]..".fbx")
      end,
    },
    {
      class = "Occluder",
      model = "assets/models/env/dungeon_wall_01_occluder.fbx",
    },
  },
  editorIcon = 84,
  minimalSaveState = true,
  tags = { "VB","Under Dungeon" },
}

the new one (fixes light through walls):

Code: Select all

defineObject{
  name = "ud_wall_torch",
  baseObject = "base_wall",
  components = {
    {
      class = "Model",
      model = "mod_assets/vb/models/models_under_d/env/ud_wall_torch.fbx",
      staticShadow = true,
      onInit = function(self)
        local tab = {"a", "b", "c"}
        self.go:spawn("ud_wall01_"..tab[math.random(#tab)])
      end,
    },
    {
      class = "Light",
      offset = vec(0, 1.4, -0.42),
      range = 8,
      color = vec(1.3, 0.68, 0.35),
      brightness = 3,
      castShadow = true,
      shadowMapSize = 64,
      staticShadows = true,
      staticShadowDistance = 0, -- use static shadows always
      onUpdate = function(self)
        local noise = math.noise(Time.currentTime()*3 + 123) * 1 + 1.5
        self:setBrightness(noise * 6)
      end,
    },
    {
      class = "Particle",
      particleSystem = "ud_fire02",
      offset = vec(0, 1.2, -0.42),
    },
    {
      class = "Sound",
      sound = "ud_fire_small",
    },
  },
  editorIcon = 84,
  minimalSaveState = true,
  tags = { "VB","Under Dungeon" },
}

That said, I have seen it next to secret doors, and it looks like the light does not update when the secret door opens. I guess it comes from staticShadows = true ?

Yep. The shadow map only gets recomputed when the party is closer to the light than the staticShadowDistance, which for this light is 0, so it'll update once when the LightComponent first updates (and after every reload) and otherwise won't.
In your original definition, the wall ModelComponent appears after the LightComponent, which means it'll be created after the LightComponent, and I guess the LightComponent is updating before that happens. The new definition has the wall model created prior to the LightComponent, so it fixes this issue, but I think simply moving the wall ModelComponent up in the original definition would also work.

Oh I did not think about the order! And I just realize now that this is a minimalSaveState object, so the new code will spawn many walls XD

@bongobeat: you could look at objects.lua in the spells pack to see how I solved this.