tobiaspfaff / grim_mouse

ResidualVM main repository
http://residualvm.org
GNU General Public License v2.0
56 stars 8 forks source link

Fire beaver damn freeze #30

Closed headsupduse closed 10 years ago

headsupduse commented 10 years ago

This is my 1st time playing the game. When I went through the door in the forest that leads to the fire beaver damn, after the CG cutscene, the beaver runs away from Manny, all the way to the opposite side of the damn from where Manny was, and then stops, locked in a running animation. The cursor was in the X shape, and I couldn't move Manny around or do anything. From what I understand, the beaver is supposed to run towards Manny and chase him out. This is halting my progress. Thanks for all of your work!

frankiesimon commented 10 years ago

I got to the same point exactly in the game.

Thank you for all the amazing work up to this point!

frankiesimon commented 10 years ago

Update: I didn't get a freeze when I picked up the key before going through the door. I did get some freezes after the second or third time the beavers chased me out - but anyway, I got through the first freeze by picking up the key first.

ZydrateJunkie commented 10 years ago

Exacty the same issue. Cannot resolve it and resume the game from where I left off, :(.

absolutltegend commented 10 years ago

This is happening to me as well.

Its like the cursor is waiting for the scene to load (it displays the 'X' symbol). The other keys are useless at this time, and you cannot access the developer console either.

Tobias great work with what you have accomplished with this interface. It is seamless and despite the minimal bugs I think it is fantastic!

Pg32312 commented 10 years ago

I am also experiencing this bug. No matter how many times i try and load into that zone, or have gotten the key first before going in there - the cursor freezes on an 'X' and will not allow any action once the beaver cut-scene ends.

tobiaspfaff commented 10 years ago

fixed in git

tobiaspfaff commented 10 years ago

in v0.5

tahuomo commented 10 years ago

The bug still occurs in v0.5_git if you have not completed the bone wagon upgrade.