|
Post by Sikat on Oct 1, 2016 6:33:04 GMT
Oh that, yes it's swiping then. I think the problems people are experiencing is due to lag OR non rooted device perhaps.
I just encountered problems with it on my Galaxy S4, it doesn't seem to recognize that it's in a battle, and does not find Rain's position probably due to him being obstructed by the trees in phantom forest.
I moved the button and it's working as intended. Will post more if there are troubles.
|
|
|
Post by Sikat on Oct 1, 2016 7:14:29 GMT
 Stuck there for the battle loop. Ok have been trying everything and the one that seems to work is with ALWAYS single step. Others don't work. What value do you suggest for the lag with always single step mode?
|
|
|
Post by tinotk on Oct 1, 2016 17:10:55 GMT
With that option I suggest you go with 0.8, you can also keep decreasing it until you find a better one. Can you record the screen running the script so I can see when it went wrong. Swiping works well for me on my phone at 1.0 lagx until the final boss battle though. In theory, if Always single step is working for you, then swiping should work (with a good lagx).
By the way while testing this path, I just found out a syntax error in phantom forest path after the final boss, will upload a fix soon.
|
|
|
Post by Sikat on Oct 1, 2016 18:49:32 GMT
So will you make a version for dpad navigation? It seems to be more reliable
|
|
|
Post by poweredbypho on Oct 1, 2016 19:58:48 GMT
Thanks for reporting, it will help others who getting same problem as you. Anyone using this script, please help me complete the poll on the first post. If your answer is Yes, please tell me which device you are using. Thank you!Swipe mode 1 is working for me! NOX emulator on 480x800 phone resolution. Not sure why, but I left the Dungeon Finder on ELT on overnight and I woke up to full NRG on both emulators - based on the EXP bar progress it looks like it stopped looping after running out of NRG last night. Ankulua button was still showing "stop" so I'm not sure if it's an issue Ankulua or the script. Anyone else have this issue?
|
|
|
Post by tangod on Oct 1, 2016 22:35:12 GMT
Xperia z3 compact, 1.5x lag seems to be ideal for me over night although 1 seems to work fine, just like to be safe.
I use swipe mode 2, single step only.
|
|
|
Post by Sikat on Oct 2, 2016 2:49:21 GMT
With that option I suggest you go with 0.8, you can also keep decreasing it until you find a better one. Can you record the screen running the script so I can see when it went wrong. Swiping works well for me on my phone at 1.0 lagx until the final boss battle though. In theory, if Always single step is working for you, then swiping should work (with a good lagx). By the way while testing this path, I just found out a syntax error in phantom forest path after the final boss, will upload a fix soon. Tell me how to. I tested on Earth Shrine Exploration which works well in Nox with Swipe 1 and Single Step Only, the only thing that works with my device is Always Single Step. Also, dungeon_finder seems slow or sometimes fail to click the AUTO button.
|
|
|
Post by tinotk on Oct 2, 2016 6:25:25 GMT
With that option I suggest you go with 0.8, you can also keep decreasing it until you find a better one. Can you record the screen running the script so I can see when it went wrong. Swiping works well for me on my phone at 1.0 lagx until the final boss battle though. In theory, if Always single step is working for you, then swiping should work (with a good lagx). By the way while testing this path, I just found out a syntax error in phantom forest path after the final boss, will upload a fix soon. Tell me how to. I tested on Earth Shrine Exploration which works well in Nox with Swipe 1 and Single Step Only, the only thing that works with my device is Always Single Step. I used AZ Screen Recorder, there are many on Google Play store, you can search for "screen recorder". But before doing that, can you try the latest v0.3 first, I made some changes to handling battles in explorations. I think your problem might come from the script exiting battle state too soon, thus leading to missteps but it can be other unknown reason too
|
|
|
Post by Sikat on Oct 2, 2016 6:40:39 GMT
What about the AUTO battle problem in regular dungeon_finder? Sometimes it works flawlessly for hours, sometimes it just stuck in the battle screen doing nothing.
|
|
|
Post by Sikat on Oct 2, 2016 6:41:28 GMT
Tell me how to. I tested on Earth Shrine Exploration which works well in Nox with Swipe 1 and Single Step Only, the only thing that works with my device is Always Single Step. I used AZ Screen Recorder, there are many on Google Play store, you can search for "screen recorder". But before doing that, can you try the latest v0.3 first, I made some changes to handling battles in explorations. I think your problem might come from the script exiting battle state too soon, thus leading to missteps but it can be other unknown reason too Might be the case as I saw something like Going up 10000ms while still in battle. Also noticed a new bug introduced in this version : It won't click Depart but considers it already inside the exploration zone sometimes.
|
|
|
Post by Sikat on Oct 2, 2016 8:56:47 GMT
|
|
|
Post by tinotk on Oct 2, 2016 18:29:46 GMT
Remember to always disable notifications for Ankulua in SuperSU. You can see that the msgbox "Ankulua has been granted..." covered the depart button. The script only check the button once, if the notification was covering the button it couldn't detect and click it. In fact this will also apply to all situations, where notifications (including Ankulua's play/stop button) popup and cover the image, Ankulua will fail to detect it. P/S: I made some improvements to the script handling boss battle based on what I saw in your second clip. Looked like Rain was still in battle state after done with the boss so it took a while for him to finish the exploration.
|
|
|
Post by Sikat on Oct 2, 2016 23:46:23 GMT
Ok, this morning I wake up to one Game Over screen and two fail to connect screen. When internet is restored it resumes from Battle screen and the script stops. Can you handle the Game Over screen too?
It might be better for your script to check Depart and other things over so there isn't any possibility of human error.
|
|
|
Post by darbelimatkaptr on Oct 3, 2016 12:34:48 GMT
You mean this? Let me know how else I can be of help. screenshot ![]() Well, you set the lagx too low. Consider change it to 0.6 or higher, take a look at jonny's ankulua.boards.net/post/1811 here, it seems that 0.6 has been working for him. You might want to read this post too: ankulua.boards.net/post/1807. I have explained detail how the script deal with Always step mode in the post. So back to your case, the problem came from 0.5 lagx. Rain was supposed to go left for 3500 ms, then take 3 steps right before going up. With 0.5 lagx & Always selected, Rain will only go left for 17 steps, so 3 steps to the right will leave him at the column. 0.55 might work for you because this will make Rain go left 19 steps. Let me know the result. I can confirm limit is between 0.5-0.6 lag. I use 0.6.
|
|
|
Post by Sikat on Oct 3, 2016 12:52:54 GMT
RIP Nox. Use Memu instead.
Oh and I noticed the first time I fire up a dungeon it has a chance to not click on Auto. If I manually click Auto it will work fine.
|
|