Does not saving memory

[jaykodeveloper]

Hi Aleju,

Question again here. I ran collect_experience_supervised.py and waited until it fully starts. Then I back the game and press CTRL. But it does not seem like it is saving memory to replay_memory_reinforced.sqlite. It is not growing nor does not say it is saving memory. Is it a bug?

Thanks

[aleju]

Hm, it's been quite a long time since I implemented that script, so that is hard to debug from a distance. Does the console say anything? It could be that the script does not see/recognize the Route Advisor at the bottom right of the screen and if that is not the case it will not do anything. It can easily happen if the route advisor is hidden, is a little bit moved or looks a tiny bit different compared to what was expected. Though it should then print errors on the console saying that it doesn't see it. It could also be that reading out the pressed keys does not work for some reason. I guess OS and library version differences could easily cause this.

The crude method for debugging would be to add in collect_experiences_supervised.py before Line 54 a print("Keys:", keys_modifiers, keys). If no "Keys: (...)" ever comes up, it means that the loop is never executed and hence it will neither check if any key was pressed nor react to that.

[jaykodeveloper]

The route advisor is displayed but console still says, it is not visible. It may be looks a tiny bit different compared to what was expected. I tried to print(“Keys:”, keys_modifiers, keys), sometimes it hits this line, sometimes no. But it recognizes ctrl key pressed. How can I fix it recognize route advisor? I guess the updated game also cause this one as well.

[aleju]

If it is sometimes recognized, it could easily be a very minor difference in appearance. You can set in lib/ets2window.py Line 49 (is_route_advisor_visible()) the threshold argument a bit higher and see if it works then. You can also reactive line 57 (print("ra_rows", ra_rows)). Whatever that line prints (column-wise average pixel intensity of route advisor area) should be similar to the values in expected and it shouldn't change very much over time. If it is different from expected you can replace the values in expected with the ones that you get.

Downside is, that some other stuff might also look different for you, causing more issues. E.g. the speed-o-meter reading could become an issue. The estimation of the current steering wheel angle too.