|
|
Post by Cory Trese on Jun 5, 2015 22:48:27 GMT -5
Do you like it?
|
|
|
|
Post by johndramey on Jun 6, 2015 1:37:54 GMT -5
Do you mean a system for the LoS? Or has there been some kind of cosmetic change I've not noticed?
If you are talking about the LoS uncovering system, it is working amazingly smoothly. Whatever you guys did to fix it, it's working amazingly well!
|
|
|
|
Post by contributor on Jun 6, 2015 2:05:40 GMT -5
I'm still getting issues with it not uncovering things even one square away. I ran my captain right up to a hunter without knowing it until a scout caught up with him. Is there anything I can do to help diagnose the problem?
|
|
|
|
Post by fallen on Jun 6, 2015 7:43:38 GMT -5
contributor - the entire LoS system has been rewritten and we've been unable to reproduce any of the bugs from P1 that were reported. So, if you are finding fog issues, please provide screenshots, app version, device, OS version.
|
|
|
|
Post by contributor on Jun 6, 2015 15:22:16 GMT -5
Here's one on 0.0.8. Level is the Artifact Chamber (or something like that). Device is Samsung Galaxy Tab 2 7.0 running a custom ROM of Android 4.4.4. .png) |
|
|
|
Post by fallen on Jun 6, 2015 15:27:11 GMT -5
contributor - how did you get that Templar there? Are you returning from the menu? Or is this during play and you walked up? Any other info you can provide about your tap-style? Are you jamming taps when this kind of thing happens? Hoping we can get enough info to reproduce.
|
|
|
|
Post by contributor on Jun 6, 2015 15:32:33 GMT -5
I don't even know what jamming taps means, but I don't think I do it. I just tap >*< like that. The only other info I can add was that this was the first turn. I moved him up there to try and peak him around the corner and the fog didn't retreat. I then moved him one square further to the east than I intended just to see if the fog would push back and it didn't. That's when I snapped the pic. So the fog was like that when he was one square to the west (or possibly SW I can't remember for certain) and didn't change as I moved one square closer. You're lucky there were not big uglies hiding in that fog, as I sent him in just to test for you.
|
|
|
|
Post by fallen on Jun 6, 2015 15:39:42 GMT -5
contributor - "jamming taps" would refer to tapping a lot really fast or something. How you might "jam" the Blockade button in ST RPG. First turn is a good clue, thx.
|
|
|
|
Post by Cory Trese on Jun 6, 2015 18:37:52 GMT -5
Very sad to see this thread. Good thing is that the new implementation appears to be bug free, aside from this one screenshot. There must be a very specific set of moves that trigger it -- or it is an issue isolated to a particular type of CPU or GPU.
Sadly, I haven't seen it have any issues on any device yet -- right now I am thinking this version of code is definitely good enough to go with for the production release.
Really hope we can figure out this case in the screenshot -- you don't have a way to show the exact move path you took? A series of screenshots or a video?
|
|
|
|
Post by contributor on Jun 7, 2015 10:35:00 GMT -5
You guys are gonna hate me. I'm seeing this quite regularly. I'm on a different device too this time. The only other clue I have is that it seems to only affect one templar in each level. Here are a few more screen shots. Device is Samsung Galaxy S Duos II (GT-S7582) running Android 4.2.2   |
|
|
|
Post by ntsheep on Jun 7, 2015 10:42:50 GMT -5
I've been having this also but for the life of me it seems completely random and I can't notice a pattern that would be worth reporting. I've noticed there is a TP upgrade that is supposed to increase the sensor range of all the Knights on the map. Could this somehow be related to that? Perhaps the game code is checking for it, not seeing it, and not allowing the fog to be lifted.
|
|
|
|
Post by Cory Trese on Jun 7, 2015 11:00:08 GMT -5
Definitely not going to hate anyone for reporting bugs.
I hope we can get it fixed. It's definitely caused by the player doing something -- if we can figure out what you're doing -- specifically how you are moving and who -- then I'm sure I can fix it.
Thankfully we've reduced the issue 99% for the average user -- I am guessing there is a very rare side case you're triggering that I'm not testing for.
|
|
|
|
Post by slayernz on Jun 8, 2015 5:15:03 GMT -5
Got it too S4 Droid 4.4.2 Ver 0.0.9 On Tutorial level 1   Both done moving 1 square at a time to avoid it occurring because of spamming the movement. Obviously FOW cleared when the turn finished/new turn started. |
|
|
|
Post by Cory Trese on Jun 8, 2015 7:38:07 GMT -5
Unfortunately even moving 1 square at a time our references devices don't show a bug -- none of them do  I did try, for about two hours, to get it to bug out. I was even trying with two devices at once to save time. Nothing! |
|
|
|
Post by jknut on Jun 8, 2015 8:50:45 GMT -5
Fog not clearing (Windows 0.0.9):  |
|
