-
-
Notifications
You must be signed in to change notification settings - Fork 394
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
Controlled ViZDoom instance exited unexpectedly #430
Comments
This error can stem from any number of causes, as it just generally means the vizdoom binary died all the sudden. Here are some suggestions that could work:
|
Unfortunately not using anaconda is not an option for me. I ended up moving |
I have the same problem with python3.7.7 and vizdoom1.1.7, any update? |
I have the same problem with python3.8.8 and vizdoom1.1.9, any update? |
@Waterkin Can you share more details?
|
@Miffyli I tried to import vizdoom in Pycharm on Mac, but the error indicated that I didn't download the .wad file. |
Ah gotcha! Sadly I am not a mac person so can not comment on the bugs too much (sounds like you found something that needs to be better documented, so a PR to adjust for that would be very welcome!) The pre-compilation thing is a known-ish issue: the pre-built binaries only work on a very specific version of Python. On Mac and Linux I highly recommend building the packages yourself: https://github.com/mwydmuch/ViZDoom/blob/master/doc/Building.md#macos_build . Make sure the interpreter used by pycharm is the same you installed vizdoom on. |
Ok thanks a lot. I am still learning to use Github. Happy to PR for that. |
Hi @Waterkin, could you tell me how have you installed ViZDoom? From source? Using |
Full error:
Running:
I found this older issue #34 mentioning the same error, the solution, however, never got published by the user.
The text was updated successfully, but these errors were encountered: