The install instructions should be improved about vizdoom

[wjaskowski]

Mea culpa, again. Thanks. fsp.py works! I'll check other things when on Xs.

On 25 January 2016 at 17:47, Marek Wydmuch [email protected] wrote:

The problem probably lies in wrong link to doom executable (missing 'z'
between 'vizia' and 'doom') - it should be viziazdoom.

—
Reply to this email directly or view it on GitHub
#16 (comment).

[mihahauke]

was ../../bin/python/vizia.so correctly in bin directory?

[wjaskowski]

You are right. I forgot to run the compiler :)

So now I get when I run it over ssh (no X server):

➜  python git:(master) ✗ ./essentials.py
Traceback (most recent call last):
  File "./essentials.py", line 67, in <module>
    game.init()
vizia.doom_unexpected_exit_exception: Controlled ViziaZDoom instance exited
unexpectedly.

This is expected to some extent, but error message is probably not clear.

Is there any example showing how to run it without X server?

Btw., for some examples I obviously needed:

sudo apt-get install python-opencv

On 25 January 2016 at 13:47, Michał Kempka [email protected] wrote:

was ../../bin/python/vizia.so correctly in bin directory?

—
Reply to this email directly or view it on GitHub
#16 (comment).

[mihahauke]

Sorry, didn't thing that anyone would like to try something without Xserver for starters.
fps.py will work without graphics.
Or just add "game.set_window_visible(False)" to any example before init.
We'll add some build and first run instructions soon.

[wjaskowski]

It does not:

➜  python git:(master) ✗ grep set_window_visible -B 1 -A 1 fps.py
game.set_screen_resolution(res.RES_320X240)
game.set_window_visible(False)
game.init()
➜  python git:(master) ✗ ./fps.py
Traceback (most recent call last):
  File "./fps.py", line 21, in <module>
    game.init()
vizia.doom_unexpected_exit_exception: Controlled ViziaZDoom instance exited unexpectedly.

[mihahauke]

For now we have no idea what's wrong but you could try:

• checking if viziazdoom links properly to REPO_DIRECTORY/bin/viziazdoom
• checking if viziazdoom and viziazdoom.pk3 are present in REPO_DIRECTORY/bin
• sudo apt-get install build-essential zlib1g-dev libsdl2-dev libjpeg-dev nasm tar libbz2-dev libgtk2.0-dev cmake git libfluidsynth-dev libgme-dev libopenal-dev timidity

[mwydmuch]

The problem probably lies in wrong link to doom executable (missing 'z' between 'vizia' and 'doom') - it should be viziazdoom.

[elanmart]

Hey,
I also have had some troubles installing the software, specifically:

sudo apt-get install libsdl2-dev fails on my machine, had to build from sources.
Then, after running cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_PYTHON=ON -DBUILD_JAVA=OFF
I get the following error:

...
-- Found PythonInterp: /home/marcin/anaconda/bin/python2.7 (found suitable version "2.7.11", minimum required is "2.7") 
-- Found PythonInterp: /home/marcin/anaconda/bin/python2.7 (found version "2.7.11") 
-- Found components for NumPy
-- NUMPY_ROOT_DIR    = /usr/local
-- NUMPY_INCLUDES    = /home/marcin/anaconda/lib/python2.7/site-packages/numpy/core/include
-- NUMPY_LIBRARIES   = 
-- NUMPY_API_VERSION = 1.10.4
-- Boost version: 1.60.0
-- Found the following Boost libraries:
--   python
-- Configuring done
CMake Warning at /usr/local/share/cmake-3.3/Modules/FindPythonLibs.cmake:232 (add_library):
  Cannot generate a safe runtime search path for target vizdoompython because
  files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libpython2.7.so.1.0] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
      /home/marcin/anaconda/lib

  Some of these libraries may not be found correctly.
Call Stack (most recent call first):
  CMakeLists.txt:131 (python_add_module)


CMake Warning at vizdoom_src/src/CMakeLists.txt:840 (add_executable):
  Cannot generate a safe runtime search path for target vizdoom because files
  in some directories may conflict with libraries in implicit directories:

    runtime library [libz.so.1] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
      /home/marcin/anaconda/lib

  Some of these libraries may not be found correctly.

I'll try to fix this during weekend, but any tips would be appreciated.

Edit: using Ubuntu 14.04, python & numpy from anaconda distribution.

[mwydmuch]

Hi, elanmart

1. Thanks for Your interest in ViZDoom :)
2. What is exactly Your problem with apt-get install libsdl2-dev? Have You tried apt-get update and apt-get install -f?
3. Your default Python installation are conflicting with anaconda. Its only a warning, so Makefile should be generated. Python paths look fine, it should compile and work despite warnings.

You can always tell CMake where to look for Python libs using -DPYTHON_INCLUDE_DIR
i -DPYTHON_LIBRARY.

[elanmart]

What is exactly Your problem with apt-get install libsdl2-dev? Have You tried apt-get update and apt-get install -f?

For the record, the error was E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages, but it wasn't caused by the held packages. Anyway, this seems specific to my machine and I think can be ignored.

Your default Python installation are conflicting with anaconda. Its only a warning, so Makefile should be generated. Python paths look fine, it should compile and work despite warnings.

This was indeed unusual, after reinstalling python and downloading ViZDoom again, everything seems to work fine.

[yshahin]

What is the g++ command to compile the cpp files?

[mihahauke]

You could use e.g.:
g++ Basic.cpp -lboost_system -lvizdoom -L../../bin -../../vizdoom_api_src -Wl,-rpath=../../bin -o Basic

You could also use cmake with CMakeLists.txt from examples/c++ as a base .