Author Topic: crash on unit selection  (Read 2193 times)

treba

  • Guest
crash on unit selection
« on: 28 June 2011, 15:52:27 »
hey all,

just installed megaglest on my eeepc 1101ha (gma 500 graphics chip) under ubuntu 11.04 and the emgd driver. the game seems to run fine under lowest settings, but as soon as i select any unit, i get the following error:
(click to show/hide)

tested it also with vanilla glest, same story. so it's some deep engine error.

tomreyn

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: crash on unit selection
« Reply #1 on: 28 June 2011, 16:44:15 »
Hmm, this looks more like a graphics driver issue to me - according to the backtrace this segmentation fault happened while the EMGD OpenGL driver was rendering. This driver is both rather young and licensing issues make it depend on a proprietary core.
https://secure.wikimedia.org/wikipedia/en/wiki/Intel_GMA#GMA_500
https://secure.wikimedia.org/wikipedia/en/wiki/Intel_GMA#GMA_500_on_Linux
https://secure.wikimedia.org/wikipedia/en/wiki/System_Controller_Hub#GMA_500_Linux_support
https://launchpad.net/~gma500/+archive/emgd
http://edc.intel.com/Software/Downloads/EMGD/#features

The drivers available for this GPU may provide stable 3D operation at some point but this may not be just yet.

Aside of this, I'm not sure whether the components of this system make it match the minimum system requirements (see README file).
« Last Edit: 28 June 2011, 17:00:09 by tomreyn »
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

will

  • Golem
  • ******
  • Posts: 783
    • View Profile
Re: crash on unit selection
« Reply #2 on: 28 June 2011, 17:08:39 »
It might help to install xorg edgers.

Its extra interesting if you already have...

treba

  • Guest
Re: crash on unit selection
« Reply #3 on: 29 June 2011, 05:45:29 »
thanks for the fast replies.
@summary: i don't think xorg edgers will really help, because in order to run the emgd driver, i had to use an older version of xorg (1.9 instead of ubuntu default 1.10). the emgd driver is currently by far the best driver for the gma 500, but it's somehow behind the regular releases and has to be installed from a launchpad repository.

@tomreyn: it's true that it has somethink to do with the driver, i think if i remember correctly, i had the same problem with the almost similar windows driver. i just wondered, whether it can be fixed on the side of the engine rather than the driver.
but maybe i just have to wait for the driver to get better or the open source driver to become ready.

besides, the system requirements should be fine, althought the cpu is maybe a little bit slow. the chip and driver support opengl 2.1, 1 gig ram is there and a 1.33ghz cpu.

tomreyn

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: crash on unit selection
« Reply #4 on: 29 June 2011, 12:17:08 »
thanks for the fast replies.
@summary: i don't think xorg edgers will really help, because in order to run the emgd driver, i had to use an older version of xorg (1.9 instead of ubuntu default 1.10). the emgd driver is currently by far the best driver for the gma 500, but it's somehow behind the regular releases and has to be installed from a launchpad repository.

I agree, the Ubuntu PPA at https://launchpad.net/~gma500/+archive/emgd which provides the driver also comes (via package dependencies) with its own patched xserver-xorg replacement package for Natty (Ubuntu 11.04) which is actually an X.org 1.9 version (it just pretends to be a 1.10 version to make it installable on Ubuntu Natty which ships 1.10 by default; the version string is: 1.10.9-down1.9.2.901.2+git20101129+server-1.9-branch.65f2ab20-0ubuntu0sarvatt2~natty).

@tomreyn: it's true that it has something to do with the driver, i think if i remember correctly, i had the same problem with the almost similar windows driver. i just wondered, whether it can be fixed on the side of the engine rather than the driver.
but maybe i just have to wait for the driver to get better or the open source driver to become ready.

I would be the wrong person to answer the question whether it can be fixed / worked around from within the game (I assume it possbily could, but it would involve a lot of testing, snce there are no known criteria of what works and what does not). But this would seem like the wrong approach. While OpenGL is a somewhat problematic standard it is good to exist, since you need such standards everyone agrees on (across multiple hardwares + drivers) to have a common foundation you can write code for. Otherwise game developers would end up becoming graphics driver workaround writers for every GPU out there, which (though it partially should not have to happen - that's what standards are there for - does have to happen sometimes due to various shortcomings, mostly in existing graphics drivers) is much less than ideal.

So, in your case, having bought a hardware which its vendor only provides an outdated and somewhat crippled driver for, I'm afraid you will indeed need to wait + hope for availability of better driver support. :-/

besides, the system requirements should be fine, althought the cpu is maybe a little bit slow. the chip and driver support opengl 2.1, 1 gig ram is there and a 1.33ghz cpu.

The CPU is indeed a bit slow, and a single core 1.33 GHz CPU is below the (admittedly somewhat artificial and imprecise) statement on minimum requirements (single core 1.5 GHz CPU) we have in the README. Apparently the driver does not fully support the  OpenGL 2.1 specification, otherwise those issues you run into should not happen (unless it is running out of RAM etc.)

The "1.0 GB RAM" listed as a requirement in the README refers to a minimum of 1 GB free RAM for exclusive use by the game. If you have a total of 1 GB system memory then a good part of it will be used by the GPU (which depends on 'stealing' RAM from the system memory), and another part by the operating system and other processes, leaving a maximum of 650 MB RAM for exclusive use by the game.

Something you could ty is to experiment with texture compression (an option which can be switched within the game) as well as to add another GB of RAM (this system can have a maximum of 2 x 1.0 GB RAM).
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

 

anything