white screen.

Just downloaded Vega Strike and need help? Have a question but don't know where to start? Ask here.
Post Reply
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

white screen.

Post by jbmuffat »

Good evening.
Having some problems with the docking, I decided to delate Vega Strike and to re-install it.
But now, when loading the game, all I have is a white screen and then it crash.

I am on Ubuntu 16.04

Any help?
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

Where are you installing it from?

Edit

There is currently no supported Binary release, if you're getting it from a repository it has nothing to do with us.

Many of the binaries nowadays do not support Ubuntu 16.04 or newer. However some forks make an attempt. I for example have a fork: https://github.com/Taose/Vegastrike-taose the Master branch should be compilable on your system. (Though I would advise upgrading your ubuntu).

You can try installing that using the instructions: https://github.com/Taose/Vegastrike-tao ... w-to-Build

Please let me know if anything is unclear or it still doesn't work.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

I have loaded it with App Grid and with Synaptic.
I'l try to re-install it later.
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

Yeah that will be a problem then. Unfortunately, it has to be installed from source.

The reasons are quite numerous.

1. The FFMPEG is unmaintained and causes a lot of problems when installing as does Ogre and Boost.
2. C++ the language in which the majority of the game is coded has evolved and parts of the game no longer work the way they should.

We appreciate your time ^-^.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
TBeholder
Elite Venturer
Elite Venturer
Posts: 753
Joined: Sat Apr 15, 2006 2:40 am
Location: chthonic safety

Re: white screen.

Post by TBeholder »

Unfortunately, packages are not properly maintained. For a while code and data packages were from different versions...
"Two Eyes Good, Eleven Eyes Better." -Michele Carter
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

Hello
I'm sorry Itusa but I don't understand what you want me to do.
For exemple: where is the source?
Have a good afternoon.
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

Right there are at least two versions of the "source".

Official: http://vegastrike.sourceforge.net/getfiles
Fork: https://github.com/Taose/Vegastrike-taose/releases

I'd prefer the fork (since that's the only one I can get working myself). The instructions may be unclear but largely...

Clone the Master (or grab a zipped copy).
navigate to the engine directory.
Create "Build Directory"
Navigate to the build directory.
Run from terminal "cmake ../"

At this stage you may find that there are some dependencies lacking, I would appreciate it if you could tell me which ones.

Once this has been completed: Run "make"

Navigate up to the Vegastrike directory and create a new directory called bin.

Then copy vegastrike and vssetup from the build directory created earlier to the bin directory. Run the game from terminal while in the bin folder using ./vegastrike. You don't actually need the vegaserver/mesh tools.

https://github.com/Taose/Vegastrike-tao ... w-to-Build

It was largely based on the instructions by Klauss.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
TBeholder
Elite Venturer
Elite Venturer
Posts: 753
Joined: Sat Apr 15, 2006 2:40 am
Location: chthonic safety

Re: white screen.

Post by TBeholder »

"Two Eyes Good, Eleven Eyes Better." -Michele Carter
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

I must be stupid but cmake does not run.
I am in the Buil directory, i run "cmake../" and the anser is that ubuntu can't find any file or directory.
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

"user@computer$ cmake ../"

The space between cmake and the '../' is important.

Do you have cmake installed? (apt-get install cmake).

"../" is command line short cut to mean the directory above. So ../../ would mean going up two directory levels. (Assuming 1st / 2nd / 3rd then ../../ would jump from 3rd to 1st)

Honestly, don't worry about it, we don't expect everyone to know how to use the terminal, while simple it can sometimes be a steep learning curve, so we'll guide you through the process, it's just going to take a bit longer.

Your directory structure (once extracted) should look something...

Vegastrike/
  • engine/
    • build/
      • You want to be in this directory
      src/
      CMakeList.txt
      ...etc
    data/
    • lotsastuff

@TBeholder, the SVN will not compile on Ubuntu 16.04, I know, I've tried. It's a bad source.

Edit: It doesn't actually matter what you call the build directory, it's not important, you'll just need to remember the name later.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

Thank you. I'll try it tomorrow.
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

How'd it go?
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

To Itusa:

Heer the result of cmake:
jb@jb-HP-Pavilion-Notebook:~/vegastrike/engine/BuildDirectory$ cmake ../
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.12")
++ Using Internal Boost
CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY OPENGL_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.5/Modules/FindOpenGL.cmake:172 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:725 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/jb/vegastrike/engine/BuildDirectory/CMakeFiles/CMakeOutput.log".
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

