Print

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

[AW]

I left the game running when I went to bed.  When I checked it this morning it was paused after a miner found some topaz(alite?)  

For some reason the keyboard was only partly operating, escape didn't work, and the arrow keys only worked left and down, not right and up.  Some keys worked, some keys didn't.

I hit ctrl-alt-delete and it brought up the menu, I saved and exited and got back in with no problems, so whatever it was didn't get saved.

I'll note that I'm running XP and it automatically switched to the entry mode it uses when you come back from screen saver.  I was running in full-screen.

[Toady One]

Entry mode?  I'm on XP, but I don't have a screen saver.  Is that something odd?  But yeah, I'm assuming DF doesn't handle them very well.  Looking at it, DF is supposed to prevent screensavers, I think, but I guess that doesn't work.

[numerobis]

quote:Originally posted by Toady One:
<STRONG>DF is supposed to prevent screensavers, I think, but I guess that doesn't work.</STRONG>

Yeah; doesn't work for me on XP / parallels / OSX (as in, the XP VM puts up a screensaver after a while).  It also doesn't crash for me, though -- just stops DF from running.

[Javewa]

Are you using a Logitech keyboard or mouse and have SetPoint installed?

I had Z-up/-down mapped on special keys (Zoom+/-) via SetPoint and UberOptions and DF/SetPoint would occasionally go haywire. In my case, ESC, Enter and Space would cease to function. Only way to fix this was killing SetPoint.exe at the Task Manager or pressing CapsLock/NumLock at random. Not using the special keys works fine, though.

That was 33g, though, and I blamed SetPoint because it's notorious for causing bugs like this.

[Eagle of Fire]

I am running XP SP1 and I have a screensaver running after 5 minutes of innactivity. I'd have noticed something strange if it was getting into conflict with DF.

Thing is, the screensaver is supposed to enter in effect only if the imput devices (keyboard and mouse) are innactive for the amount of time you specified. If I'm playing DF, my screensaver will never take effect 'cause I'm hitting keys all the time.

Next time it happen to you, try F11. That will bring you to window mode, which should also cancel the screensaver at the same time.

[AW]

quote:Originally posted by Toady One:
<STRONG>Entry mode?  I'm on XP, but I don't have a screen saver.  Is that something odd?  But yeah, I'm assuming DF doesn't handle them very well.  Looking at it, DF is supposed to prevent screensavers, I think, but I guess that doesn't work.</STRONG>

I suppose my term 'Entry Mode' is equivalent to a Unix login (or something XDM): it displays a little icon for each user on the machine and when you click it it brings up your session.  I'm kind of lazy with the Windows GUI terminology because I don't really develop anything in it.

I didn't have any trouble before this, and I have to admit it hasn't happened since.  Another poster had a good point about Logitech.  I have a fairly old logitech wireless desktop (circa 2001) and it may indeed have some kind of keymapping in the hardware (although I recently rebuilt the system when I upgraded the CPU and didn't add any special drivers for the keyboard.)

So, I just downloaded the new 33a this morning (I think that is 176 vice 169?) and I haven't seen the behavior.

[minor digression follows, just to pad out this text...]

One funny behavior that I didn't document that seems to be continuing is that occasionally the select a unit on the unit list with 'u'=>'c' brings up the wrong creature, that might be some kind symbol lookup type problem.  

I'll see if I can find another reference in a thread and post there.

Thanks!