search

elimelec / inethack

Automatically exported from code.google.com/p/inethack
GNU General Public License v2.0
0 stars 0 forks source link

Movement fails #56

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Sometimes for no obvious reason, movement will fail, usually several times in a 
row. 
Attempting to move in a different direction will fix this.

Original issue reported on code.google.com by lhann...@gmail.com on 15 Aug 2009 at 3:59

GoogleCodeExporter commented 8 years ago 
Sometimes I don't get the direction right, maybe that's the problem here? This 
could
be fixed with visual feedback.

If it's not the direction can you find out in which circumstances it happens?

Original comment by din...@gmail.com on 15 Aug 2009 at 5:02

GoogleCodeExporter commented 8 years ago 
I'm not sure of the exact circumstances, but it happens more often in hallways 
and when walking fast but 
not fast enough to start running

Original comment by lhann...@gmail.com on 15 Aug 2009 at 2:20

GoogleCodeExporter commented 8 years ago 
I was thinking, could it be a bug in the run code. Perhaps it is detecting side 
path whe. There isint one 
and stalling movement? Just a thought

Original comment by lhann...@gmail.com on 15 Aug 2009 at 3:07

GoogleCodeExporter commented 8 years ago 
Please clarify, it's hard for me to understand where the problem is because I'm
pretty intimate with the movement code and in many hours of play-testing the 
engine
has always behaved as intended. So I need the exact situation, what you did as 
input
and in what ways it doesn't behave as you expected.

Original comment by din...@gmail.com on 15 Aug 2009 at 5:51

GoogleCodeExporter commented 8 years ago 
Ok it looks like after a run for example, say I'm tapping left it will run for 
a bit then stop like at a door or a 
fork in the hallway. At that point it will stop responding to motion unless I 
give it a couple of seconds, or 
change directions. Perhaps it's intentional, but it feels ackward for me. May 
be related to the other issue I 
posted about the run sensitivity.

Original comment by lhann...@gmail.com on 15 Aug 2009 at 5:58

GoogleCodeExporter commented 8 years ago 
So double tap, you stop in front of a door, and tap in the same direction again?
That's very probable a problem with issue 55.

Original comment by din...@gmail.com on 15 Aug 2009 at 6:14

GoogleCodeExporter commented 8 years ago

Original comment by din...@gmail.com on 21 Aug 2009 at 11:03

GoogleCodeExporter commented 8 years ago 
Should be solved with r198 and issue 55.

Original comment by din...@gmail.com on 21 Aug 2009 at 12:53