And how do you use the command "make"?
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

Gotta get the cmake to run first.

Have you installed "Build Essential" and "freeglut3-dev"?

You're missing the OpenGL libraries.

Edit:

I'm making sure to put some instructions together for Ubuntu 16.10 (should work for Ubuntu 16.04 as well) https://github.com/Taose/Vegastrike-tao ... w-to-Build Largely the Fedora instructions should work but there are some package name differences.

Edit 2:

Make explained---

Once you have run the cmake completely (with no errors), it'll produce all the necessary files in order for make to function properly. Make is effectively the compiler, it combines the configuration set up from cmake with the compiler g++ in our case, to produce the executables.

Simply go into the build directory and type "make" and press enter. It will then do everything automagically. It should be able to find the makefiles that should be inside that directory (thanks to cmake) and thus follow all necessary protocols. The vegastrike executable will be initially in there (but it has to be moved in order for it to work).

On some machines, using make with the "jobs option" or "-j#" where # is the number of cores (or sometimes more depending on your system) can decrease the time it takes to compile vega strike.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
loki1950
The Shepherd
Posts: 5841
Joined: Fri May 13, 2005 8:37 pm
Location: Ottawa
Contact:

Re: white screen.

Post by loki1950 »

For a test build and even for regular dev work I run everything in userland and then a symbolic link from the build folder to the bin folder of the data hierarchy works just fine till you get a running binary saves that install step till everything works :wink:

Enjoy the Choice :)
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

o.O symbolic link huh, I never thought about that; could be useful. I suppose I could use specific symbolic links to refer to different build-releases as well. Interesting. Thanks Loki ^-^

update: Tip was added the Vega Strike ~Taose wiki :D
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

Good morning,
"Build Essential" and "freeglut3-dev" are installed
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

and it's still showing up: Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY OPENGL_INCLUDE_DIR)

Interesting...

edit:

what about "mesa-common-dev" or similar?

edit 2:

There's a list of potentially necessary files here:

https://github.com/Taose/Vegastrike-tao ... quisites-1

So if you do have mesa-common-dev, please do check the rest of them. One of these days I'm going to have to set up a clean ubuntu virtual machine...
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

