Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time sync of radiant/dire teams upon reset not stable. #33

Open
TimZaman opened this issue Jan 6, 2019 · 10 comments
Open

Time sync of radiant/dire teams upon reset not stable. #33

TimZaman opened this issue Jan 6, 2019 · 10 comments

Comments

@TimZaman
Copy link
Owner

TimZaman commented Jan 6, 2019

Ex (0.3.2):

ValueError: dota_time discrepancy in depleting initial worldstate queue.
at reset (/root/dotaservice/dotaservice/dotaservice.py:439)
at request_handler (/root/.local/lib/python3.7/site-packages/grpclib/server.py:327)
@sijiaxu
Copy link

sijiaxu commented Jan 7, 2019

I also keep getting this error when launch the game.
but, when I disable this part of code and use the GUI host mode, I stuck at the map loading screen and can not enter the game.
Does this discrepancy in the two teams observation queue has any bad consequence, like this stuck problem?

@TimZaman
Copy link
Owner Author

TimZaman commented Jan 7, 2019

Yeah that's exactly the problem.

@TimZaman
Copy link
Owner Author

TimZaman commented Jan 7, 2019

Problem comes from what's explained in the last paragraph: https://github.com/TimZaman/dotaservice/blob/master/NOTES.md

@sijiaxu
Copy link

sijiaxu commented Jan 8, 2019

Thanks, but it seems cannot causing the stuck problem, I can not receive any normal observation(status='ok') in my client after launching the game.

@TimZaman
Copy link
Owner Author

TimZaman commented Jan 8, 2019 via email

@sijiaxu
Copy link

sijiaxu commented Jan 8, 2019

another question, you mention set the render to true in order to see the GUI, is that referring to use the HOST_MODE_GUI mode?

@TimZaman
Copy link
Owner Author

TimZaman commented Jan 9, 2019

I made the worldstate to be pushed threaded now, can you check if this solves the time discrepancy?

@sijiaxu
Copy link

sijiaxu commented Jan 9, 2019

yes, the time discrepancy error has gone, but I still stuck at the 'DOTA_GAMERULES_STATE_PRE_GAME' state, I cannot receive the world state message after that, detail log can be seen here #35

I go through the console log, there are some errors, the lack of libtensorflow.so and some .vhcg files, but it seems not the big problems after google.
so how can I debug my problems like debug option and tools? I doubt there are some problems in the dota's configure, causing game freeze and no world state sended out.

@TimZaman
Copy link
Owner Author

still an issue for me sporadically even with threaded.

@lenLRX
Copy link

lenLRX commented Jul 26, 2019

when i set ticks_per_observation to 1, i got ValueError: dota_time discrepancy in depleting initial worldstate queue.

when i set it to 2, i got assert queue.qsize() == 0 in observe()

It seems sync between two team caused a lot trouble.
But I wonder whether it is neccesery to keep sync. For me, i don't think so, i just want get the latest tick and it is ok to drop any data that i missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants