8000 Common Issues · colobot/colobot Wiki · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Common Issues

Jump to bottom
Mateusz Przybył edited this page Feb 7, 2021 · 5 revisions

How to diagnose a crash?

Information which might be useful in finding the root cause of a crash are in the list below. If you report the issue to us, we'll probably ask you to send this information to us anyway.

  1. The crash error message window.
  2. The logs which you can see by running the game from console/terminal or in a log.txt file inside the directory of the game or the saves directory. Run the game with -loglevel debug or -loglevel trace flag.
  3. If the above doesn't contain any useful information, run the game through gdb 
$ gdb colobot
(gdb) run
...play the game until it crashes...
(gdb) backtrace
...copy paste what it outputs here...

The game crashes after splash screens on Linux and I have an Intel GPU

See this comment to know the most likely reason and for a list of possible solutions. In short: mesa drivers don't play well with old OpenGL versions.

For reference, you can force/change OpenGL version with some command line switches, e.g.

$ colobot -graphics gl33 -glprofile core -glversion 3.3

Available options:

  • graphics: gl14, gl21, or gl33. gl14 is default. This option changes the graphical engine, some GPU drivers works better with different engine.
  • glprofile: core, compatibility, or opengles.
  • glversion: combination of 2 numbers separated by single period. This option override detected version of OpenGL version supported by driver.

http://colobot.info || What is Colobot? || Colobot: Gold Edition project || TerranovaTeam

Clone this wiki locally
0