Thank you for the update.
In the screenshots you added I see there is a mining hold visible in the display.
That bot tries to parse the mining hold from memory contents of the game client process. It looks like in your case the shape of memory contents is different from the examples we collected so far. That is why the bot does not recognize it.
When you send me the export of your play-session-2023-11-28T21-27-11 I can use that to adapt the bot to your game client.
If you don’t want to post a link, you can send it to support@botlab.org
Thank you, that helped. Now I see the problem is with the capacity gauge specifically.
The problem (difference from earlier training data) is even visible in the screenshot you posted from space where your ship is undocked. I highlighted the part where the gauge should appear in this image:
As you can see in your screenshot from in station, there sometimes is a text in there.
How does this part of the UI look when you have an item in the mining hold?
How would you decide that your mining hold is full enough to go for unloading the ore?
In the new picture I see that while there is still no text when in space, at least the progress bar seems to work. So it looks like we can at least derive the relative filling of the mining hold in this case.
Bots can do this by using image-processing, measuring the lengths of the blue part and dark part of that area.
Bot db8ff73090 does not use image processing for this part, since the earlier game clients all showed the textual representation of the fill level that your game client only shows when docked in station.
Thank you for the exploration!
I wonder if the display of text in the capacity gauge depends on the way to open the menu.
I remember there are at least three different ways in space:
Button in the Ship UI, to the side of the capacitor/hitpoints indications.
Context menu entry on the current ship, similar to ‘open cargo’
Some entry in the Neocom menu.
Which way do you use for the inventory seen in space?
