setting a base delay factor causes my game to crash in 3.1.1

[ledcraft]

has this been fixed?

[d_m]

I believe this is fixed; you should try it out and see!

[Derakon]

I certainly haven't had any issues with delay factors...well, ever! You should try 3.1.2v2, which is the latest stable version (ignore the "beta" label). If you're still having trouble you should let us know what system you have.

[buzzkill]

I think this came up once before. Making a large change in the setting can make the game appear to 'hang'. Did it crash or just become non-responsive?

[Nomad]

I think this came up once before. Making a large change in the setting can make the game appear to 'hang'. Did it crash or just become non-responsive?

Yeah, that happened to me. I was setting it to run extra slow so I could test out some tile designs, and casually assumed it went up linearly when it's actually squared. Set it to 255 and you end up with 65 seconds between each frame of animation, which seems just a tad excessive. I really think delay_factor should be capped at 63 or even 31 instead - does anyone actually need a frame of animation to hold still for longer than one second?

(Also dangerous: the fact that it doesn't show you that you've set the delay to something stupidly huge unless you hit d to look at it again after you've already confirmed your setting.)

[Derakon]

That latter point is really annoying, especially since it used to tell you what the actual delay was, in milliseconds. The current system is completely opaque to new users. This doesn't help people find out that Angband has animations at all.

(The delay factor should also default to something nonzero; maybe 4ms)