I'm sending you what I've done and the result
jb@jb-HP-Pavilion-Notebook:~/vegastrike/Vegastrike-taose-0.5/engine/Build Directory$ sudo apt-get install gcc-5 g++-5
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
gcc-5-base:i386 libjs-jquery-ui libjs-jquery-ui-theme-smoothness libjs-requirejs libjs-requirejs-text libsimgearcore2017.1.2 libsimgearscene2017.1.2 linux-headers-4.4.0-64
linux-headers-4.4.0-64-generic linux-headers-4.4.0-64-lowlatency linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic linux-headers-4.4.0-66-lowlatency
linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-headers-4.4.0-67-lowlatency linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic
linux-headers-4.4.0-70-lowlatency linux-image-4.4.0-64-generic linux-image-4.4.0-64-lowlatency linux-image-4.4.0-66-generic linux-image-4.4.0-66-lowlatency
linux-image-4.4.0-67-generic linux-image-4.4.0-67-lowlatency linux-image-4.4.0-70-generic linux-image-4.4.0-70-lowlatency linux-image-extra-4.4.0-64-generic
linux-image-extra-4.4.0-66-generic linux-image-extra-4.4.0-67-generic linux-image-extra-4.4.0-70-generic linux-signed-image-4.4.0-64-generic
linux-signed-image-4.4.0-64-lowlatency linux-signed-image-4.4.0-66-generic linux-signed-image-4.4.0-66-lowlatency linux-signed-image-4.4.0-67-generic
linux-signed-image-4.4.0-67-lowlatency linux-signed-image-4.4.0-70-generic linux-signed-image-4.4.0-70-lowlatency snap-confine
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
The following additional packages will be installed:
cpp-5 gcc-5-base gcc-5-base:i386 gcc-6-base gcc-6-base:i386 lib32gcc1 lib32stdc++6 libasan2 libatomic1 libcc1-0 libcilkrts5 libgcc-5-dev libgcc1 libgcc1:i386 libgfortran3
libgomp1 libgomp1:i386 libitm1 liblsan0 libmpx0 libobjc4 libquadmath0 libstdc++-5-dev libstdc++6 libstdc++6:i386 libtsan0 libubsan0
Paquets suggérés :
gcc-5-locales g++-5-multilib gcc-5-doc libstdc++6-5-dbg gcc-5-multilib libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg libstdc++-5-doc
Les paquets suivants seront mis à jour :
cpp-5 g++-5 gcc-5 gcc-5-base gcc-5-base:i386 gcc-6-base gcc-6-base:i386 lib32gcc1 lib32stdc++6 libasan2 libatomic1 libcc1-0 libcilkrts5 libgcc-5-dev libgcc1 libgcc1:i386
libgfortran3 libgomp1 libgomp1:i386 libitm1 liblsan0 libmpx0 libobjc4 libquadmath0 libstdc++-5-dev libstdc++6 libstdc++6:i386 libtsan0 libubsan0
29 mis à jour, 0 nouvellement installés, 0 à enlever et 5 non mis à jour.
Il est nécessaire de prendre 31,5 Mo dans les archives.
Après cette opération, 629 ko d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Réception de:1 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main i386 gcc-6-base i386 6.2.0-3ubuntu11~16.04 [16,7 kB]
Réception de:2 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 gcc-6-base amd64 6.2.0-3ubuntu11~16.04 [16,7 kB]
Réception de:3 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libgcc1 amd64 1:6.2.0-3ubuntu11~16.04 [38,2 kB]
Réception de:4 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main i386 libgcc1 i386 1:6.2.0-3ubuntu11~16.04 [48,0 kB]
Réception de:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 lib32gcc1 amd64 1:6.2.0-3ubuntu11~16.04 [47,8 kB]
Réception de:6 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main i386 libstdc++6 i386 6.2.0-3ubuntu11~16.04 [434 kB]
Réception de:7 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libstdc++6 amd64 6.2.0-3ubuntu11~16.04 [400 kB]
Réception de:8 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main i386 libgomp1 i386 6.2.0-3ubuntu11~16.04 [80,0 kB]
Réception de:9 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libgomp1 amd64 6.2.0-3ubuntu11~16.04 [74,0 kB]
Réception de:10 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libitm1 amd64 6.2.0-3ubuntu11~16.04 [27,9 kB]
Réception de:11 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libatomic1 amd64 6.2.0-3ubuntu11~16.04 [9 186 B]
Réception de:12 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libasan2 amd64 5.4.1-2ubuntu1~16.04 [264 kB]
Réception de:13 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 liblsan0 amd64 6.2.0-3ubuntu11~16.04 [117 kB]
Réception de:14 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libtsan0 amd64 6.2.0-3ubuntu11~16.04 [261 kB]
Réception de:15 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libubsan0 amd64 6.2.0-3ubuntu11~16.04 [108 kB]
Réception de:16 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libcilkrts5 amd64 6.2.0-3ubuntu11~16.04 [40,8 kB]
Réception de:17 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libmpx0 amd64 5.4.1-2ubuntu1~16.04 [9 762 B]
Réception de:18 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libquadmath0 amd64 6.2.0-3ubuntu11~16.04 [132 kB]
Réception de:19 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 g++-5 amd64 5.4.1-2ubuntu1~16.04 [8 455 kB]
Réception de:20 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 gcc-5 amd64 5.4.1-2ubuntu1~16.04 [8 574 kB]
Réception de:21 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libstdc++-5-dev amd64 5.4.1-2ubuntu1~16.04 [1 432 kB]
Réception de:22 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libgcc-5-dev amd64 5.4.1-2ubuntu1~16.04 [2 232 kB]
Réception de:23 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libcc1-0 amd64 6.2.0-3ubuntu11~16.04 [31,1 kB]
Réception de:24 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 cpp-5 amd64 5.4.1-2ubuntu1~16.04 [7 802 kB]
Réception de:25 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libobjc4 amd64 6.2.0-3ubuntu11~16.04 [111 kB]
Réception de:26 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 libgfortran3 amd64 6.2.0-3ubuntu11~16.04 [270 kB]
Réception de:27 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 lib32stdc++6 amd64 6.2.0-3ubuntu11~16.04 [420 kB]
Réception de:28 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 gcc-5-base amd64 5.4.1-2ubuntu1~16.04 [17,3 kB]
Réception de:29 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main i386 gcc-5-base i386 5.4.1-2ubuntu1~16.04 [17,3 kB]
31,5 Mo réceptionnés en 30s (1 039 ko/s)
(Lecture de la base de données... 747108 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../gcc-6-base_6.2.0-3ubuntu11~16.04_amd64.deb ...
Déconfiguration de gcc-6-base:i386 (6.0.1-0ubuntu1) ...
Dépaquetage de gcc-6-base:amd64 (6.2.0-3ubuntu11~16.04) sur (6.0.1-0ubuntu1) ...
Préparation du dépaquetage de .../gcc-6-base_6.2.0-3ubuntu11~16.04_i386.deb ...
Dépaquetage de gcc-6-base:i386 (6.2.0-3ubuntu11~16.04) sur (6.0.1-0ubuntu1) ...
Préparation du dépaquetage de .../libgcc1_1%3a6.2.0-3ubuntu11~16.04_i386.deb ...
Déconfiguration de libgcc1:amd64 (1:6.0.1-0ubuntu1) ...
Dépaquetage de libgcc1:i386 (1:6.2.0-3ubuntu11~16.04) sur (1:6.0.1-0ubuntu1) ...
Préparation du dépaquetage de .../libgcc1_1%3a6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libgcc1:amd64 (1:6.2.0-3ubuntu11~16.04) sur (1:6.0.1-0ubuntu1) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.23-0ubuntu7) ...
Paramétrage de gcc-6-base:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de gcc-6-base:i386 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libgcc1:amd64 (1:6.2.0-3ubuntu11~16.04) ...
Paramétrage de libgcc1:i386 (1:6.2.0-3ubuntu11~16.04) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.23-0ubuntu7) ...
(Lecture de la base de données... 747108 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../lib32gcc1_1%3a6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de lib32gcc1 (1:6.2.0-3ubuntu11~16.04) sur (1:6.0.1-0ubuntu1) ...
Préparation du dépaquetage de .../libstdc++6_6.2.0-3ubuntu11~16.04_amd64.deb ...
Déconfiguration de libstdc++6:i386 (5.4.0-6ubuntu1~16.04.4) ...
Dépaquetage de libstdc++6:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libstdc++6_6.2.0-3ubuntu11~16.04_i386.deb ...
Dépaquetage de libstdc++6:i386 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libgomp1_6.2.0-3ubuntu11~16.04_amd64.deb ...
Déconfiguration de libgomp1:i386 (5.4.0-6ubuntu1~16.04.4) ...
Dépaquetage de libgomp1:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libgomp1_6.2.0-3ubuntu11~16.04_i386.deb ...
Dépaquetage de libgomp1:i386 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libitm1_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libitm1:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libatomic1_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libatomic1:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libasan2_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de libasan2:amd64 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../liblsan0_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de liblsan0:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libtsan0_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libtsan0:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libubsan0_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libubsan0:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libcilkrts5_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libcilkrts5:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libmpx0_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de libmpx0:amd64 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libquadmath0_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libquadmath0:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../g++-5_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de g++-5 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../gcc-5_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de gcc-5 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libstdc++-5-dev_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de libstdc++-5-dev:amd64 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libgcc-5-dev_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de libgcc-5-dev:amd64 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libcc1-0_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libcc1-0:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../cpp-5_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de cpp-5 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libobjc4_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libobjc4:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../libgfortran3_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de libgfortran3:amd64 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../lib32stdc++6_6.2.0-3ubuntu11~16.04_amd64.deb ...
Dépaquetage de lib32stdc++6 (6.2.0-3ubuntu11~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../gcc-5-base_5.4.1-2ubuntu1~16.04_i386.deb ...
Déconfiguration de gcc-5-base:amd64 (5.4.0-6ubuntu1~16.04.4) ...
Dépaquetage de gcc-5-base:i386 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Préparation du dépaquetage de .../gcc-5-base_5.4.1-2ubuntu1~16.04_amd64.deb ...
Dépaquetage de gcc-5-base:amd64 (5.4.1-2ubuntu1~16.04) sur (5.4.0-6ubuntu1~16.04.4) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.23-0ubuntu7) ...
Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
Paramétrage de lib32gcc1 (1:6.2.0-3ubuntu11~16.04) ...
Paramétrage de libstdc++6:i386 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libstdc++6:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libgomp1:i386 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libgomp1:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libitm1:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libatomic1:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de gcc-5-base:amd64 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de gcc-5-base:i386 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de libasan2:amd64 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de liblsan0:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libtsan0:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libubsan0:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libcilkrts5:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libmpx0:amd64 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de libquadmath0:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de cpp-5 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de libcc1-0:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libgcc-5-dev:amd64 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de gcc-5 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de libstdc++-5-dev:amd64 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de g++-5 (5.4.1-2ubuntu1~16.04) ...
Paramétrage de libobjc4:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de libgfortran3:amd64 (6.2.0-3ubuntu11~16.04) ...
Paramétrage de lib32stdc++6 (6.2.0-3ubuntu11~16.04) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.23-0ubuntu7) ...
jb@jb-HP-Pavilion-Notebook:~/vegastrike/Vegastrike-taose-0.5/engine/Build Directory$ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 60 --slave /usr/bin/g++ g++ /usr/bin/g++-5
update-alternatives: utilisation de « /usr/bin/gcc-5 » pour fournir « /usr/bin/gcc » (gcc) en mode automatique
jb@jb-HP-Pavilion-Notebook:~/vegastrike/Vegastrike-taose-0.5/engine/Build Directory$ cmake ..:
CMake Error: The source directory "/home/jb/vegastrike/Vegastrike-taose-0.5/engine/Build Directory/..:" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
jb@jb-HP-Pavilion-Notebook:~/vegastrike/Vegastrike-taose-0.5/engine/Build Directory$ cmake ../
++ Using Internal Boost
!! Why you no have GL?
CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find GLUT (missing: GLUT_glut_LIBRARY GLUT_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.5/Modules/FindGLUT.cmake:126 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:735 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/jb/vegastrike/Vegastrike-taose-0.5/engine/Build Directory/CMakeFiles/CMakeOutput.log".
jb@jb-HP-Pavilion-Notebook:~/vegastrike/Vegastrike-taose-0.5/engine/Build Directory$
I will understand if you want to stop.
Have a happy sunday.
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

I...dun read french at the best of times >.<; So you'll have to bear with me. I'm happy to support users of the Vega Strike community and improve the software where at all possible to make it easier. (We haven't got a binary yet, sorry).

Now, cmake is swearing quite strongly that you neither GL nor GLUT

You don't need GCC5...gcc 3 would be just fine. (Edit: GCC or g++ in ubuntu's case usually is the preferred compiler, but the compiler has little to do with the GL libraries).

Code: Select all

sudo apt-get install git cmake gcc gcc-c++ python python-dev libglu1-mesa-dev freeglut3-dev mesa-common-dev install libopenal0a libopenal-dev libsdl2-dev  libvorbis-dev libjpeg-dev libpng-dev
That command should install everything you need...and probably a few things that might not be essential for ubuntu. Just copy and pasta.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
jbmuffat
Explorer
Explorer
Posts: 13
Joined: Sat Jan 21, 2017 9:53 pm

Re: white screen.

Post by jbmuffat »

it answers:
" there is no version of libopenal0a but it is on the database. It means that the package is meessing, outdated or on an other source.
Impossible to open gcc-c+ package
impossible to find like the expression gcc-c+
impossible to find the package "install"
"libopenal0aé has no version that can be installed
Itusa
Hunter
Hunter
Posts: 85
Joined: Wed Jul 30, 2014 5:59 pm

Re: white screen.

Post by Itusa »

Try: libopenal1

"sudo apt-get install libopenal1"

You should already have g++ at any rate. libopenal is a package that is declared differently to different package managers so...

At any rate, you can try cmake again.
Operating System: (Linux) Ubuntu 16.10 (Yakkety)
Vegastrike-taose: 0.5.1
TBeholder
Elite Venturer
Elite Venturer
Posts: 753
Joined: Sat Apr 15, 2006 2:40 am
Location: chthonic safety

Re: white screen.

Post by TBeholder »

there is no version of libopenal0a but it is on the database. It means that the package is meessing, outdated or on an other source.
Huh.
If you have problems with strange versions, broken, and so on, search openal in package manager (Synaptic, if you use Debian or derived distro) to see how they are really named, whether you have obvious problems with those (like it's marked as broken, or installed files aren't, etc. Then select and install/reinstall those packages (lib*-dev) manually.
"Two Eyes Good, Eleven Eyes Better." -Michele Carter
Post Reply