I am planning to experiment with population-based training and self-play, similar to the recent DeepMind's Q3 CTF paper. The obvious requirement would be the ability to train the agents to play against other agent copies on the same map at the same time.

I could probably wrap a multiplayer session into a single multi-agent interface and use ASYNC_PLAYER mode, maybe with increased tickrate (https://github.com/mwydmuch/ViZDoom/issues/209) However the optimal way to implement this would be to render multiple observations for different agents within the same tick in the same process in synchronous mode, similar to how it's done in single-player.

Any thoughts on what is the right course of action here? Does multi-agent SYNC mode seem feasible or would it require changing half the codebase?

When I try to install the vizdoom using 'pip install',the error raised that : ERROR: Command errored out with exit status 1: command: /usr/bin/python3 /tmp/tmpoln7vkbf build_wheel /tmp/tmp6vsdacbc cwd: /tmp/pip-install-kby3x8wx/vizdoom Complete output (38 lines): running bdist_wheel running build Traceback (most recent call last): File "/tmp/tmpoln7vkbf", line 280, in main() File "/tmp/tmpoln7vkbf", line 263, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "/tmp/tmpoln7vkbf", line 204, in build_wheel return _build_backend().build_wheel(wheel_directory, config_settings, File "/tmp/pip-build-env-jljcnwxe/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 230, in build_wheel return self._build_with_temp_dir(['bdist_wheel'], '.whl', File "/tmp/pip-build-env-jljcnwxe/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 215, in _build_with_temp_dir self.run_setup() File "/tmp/pip-build-env-jljcnwxe/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 267, in run_setup super(_BuildMetaLegacyBackend, File "/tmp/pip-build-env-jljcnwxe/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 158, in run_setup exec(compile(code, file, 'exec'), locals()) File "setup.py", line 147, in setup( File "/tmp/pip-build-env-jljcnwxe/overlay/lib/python3.8/site-packages/setuptools/init.py", line 153, in setup return distutils.core.setup(**attrs) File "/usr/lib/python3.8/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command cmd_obj.run() File "/tmp/pip-build-env-jljcnwxe/overlay/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 299, in run self.run_command('build') File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command cmd_obj.run() File "setup.py", line 125, in run if os.path.exists(python_library): File "/usr/lib/python3.8/genericpath.py", line 19, in exists os.stat(path) TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType ERROR: Failed building wheel for vizdoom Failed to build vizdoom ERROR: Could not build wheels for vizdoom which use PEP 517 and cannot be installed directly And my OS info lies below:

Linux version 4.4.0-19041-Microsoft ([email protected]) (gcc version 5.4.0 (GCC) ) #1237-Microsoft Sat Sep 11 14:32:00 PST 2021

I've just updated my ViZDoom version and even though it used to compile and work just fine, fbda2ab19 seems to break the build for me . With this change it can no longer find boost-python. I installed the libraries using the following commands. I see that /usr/local/include/boost/python.hpp exists.

brew install boost
brew install boost-python --with-python3

Once I comment out this addtional set it compiles without any problems.

closes #225

This work adds sound into the state space of vizdoom, we can now pass audio buffers synchronously as a NumPy array to the state variable. To enable this set game.set_soft_sound_enabled(True). enabling this slows down sync frame rate by a bit, but this gives researchers the option to tap into a lesser-seen state space.

I'm getting a link error at build on Ubuntu 16.04 LTS. Any ideas?

[ 99%] Building CXX object src/vizdoom/src/CMakeFiles/vizdoom.dir/vizdoom_game.cpp.o
[ 99%] Building CXX object src/vizdoom/src/CMakeFiles/vizdoom.dir/vizdoom_screen.cpp.o
[ 99%] Building CXX object src/vizdoom/src/CMakeFiles/vizdoom.dir/vizdoom_shared_memory.cpp.o
[100%] Building CXX object src/vizdoom/src/CMakeFiles/vizdoom.dir/vizdoom_message_queue.cpp.o
[100%] Building CXX object src/vizdoom/src/CMakeFiles/vizdoom.dir/vizdoom_main.cpp.o
[100%] Building CXX object src/vizdoom/src/CMakeFiles/vizdoom.dir/vizdoom_depth.cpp.o
[100%] Linking CXX executable ../../../bin/vizdoom
CMakeFiles/vizdoom.dir/tempfiles.cpp.o: In function `FTempFileName::FTempFileName(char const*)':
tempfiles.cpp:(.text+0x7): warning: the use of `tempnam' is dangerous, better use `mkstemp'
//lib/x86_64-linux-gnu/libsystemd.so.0: undefined reference to `lzma_stream_decoder@XZ_5.0'
//lib/x86_64-linux-gnu/libsystemd.so.0: undefined reference to `lzma_end@XZ_5.0'
//lib/x86_64-linux-gnu/libsystemd.so.0: undefined reference to `lzma_code@XZ_5.0'
collect2: error: ld returned 1 exit status
src/vizdoom/src/CMakeFiles/vizdoom.dir/build.make:8868: recipe for target 'bin/vizdoom' failed
make[2]: *** [bin/vizdoom] Error 1
CMakeFiles/Makefile2:897: recipe for target 'src/vizdoom/src/CMakeFiles/vizdoom.dir/all' failed
make[1]: *** [src/vizdoom/src/CMakeFiles/vizdoom.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

I've noticed that the function 'random' in acs scripts works poorly, since the numbers obtained have kind of a scheme and generally one number repeats many times more than the others.

Do you guys know if there's a way to use a 'better' random number generator?

Coming from ZDOOM I don't see any hope. No C++ functions can be imported or so. I could imagine however, that somehow one can set a variable in the acs script, directly from vizdoom. Something like, game.set_game_variable(USER1). Would it be possible? Do you see any workaround?

Thanks in advance!

E.g. by commanding "enable_audio" before initing the game, and then receiving additional object in State object which holds audio samples played inside that time frame.

I know it is VizDoom but this could possibly allow bots to "home in" towards high-action areas and/or hear close-by enemies behind them.

Hello,

I can't find any documentation on the user variables like the one used in the example on your website:

"It is also possible to access user variables (USER1, USER2 ... USER32), which correspond to ACS scripts' global variables 1-32." Such as when used in game.get_game_variable(GameVariable.USER1)

I've tried looking at ACS documentation on ZDoom and Doom wikis, but I cannot find and reference to these global variables. Is there a list somewhere of these variables?

I am asking because I want to make the agent lose reward whenever it uses ammo so it learns to conserve it.

Hi, I'm using VizDoom to train my agent to learn to navigate. But there are several questions:

1. in my scenario, the maze is discrete, which means I regard the vizdoom as a 3D grid world. However, I don't know how to randomly initialize my agent in those grids.
2. By the way, I want the agent to move in three ways: move forward for 1 grid (a specific length), turn left (90 degrees), and turn right (90 degrees as well). But I only find the button to move in a very small step or turn a small angle. Could you please provide me with some hints to do those things? Thanks a lot!

Adding Gym Wrapper for Vizdoom

1. Base env, env definitions, documentation borrowed from vizdoomgym with minor changes wrt recent gym API (0.22.0).
2. env.render is done using pygame after extracting it from vizdoom's screen buffer. Can maybe use Vizdoom API directly if gym rendering API is changed.
3. Added a test to check the env for different obs types for every configuration. (health, position, labels, depth = True / False). Another test to check obs at terminal state, since this is handled separately.
4. Unsure about the folder placement. I felt this was okay. Added commands to copy it to build destination.

hi im try to use vizdoom on my computer os:windows10 i've install vizdoom in D:\Users\user\Anaconda3\Lib\site-packages\vizdoom and my basic.py is in D:\Users\user\Anaconda3\Lib\site-packages\vizdoom\examples use vscode to run this

from vizdoom import * import random, time

game = DoomGame() game.load_config("../config/basic.cfg") game.init()

shoot = [0,0,1] left = [1,0,0] right = [0,1,0]

episodes = 10 for i in range(episodes): game.new_episode() while not game.is_episode_finished(): state = game.get_state() img = state.image_buffer misc = state.game_variables action = random.choice([shoot, left, right]) # A random agent reward = game.make_action(action) time.sleep(0.02) # Just to make it slower print("Total reward: " + str(game.get_total_reward()))

and got this D:#Git\Python>python vizdoom.py Traceback (most recent call last): File "vizdoom.py", line 1, in from vizdoom import * File "D:#Git\Python\vizdoom.py", line 4, in game = DoomGame() NameError: name 'DoomGame' is not defined

im not sure what kind of problem am i running to

since i dont really understand the installing step so any problem is possible to make by me, im very sorry for such unclear question,and ive been searching for solution for a long time and i still cant figure it out. if i miss any information for my question,please let me know. thank you for your apply.

oh ! i can run vizdoom.exe,dont know would that help?

New versions of setuptools warns about:

SetuptoolsDeprecationWarning:     Installing 'vizdoom.gym_wrapper' as data is deprecated, please list it in `packages`.
    !!


    ############################
    # Package would be ignored #
    ############################
    Python recognizes 'vizdoom.gym_wrapper' as an importable package,
    but it is not listed in the `packages` configuration of setuptools.

    'vizdoom.gym_wrapper' has been automatically added to the distribution only
    because it may contain data files, but this behavior is likely to change
    in future versions of setuptools (and therefore is considered deprecated).

    Please make sure that 'vizdoom.gym_wrapper' is included as a package by using
    the `packages` configuration field or the proper discovery methods
    (for example by using `find_namespace_packages(...)`/`find_namespace:`
    instead of `find_packages(...)`/`find:`).

    You can read more about "package discovery" and "data files" on setuptools
    documentation page.


!!

  check.warn(importable)
E:\Python37\lib\site-packages\setuptools\command\build_py.py:202: SetuptoolsDeprecationWarning:     Installing 'vizdoom.scenarios' as data is deprecated, please list it in `packages`.
    !!


    ############################
    # Package would be ignored #
    ############################
    Python recognizes 'vizdoom.scenarios' as an importable package,
    but it is not listed in the `packages` configuration of setuptools.

    'vizdoom.scenarios' has been automatically added to the distribution only
    because it may contain data files, but this behavior is likely to change
    in future versions of setuptools (and therefore is considered deprecated).

    Please make sure that 'vizdoom.scenarios' is included as a package by using
    the `packages` configuration field or the proper discovery methods
    (for example by using `find_namespace_packages(...)`/`find_namespace:`
    instead of `find_packages(...)`/`find:`).

    You can read more about "package discovery" and "data files" on setuptools
    documentation page.


!!

As in the title, this might be a nice addition. Not sure if it's possible to make it also work with Sphinx. They should use the pydocstyle and Google styles so that they have a standard formatting.

This consists of a few subtasks:

• Create Farama-like documentation generated by sphinx.
• Figure out what is a proper way to document Gym/Gymnasium API and core API (pybind11 module) and generate sphinx docs for them (and migrate old docs to the new format).
• Have the documentation website be at .farama.org.
• Include the standard Farama code of conduct.

A workflow for building for Linux (manylinux?), macOS (Intel only?) and Windows (optional?) wheels using GitHub Actions (currently, ViZDoom is only distributed as source distribution, except for Windows, where wheels are provided) needs to be created. It should run when a Release is published on GitHub.