Extremly slow framerates in Linux! (solved!)

[Maplesyrup]

Hi all,
I have been playing glest, which I rather enjoy. So I downloaded megaglest which appears to be even better. However, I cannot play megaglest due to the extremely slow frame rates on any of the 3d background menus and in the game. It shudders and stops constantly. I have disabled compiz, and tried both the latest and the last versions, both having the same problem. My computer isn't a gaming rig, having a core 2 duo 2.4ghz processor, 3Gb of ram and integrated graphics < is that enough to run this game. If anyone can help me it would be great!

update:  this issue is solved see here

[softcoder]

Please give full details of your operating system and video card hardware and what version of Mega-Glest you are running.

Paste the output of:

Windows:

glest_game.exe --version
glest_game.exe --opengl-info

Linux:

./glest --version
./glest --opengl-info

Thanks

[Maplesyrup]

Running lucid linux (10.04) 32bit
have integrated intel(R) Graphics Media Accelerator 450 OMHD
Tried megaglest 3.3.6, but now have 3.3.5, both have the same problem
Thanks

[titi]

Hi, some more questions:
 
Did you run glest on the same machine?
Which version of glest worked fine for you? The one from the ubuntu repositories ? Or did you install it using any kind of installer?
How did you install megaglest? Did you use the installer?

In general:
Glest form the ubuntu repositories comes with a very low  default screen resolution( 640x480? ).
MG starts up with 1024x768 by default. Go to the option ( best is ingame ) and switch down resolution to 640x480x16 or maybe 800x600x16 works too.
Then lower some of the other settings too ( shadows off! max light sources 1, maybe switch off 3d textures, but this will look worse )..
Then restart Megaglest ... Maybe it helps

In general your (and maybe all) integrated graphics cards are not very powerful, so don't expect too much.

[John.d.h]

I'm running the same operating system and I have the same problem with all types of Glest, and anything with 3D graphics, really.  My problem is that Ubuntu doesn't support 3D acceleration on my graphics card.  Maybe you're having the same problem?  Glest itself doesn't take much in the way of resources, so you should have way more than enough processor speed and RAM.  Megaglest shouldn't be much harder to run, but I could be wrong.

[softcoder]

Hey John did you a) install the native video drivers for you card (not the default Open source ones) and b) disable Compiz in the:

System->Preferences->Appearance->Visual Effects area?

Thanks

[John.d.h]

Yes on both counts.  The only drivers available from Via for Linux are outdated and basically worthless.  I have another computer where I can do my 3D stuff, but it's a hassle to switch back and forth between machines.

[Maplesyrup]

Yeah, normal glest runs absolutely fine on the same computer.
The one from repositories. Megaglest was installed using an installer.
I changed all the settings to low on megaglest, it changed nothing (well except how the game looks).
It could be my graphics, but when I had vista it played warcraft 3 and halo absolutely fine... I wonder if there is a way if I can see if the 3d graphics are working? John, did glest work fine on your 3d-lacking machine?

[John.d.h]

John, did glest work fine on your 3d-lacking machine?

No, all types of Glest give me equally horrible performance (roughly one frame per second ).  Even Blender, which is famously light, is cumbersome on my machine.

[titi]

I have no idea at the moment  

MG 3.3.6 should be running the same code to render the menus, so there shouldn't be a difference! 3.3.5 was ... a bit slow  .
( Is here maybe someone else who can establish these kind of problems? )

[Maplesyrup]

megaglest gives me about one frame per second. For some reason this is the only game I have played on ubuntu- on the same machine, that has given me any problems at all .
Yeah it is strange as glest and megaglest have almost identical menus yet there is such a dramatic difference! It doesn't seem like anyone is having these problems either.

[titi]

Which CPU do you use? AMD/Intel or something not so common like VIA?
Maybe you can compile a binary on your machine? Probably its a build issue, because our binary is build on ubuntu 8.04 ( there are good reasons for this! )

By the way:
Try to join the irc chat,  maybe people can halp faster when they get direct feedback. ( try it tomorrow! Today the developers are a bit rare there .... )
http://webchat.freenode.net/?&channels=glest

[Maplesyrup]

An intel core 2 duo 2.4ghz processor.
Oh ok, will join the chat and try and get some help there too.
Thanks for the brainstorming so far

[tomreyn]

The only drivers available from Via for Linux are outdated and basically worthless.

I'm not sure how fluid you are with Linux. If you'd like someone else to take another look at what hardware you have and whether there may be better drivers available I can do this. If interested, please PM the output of:

Code: [Select]

lspci -knnOr you could paste it into a spoiler message on this board.

[John.d.h]

I know how to do fairly basic command-line stuff in Linux, but I'm a bit over my head when it comes to drivers and that kind of thing, so I'd definitely appreciate the help.  I'll go ahead and send you a PM.

[softcoder]

Ok we just discovered that for some people on Linux you need to run the following from your mega-glesr root folder (by default this is in ~/megaglest):

Code: [Select]

mkdir lib_bkp
mv lib/* lib_bkp/
cp lib_bkp/libcurl* lib/
cp lib_bkp/libgnu* lib/
cp lib_bkp/libicu* lib/
cp lib_bkp/liblua* lib/
cp lib_bkp/libxerces* lib/

then re-run mega-glest:

./glest

[Dritominous]

Woo hoo!  That works!

Thanks!   

[softcoder]

And just for the record, the next release should offer even better performance (for the brave test out SVN trunk). Coming soon.

[ultifd]

Hmm, why is this thread stickied?
Is it because of this helpful... Well it is at the FAQ already, so...

Ok we just discovered that for some people on Linux you need to run the following from your mega-glesr root folder (by default this is in ~/megaglest):

Code: [Select]

mkdir lib_bkp
mv lib/* lib_bkp/
cp lib_bkp/libcurl* lib/
cp lib_bkp/libgnu* lib/
cp lib_bkp/libicu* lib/
cp lib_bkp/liblua* lib/
cp lib_bkp/libxerces* lib/

then re-run mega-glest:

./glest

[harvestman]

Hmm, why is this thread stickied?
Is it because of this helpful... Well it is at the FAQ already, so...

Ok we just discovered that for some people on Linux you need to run the following from your mega-glesr root folder (by default this is in ~/megaglest):

Code: [Select]

mkdir lib_bkp
mv lib/* lib_bkp/
cp lib_bkp/libcurl* lib/
cp lib_bkp/libgnu* lib/
cp lib_bkp/libicu* lib/
cp lib_bkp/liblua* lib/
cp lib_bkp/libxerces* lib/

then re-run mega-glest:

./glest

I just get the message "cp: cannot stat lib_bkp/libcurl* no such file or directory" whenever I type in the lines beginning cp...

What does this mean please?

[softcoder]

thats because in 3.5 not all the files are there since some are compiled right into the binary itself, so that message can be ignored.