Open nexty5870 opened 3 years ago
Maybe the asteroids look slightly different in your game client. Such an issue is easily fixed by adding more training data. If you link the session recording archive of your session, I can take a look and adapt the bot to your game client. You can upload the file directly here in the GitHub issue. To get the archive for your session, see the guide at https://to.botlab.org/guide/how-to-report-an-issue-with-a-bot-or-request-a-new-feature#getting-the-session-recording-archive
Does a specific fitting is required maybe? Im having Miner I laser at the present
Let's have a look at the status text. Does it display the right number of mining lasers?
Thank you for getting back to me that quick!
attached one of the session log session-2020-12-28T00-47-29-4e91d7.zip
event 146 you can see the Asteorid available to mine there
Thank again!
In the archive session-2020-12-28T00-47-29-4e91d7.zip
, your game client's reading looks like the 'Name' column in the overview is not visible.
Does it work when you make this column visible in the overview?
that make the trick actually! thank a lot
have now order some credit as well - amazing dev, thank you!
I expanded the bot to avoid it skipping asteroid belts in this scenario: https://github.com/Viir/bots/commit/dea59f373d7be5f3908ec1e2ff24a5309fbb7617
For the scenario session-2020-12-28T00-47-29-4e91d7.zip
, this version shows a new message instead, for example, in event 110:
Session performance: times unloaded: 0, volume unloaded / m³: 0
---
Current reading: Ore hold filled 0%. Shield HP at 100%. Found 2 mining modules. I see the drones window: In bay: 2, in local space: 0.
+ I see ship UI and overview, undocking complete.
++ The 'Name' column in the overview window seems disabled.
+++ Please configure the overview to show objects names.
++++ I am stuck here and need help to continue.
+++++ Wait
In the archive
session-2020-12-28T00-47-29-4e91d7.zip
, your game client's reading looks like the 'Name' column in the overview is not visible.Does it work when you make this column visible in the overview?
I have the same issue and I have tried to apply this fix, and realised the “name” column is already in the overview.
if theres a way for me to send you the log (and how to) let me know! Would love for this to be fixed
if theres a way for me to send you the log (and how to) let me know! Would love for this to be fixed
The easiest way would be to add the log (session recording archive) to this issue thread. I can drag & drop a file into the text box here, and that gets uploaded then so other people can access it. I tested this using the Chrome browser on Windows 10.
Does this way to upload work for you?
if theres a way for me to send you the log (and how to) let me know! Would love for this to be fixed
The easiest way would be to add the log (session recording archive) to this issue thread. I can drag & drop a file into the text box here, and that gets uploaded then so other people can access it. I tested this using the Chrome browser on Windows 10.
Does this way to upload work for you?
session-2021-01-18T10-21-07-538048.zip let me know if i did the right steps ! thank you for your time
Yes, that worked. I am looking at event 66 in session-2021-01-18T10-21-07-538048. In this case, it seems like there was no asteroid remaining in the belt. In this case, it seems like there was no asteroid remaining in the belt. In the overview window, you can see only four entries. None of those seems to be an asteroid. The solution is to find a solar system with asteroids remaining in the belts (or another mining site you can bookmark). You need to start the bot in a solar system that has asteroids. If you saw asteroids outside the overview window, the solution would be to make them visible in the overview.
You can also look at status display for guidance. In the display text for event 66, you also see this:
++++ I see no asteroid in the overview. Warp to mining site.
Hi everyone,
have try the bot yesterday, it seems being looping in warping saying that he cannot find asteroid on the belt,
I have my overview set to Mining so asteroid belt are being display with the closest range as per the note
I have try to manually start the mining process in one of those belt, resume the bot and it was running properly (meaning the bot was able to detect the mining progress and drop off to station )
Does a specific fitting is required maybe? Im having Miner I laser at the present