|
Post by anelephant on Dec 1, 2020 20:42:50 GMT
I'm sure this is the correct position... i.imgur.com/x0CZEPj.pngAlso after further testing, this only happens with the Venture III. It also has nothing to do with mining in low/high sec, I cannot mine properly in any area with the V3. I can use the exact same settings with the Venture II for example and it will work. can you try switching android emulator? from nox to ldplayer or vice versa. I guess I have to apply the same fix to enable alternate check on active miners even for ventures. I was using LDPlayer with the recommended settings. To test I installed it on Nox using the recommended settings and it seems to be working fine. What is the reason for that, out of curiosity?
|
|
|
Post by newbiex on Dec 1, 2020 21:23:48 GMT
can you try switching android emulator? from nox to ldplayer or vice versa. I guess I have to apply the same fix to enable alternate check on active miners even for ventures. I was using LDPlayer with the recommended settings. To test I installed it on Nox using the recommended settings and it seems to be working fine. What is the reason for that, out of curiosity? It must be some settings in the android emulators. There are some users that uses Nox and getting similar issue but switching to LDplayer seems to work for them.
|
|
|
Post by semuth on Dec 2, 2020 15:14:25 GMT
hello newbiex, 1. can you make option to unload cargo @ 50-60%? 2. i suggest to use "set as destination" button as panic button to warp to station when pirate came, you can use search history to find the station
thank you
|
|
|
Post by tototara on Dec 2, 2020 20:37:40 GMT
Hey newbiex, tl;dr: Active miners detection fails with a Venture III with 3 lasers (and circulation rigs, if it matters), but works perfectly fine with a Venture II. I don't see why it could do that, but I tried it and the difference is obvious. One works, the other fails. So there is a problem with active miners detection. Also, with the Venture II, if everything works, there is one thing that doesn't work : docking to station. It opens the station list, but does not warp/dock to it.I just tried the script today. One hour ago it worked fine on a Venture II with 2 mining lasers. Then I switch to a Venture III, and now it invariably fails to recognize that miners are active. I didn't change any single setting in LDPlayer in the meantime. I literally just switched ships. I tried the alternative active miners check : the problem is the same, it always says 0 active miners, and because of this it goes through the list of ores again, and unlock the ore instead of locking it, then is stuck in a state where it has no idea of what is going on (before locking a new asteroid, you should check if one is already locked... because it seems like the bot thinks it is locking an asteroid, while in fact it's already locked so it effectively clicks on "unlock" then it's completely stuck - it should be an easy fix to implement. Before you try to lock, check that the first entry in the contextual menu says "lock" and not "unlock")
EDIT: I tried again with Venture II, works perfectly. Went back to Venture III, and this time it even had a problem. When the distance reached the limit to mine, it was going through overview for some reason. So later, when it saw it was only at 13km... it failed to stop the engine and start the mining lasers. So the ship was still approaching, but not mining. So then it goes into overview, but it locked something else than the pyroxeres (the one that it usually unlocks instead of locking) because since the ship was moving, overview got reorganized just before it clicked). But, even without this last bug, the problem was here. It was stuck trying to lock an ore, while one was already locked (you should check the list of locked object on the top, also maybe, before trying to lock again).
|
|
|
Post by anelephant on Dec 2, 2020 22:00:20 GMT
Hey newbiex, tl;dr: Active miners detection fails with a Venture III with 3 lasers (and circulation rigs, if it matters), but works perfectly fine with a Venture II. I don't see why it could do that, but I tried it and the difference is obvious. One works, the other fails. So there is a problem with active miners detection. Also, with the Venture II, if everything works, there is one thing that doesn't work : docking to station. It opens the station list, but does not warp/dock to it.I just tried the script today. One hour ago it worked fine on a Venture II with 2 mining lasers. Then I switch to a Venture III, and now it invariably fails to recognize that miners are active. I didn't change any single setting in LDPlayer in the meantime. I literally just switched ships. I tried the alternative active miners check : the problem is the same, it always says 0 active miners, and because of this it goes through the list of ores again, and unlock the ore instead of locking it, then is stuck in a state where it has no idea of what is going on (before locking a new asteroid, you should check if one is already locked... because it seems like the bot thinks it is locking an asteroid, while in fact it's already locked so it effectively clicks on "unlock" then it's completely stuck - it should be an easy fix to implement. Before you try to lock, check that the first entry in the contextual menu says "lock" and not "unlock")
EDIT: I tried again with Venture II, works perfectly. Went back to Venture III, and this time it even had a problem. When the distance reached the limit to mine, it was going through overview for some reason. So later, when it saw it was only at 13km... it failed to stop the engine and start the mining lasers. So the ship was still approaching, but not mining. So then it goes into overview, but it locked something else than the pyroxeres (the one that it usually unlocks instead of locking) because since the ship was moving, overview got reorganized just before it clicked). But, even without this last bug, the problem was here. It was stuck trying to lock an ore, while one was already locked (you should check the list of locked object on the top, also maybe, before trying to lock again).
I literally just stated this problem here and got a solution. Go back a page and read the thread
|
|
|
Post by tototara on Dec 2, 2020 22:21:53 GMT
I literally just stated this problem here and got a solution. Go back a page and read the thread The solution you got was not a solution. It was a "try this... oh it works with Nox but not LDPlayer. No idea why, but it's cool". While the dev has stated some people had problems with Nox instead. That's not a solution, that's luck. Other people will have the same problem, with LDPlayer and/or Nox. If you go back through the thread, you'll find that's one of the most common problem people encounter. Also, I stated another problem related to docking in station, that seems to be unrelated. We have no idea if using Nox would fix that also. This needs to be fixed by finding a reliable way to detect the illuminated circle going around the mining laser icon - shouldn't be too hard (I'm a dev myself, I have some experience, even with OCR or UI automation). .
Also, the "momentary lucky fix" that you used, consists in using Nox instead of LDPlayer, despite LDPlayer listed as working better. In order to do that, I'd have to re-download EVE Echoes. That's 2GB and I'm currently on a mobile DATA connection for lack of a landline connection where I am currently situated. So this is not an option for me.
|
|
|
Post by zgholdingsllc on Dec 3, 2020 1:05:17 GMT
I literally just stated this problem here and got a solution. Go back a page and read the thread The solution you got was not a solution. It was a "try this... oh it works with Nox but not LDPlayer. No idea why, but it's cool". While the dev has stated some people had problems with Nox instead. That's not a solution, that's luck. Other people will have the same problem, with LDPlayer and/or Nox. If you go back through the thread, you'll find that's one of the most common problem people encounter. Also, I stated another problem related to docking in station, that seems to be unrelated. We have no idea if using Nox would fix that also. This needs to be fixed by finding a reliable way to detect the illuminated circle going around the mining laser icon - shouldn't be too hard (I'm a dev myself, I have some experience, even with OCR or UI automation). .
Also, the "momentary lucky fix" that you used, consists in using Nox instead of LDPlayer, despite LDPlayer listed as working better. In order to do that, I'd have to re-download EVE Echoes. That's 2GB and I'm currently on a mobile DATA connection for lack of a landline connection where I am currently situated. So this is not an option for me. If you are a dev yourself and it's easy, why not create your own and stop whining on something that you think is easy to do. We all pay for the bot but try to make your post easy read so that others may help you. Stop your sarcasm. Somebody might help instead of the dev. OR just quit EVE.. you don't deserve to play it.. NOOB!
|
|
|
Post by newbiex on Dec 3, 2020 3:17:51 GMT
hello newbiex, 1. can you make option to unload cargo @ 50-60%? 2. i suggest to use "set as destination" button as panic button to warp to station when pirate came, you can use search history to find the station thank you #1. sure. we will add that 50-60% but not sure why you need this? the 10-20% was added just for testing purposes. then 90-100% was added to actually improve mining. #2. will do. I think 2-3 people suggested this already.
|
|
|
Post by newbiex on Dec 3, 2020 3:30:59 GMT
Hey newbiex, tl;dr: Active miners detection fails with a Venture III with 3 lasers (and circulation rigs, if it matters), but works perfectly fine with a Venture II. I don't see why it could do that, but I tried it and the difference is obvious. One works, the other fails. So there is a problem with active miners detection. Also, with the Venture II, if everything works, there is one thing that doesn't work : docking to station. It opens the station list, but does not warp/dock to it.I just tried the script today. One hour ago it worked fine on a Venture II with 2 mining lasers. Then I switch to a Venture III, and now it invariably fails to recognize that miners are active. I didn't change any single setting in LDPlayer in the meantime. I literally just switched ships. I tried the alternative active miners check : the problem is the same, it always says 0 active miners, and because of this it goes through the list of ores again, and unlock the ore instead of locking it, then is stuck in a state where it has no idea of what is going on (before locking a new asteroid, you should check if one is already locked... because it seems like the bot thinks it is locking an asteroid, while in fact it's already locked so it effectively clicks on "unlock" then it's completely stuck - it should be an easy fix to implement. Before you try to lock, check that the first entry in the contextual menu says "lock" and not "unlock")
EDIT: I tried again with Venture II, works perfectly. Went back to Venture III, and this time it even had a problem. When the distance reached the limit to mine, it was going through overview for some reason. So later, when it saw it was only at 13km... it failed to stop the engine and start the mining lasers. So the ship was still approaching, but not mining. So then it goes into overview, but it locked something else than the pyroxeres (the one that it usually unlocks instead of locking) because since the ship was moving, overview got reorganized just before it clicked). But, even without this last bug, the problem was here. It was stuck trying to lock an ore, while one was already locked (you should check the list of locked object on the top, also maybe, before trying to lock again).
#1. The alternate miners check option was for running retriever. This will be changed in the next release to apply for venture too. if your miners count is working then 90% of the time you shouldn't be getting those multiple locked ore and even if the bot did it will work it out. Your issue is the miners count is not working at all so the bot does all those silly thing. Yes, that can be done to re-check if an ore is locked already before locking new one. #2. Overview is moving and it can happen that the lock ore is different than what it should locked. This can happen. #3. If you are over the 1 day free trial then don't expect bot will work as expected. Are you still on a trial mode and have not consumed the free 1 day?
|
|
|
Post by newbiex on Dec 3, 2020 3:41:19 GMT
I literally just stated this problem here and got a solution. Go back a page and read the thread The solution you got was not a solution. It was a "try this... oh it works with Nox but not LDPlayer. No idea why, but it's cool". While the dev has stated some people had problems with Nox instead. That's not a solution, that's luck. Other people will have the same problem, with LDPlayer and/or Nox. If you go back through the thread, you'll find that's one of the most common problem people encounter. Also, I stated another problem related to docking in station, that seems to be unrelated. We have no idea if using Nox would fix that also. This needs to be fixed by finding a reliable way to detect the illuminated circle going around the mining laser icon - shouldn't be too hard (I'm a dev myself, I have some experience, even with OCR or UI automation). .
Also, the "momentary lucky fix" that you used, consists in using Nox instead of LDPlayer, despite LDPlayer listed as working better. In order to do that, I'd have to re-download EVE Echoes. That's 2GB and I'm currently on a mobile DATA connection for lack of a landline connection where I am currently situated. So this is not an option for me. I'm aware of the 'active miners check" issue that is why the alternate miners check was provided temporarily for retriever only. If you go back some pages it was explained that this option will be rolled to venture as well. Yes. it shouldn't be hard to detect that illuminated thing but try using Ankulua script and you will see why it was not that easy. Actually, till now that check will not work 100% even with alternate miners check - there are instances that it will not work.
|
|
|
Post by semuth on Dec 3, 2020 4:58:35 GMT
hello newbiex, 1. can you make option to unload cargo @ 50-60%? 2. i suggest to use "set as destination" button as panic button to warp to station when pirate came, you can use search history to find the station thank you #1. sure. we will add that 50-60% but not sure why you need this? the 10-20% was added just for testing purposes. then 90-100% was added to actually improve mining. #2. will do. I think 2-3 people suggested this already. #1. less time at mining belt = more safety. ofc less ore mined, but you can avoid to meet pirate by spending less time at belt and more ore stored at station. #2. i will be gratefull if its implemented. thank you #3. more suggest..we can mix cloacking module with local list check. so when red or grey come to system, bot will automaticaly click cloacking module until red/grey leave the system. #4. there is issue with venture III mining with ion miner, it seems active miner detection is failed. i change it to single diode miner and the issue is gone. btw, thank you for lowering your script price
|
|
|
Post by tototara on Dec 3, 2020 12:55:44 GMT
If you are a dev yourself and it's easy, why not create your own and stop whining on something that you think is easy to do. We all pay for the bot but try to make your post easy read so that others may help you. Stop your sarcasm. Somebody might help instead of the dev. OR just quit EVE.. you don't deserve to play it.. NOOB! Can we be constructive here, and not start fighting like kids ? Newbiex is making a bot. Okay. I report feedback about bugs. Most devs would be happy. And I guess the smart move for him if he wants to continue selling it and have it even more succesful, is to fix bugs. Why are you guys talking in his place, coming up with retard arguments like "why don't you make it yourself"? Well, the answer is simple : if it's been made somewhere, why reinvent the wheel ? At best, what I could do, is partner with someone who already made one, to make it even better. You know, like... contribute, and not reinvent 3 times the same thing and have 3 poorly working bots, when you could have one that is great. I have made very simple bots for other things (even one for mining that just detects ennemy ships and warp away - weirdly, it was working much better and faster than any other bot I've tried, including this one with which I've been ganked after 2hrs of use by a simple frigate...). But making a full mining bot would take hours and hours, probably days of tinkering, fixing bugs and cases you didn't think about in the beginning, etc. It would be worth it if I intended to sell it for money, otherwise, the minimal isk gain is clearly not worth the dozens of hours you'd have to spend to make the bot. So, here you have your answer to "why not create my own and stop whining on something you think is easy to do". It takes a lot of time and is not worth for personal use. Now, let me ask you a question in return : Why are people with no experience in programming getting angry at devs talking to each other ? It makes no sense. For god's sake, stop trying to create conflict where there is just feedback and discussion. Everybody will be in a better mood, and we'll come to solutions faster, without this polluting "play yourself / make it yourself / noob you don't deserve this or that".... I haven't whined. I have sarcastically answered to a user who answered my feedback and my question aimed at the dev... Anyway, Newbiex, I hope you see my first comment and can find the useful info in this ocean of attempts at comparing penises and creating conflict. I gave you a few points that seem to be limiting factors for having a really reliable bot - which in turns mean more paying customers. As of now, I personally wouldn't pay after the one day trial for example, since it didn't seem to do the job. But I'm pretty sure it can be great with a few tweaks
|
|
|
Post by tototara on Dec 3, 2020 12:57:54 GMT
#3. If you are over the 1 day free trial then don't expect bot will work as expected. Are you still on a trial mode and have not consumed the free 1 day? Yep I was on the 1-day trial. Does the bot work differently on it, than after paying ? And thanks for the reply on the other questions. Yep... the miners count was fine in every cases, but the "active miners" always stayed at zero on the Venture III (it was correct on the Venture II).
|
|
|
Post by tototara on Dec 3, 2020 13:01:51 GMT
Yes. it shouldn't be hard to detect that illuminated thing but try using Ankulua script and you will see why it was not that easy. Actually, till now that check will not work 100% even with alternate miners check - there are instances that it will not work. Yea I didn't know Ankulua before finding your bot. I was doing everything I did in python, so the emulator/game window had to be visible at all time (it basically captures the screen and do all the work on the capture image, X times per second or every X seconds). The idea of having the bot run on the Android system too is great. But yeah... I guess there are some limitations :/ I wonder if we could get other kind of languages working on Android, and have an option to capture the screen image. If yes, that would be great for more control over what it can do.
|
|
|
Post by newbiex on Dec 3, 2020 14:42:52 GMT
Yes. it shouldn't be hard to detect that illuminated thing but try using Ankulua script and you will see why it was not that easy. Actually, till now that check will not work 100% even with alternate miners check - there are instances that it will not work. Yea I didn't know Ankulua before finding your bot. I was doing everything I did in python, so the emulator/game window had to be visible at all time (it basically captures the screen and do all the work on the capture image, X times per second or every X seconds). The idea of having the bot run on the Android system too is great. But yeah... I guess there are some limitations :/ I wonder if we could get other kind of languages working on Android, and have an option to capture the screen image. If yes, that would be great for more control over what it can do. Yes. I was doing other bots too with some other android games without Ankulua - mostly for personal use. Running multiple sessions in one PC and at the same time using the same PC for some other work is a pain. You have to attached to the game process and do low level programming so that your game window can be minimize and run independently. Ankulua makes all those things easier but with some trade off.
|
|