|
Post by eldur on Nov 17, 2013 20:01:03 GMT -5
Everyone once in a while the party glom movement appears to hit a snag. This seems most common around bridges.
On level 3 of the mines, if you click a point beyond the first bridge while glommed, the party stops on the bridge before finishing the movement to the point selected for glom movement.
|
|
|
Post by fallen on Nov 17, 2013 20:05:41 GMT -5
eldur - you see the game first accept the movement (it centers on the spot you clicked) but then half way there the group stops? Have you possibly touched the screen again (cancel)? Or ... you are trying to get them to move over a long distance and when you tap, the game seems to ignore your tap?
|
|
|
Post by eldur on Nov 17, 2013 20:13:27 GMT -5
eldur - you see the game first accept the movement (it centers on the spot you clicked) but then half way there the group stops? Have you possibly touched the screen again (cancel)? Or ... you are trying to get them to move over a long distance and when you tap, the game seems to ignore your tap? The game accepts the movement but half way there stops. More specifically, it stops on the bridge. It is repeatable on my iPhone. It happens mostly on bridges. I know I am not touching the screen when it happens. I've also had it happen going around the corner to the second stairwell on level 3.
|
|
|
Post by fallen on Nov 17, 2013 21:29:27 GMT -5
eldur - wooden bridges, yes? Thanks for the extra details. Anyone else seeing this one?
|
|
|
Post by eldur on Nov 17, 2013 21:57:36 GMT -5
eldur - wooden bridges, yes? Thanks for the extra details. Anyone else seeing this one? Cellet Void as you come in from Mines 2. Glom click the party to a location under the bridge south of where you entered.
|
|
|
Post by beuns on Nov 17, 2013 23:12:04 GMT -5
I had this one earlier. I reported it on another thread but I can't remember where. To me it seems to happens around area where you get the "did you hear that ?"
Edit : I reported it on :"stop movement on ledges" and I think I gave greater details.
|
|
|
Post by absimiliard on Nov 18, 2013 8:49:35 GMT -5
I've seen this. It's definitely where you get ambushed in the void. The first point is on the first bridge. There's another line of "trigger" squares down near the stairs down. (the ones that go down to where the campsite is) Then it occurs again on the "island" just before you cross the bridge to the stairs down to the approach to the final fight.
It's pretty clear, given the repeatability, that the game engine stops movement when you step on a trigger square; a square that triggers one of the ambushes.
I haven't tested that it happens on other levels, but I'd be surprised if it didn't.
-abs
|
|
|
Post by beuns on Nov 18, 2013 9:07:13 GMT -5
I've seen this. It's definitely where you get ambushed in the void. The first point is on the first bridge. There's another line of "trigger" squares down near the stairs down. (the ones that go down to where the campsite is) Then it occurs again on the "island" just before you cross the bridge to the stairs down to the approach to the final fight. It's pretty clear, given the repeatability, that the game engine stops movement when you step on a trigger square; a square that triggers one of the ambushes. I haven't tested that it happens on other levels, but I'd be surprised if it didn't. -abs In my game it stopped exactly at the same points but it only happens in cellet void ledges. In all other levels it went perfectly.
|
|
|
Post by fallen on Nov 18, 2013 10:21:57 GMT -5
Does it stop there only the first time when the ambush is firing? Sorry -- haven't gone down there yet to test, trying to gather as much info as I can before I dive in to spend the hours.
|
|
|
Post by Cory Trese on Nov 18, 2013 10:27:29 GMT -5
This is mine, known issue.
You are stepping into a "trigger zone" that is firing an ambush that is already over.
I missed the fix for this -- thanks for the report.
|
|
|
Post by beuns on Nov 19, 2013 11:40:20 GMT -5
This is mine, known issue. You are stepping into a "trigger zone" that is firing an ambush that is already over. I missed the fix for this -- thanks for the report. No problem Cory.
|
|