Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[agatharchides]

I've got a setup where I use doors to slow down FB's while they munched by a repeating spike field. The first 3 it polished off with no trouble, but on the forth it cuts my FPS roughly in half whenever the FB is first hit and it doesn't go up even when it is dead and its corpse atom-smashed. I've save-scummed to generate probably 10 FB's and it works the same way each time even with totally different beasts. I'm very much at a loss and wonder if this is some sort of bug. I hate to abandon the fort I have worked on for weeks but the difference between nearly 40 and barely 15 FPS is pretty severe. Any ideas? 

[Krelos]

It's clearly some sort of bug yes, but as to how to fix it... my only suggestion is to get Runesmith and use its ability to kill it as soon as the creature appears (no corpse or blood is left from this) and see if that prevents the FPS loss.

[agatharchides]

I dealt with it by walling off the cavern layer it was in, but I'll try that since I'd sooner be able to go there. Should I upload a save for bugfixing purposes before I get rid of it or would it not be worthwhile for something so rare?

[Uristocrat]

I've got a setup where I use doors to slow down FB's while they munched by a repeating spike field. The first 3 it polished off with no trouble, but on the forth it cuts my FPS roughly in half whenever the FB is first hit and it doesn't go up even when it is dead and its corpse atom-smashed. I've save-scummed to generate probably 10 FB's and it works the same way each time even with totally different beasts. I'm very much at a loss and wonder if this is some sort of bug. I hate to abandon the fort I have worked on for weeks but the difference between nearly 40 and barely 15 FPS is pretty severe. Any ideas? 

Maybe it has some kind of deadly blood or dust or something like that?  I'd run dfcleanmap after killing it and see if you get your FPS back.

[Funburns]

Doors are known to cause some FPS issues due to pathing, though this particular bug may not have to do with that. Have you tried removing the doors after the beast died? Using dfcleanmap is another thing to test, as mentioned.

When you said:

The first 3 it polished off with no trouble, but on the forth it cuts my FPS roughly in half whenever the FB is first hit and it doesn't go up even when it is dead and its corpse atom-smashed.

Do you mean that, when the FB was knocking down the first three doors, it was not being hit by spikes? "... whenever the FB is first hit" - by spike traps when it reached the fourth door? If just being spike trapped is causing the freeze, that implicates different game mechanics than if instead it's a particular set of door(s) and spike trap(s).

[agatharchides]

Sorry, it was late and I was probably unclear. I meant I had killed 3 FB's before without incident. The doors destroyed seem to be unimportant.

Spoiler (click to show/hide)

Is what it looks like, except that where the wall plugging it is there used to be 2 doors. In my save-scumming I've killed FB's before they knocked down the first door and after they got the first two with no apparent difference. I am pretty sure it is the spike traps hitting the beast that are the culprit.