Page 1 of 1

graphics & sound bugs

Posted: 09 Aug 2006, 00:51
by Gari
Hi,

I recently installed the latest release of spring on my linux distro (kubuntu), using the new svn repositorie. I tried to play (xtape on smalldivide against aai) and it worked quite well, however I have some minor bugs (minor as I can still play with them).

The first one concerns the graphics : shots dont appear. I mean, I don's see any "bullet" or any other "laser shot" when units are firing. Moreover, smoke appears "weird".
The second one concerns the sound. Sometimes, I don't really know when, some errors appear in the console, telling that it cannot play a sound.

Here are some screenshots :
The weird smoke :
Image

The shoot bug :
Image

And the sound bug :
Image

thanks !

Posted: 09 Aug 2006, 01:10
by jcnossen
You need to copy the shaders from trunk/game/shaders and the data from trunk/game/bitmaps to your spring datadir.

Posted: 09 Aug 2006, 01:22
by Gari
Thanks. I just did it ; it didn't change a thing :s The smoke and shots are still bad.

Posted: 09 Aug 2006, 05:55
by Gari
I found (guessed :p) what the event about the missing sound was : the destruction of something.
When a unit or building is destroyed, the error message about the sound not possible to find appears.

Posted: 10 Aug 2006, 02:54
by Gari
Reinstalling using keithjr's setup guide resolved the bugs. Weird :)

Posted: 10 Aug 2006, 09:01
by Acidd_UK
http://taspring.clan-sy.com/phpbb/viewt ... 727#103727

I have exactly this problem when I play using a self-compiled version. When I compile it myself, I get lots of warnings like this:

FBO.obj : warning LNK4217: locally defined symbol ___glewDeleteFramebuffersEXT imported in function "public: virtual __thiscall FBO::~FBO(void)" (??1FBO@@UAE@XZ)
TerrainVertexBuffer.obj : warning LNK4217: locally defined symbol ___glewDeleteBuffersARB imported in function "public: void __thiscall terrain::VertexBuffer::Free(void)" (?Free@VertexBuffer@terrain@@QAEXXZ)

There's 31 glew-related warnings like this in total - I suspect they're causing these graphical issues...

Posted: 10 Aug 2006, 12:08
by Tobi
No they're normal and they don't cause the graphical glitches - the glitches are caused by outdated datafiles.

Posted: 10 Aug 2006, 12:53
by clericvash
From that shot i see the GUI has finally got better buttons, the fire at will etc stuff is amazingly hard to see for me, can't wait to see those new buttons.

Posted: 10 Aug 2006, 17:20
by nobody2u
Thats the new GUI? Looks (a little) better than the current one, but what does "fight" mean :?

Posted: 10 Aug 2006, 18:28
by Masse
thats not the new gui damn it :P its improved old one

Posted: 10 Aug 2006, 18:56
by ILMTitan
@nobody2u Fight is like patrol, but doesn't automaticly repeat.

Posted: 10 Aug 2006, 22:00
by hazard
I really want those buttons.

Then I could see if my units have orders to shoot or not.

Posted: 29 Oct 2006, 12:15
by hyinennn
I've got the same graphical problems. When I looked in infolog.txt it had these lines which caught my eye:

Section resources\graphics\projectiletextures missing in file gamedata/resources.tdf
Section resources\graphics\projectiletextures missing in file gamedata/resources.tdf
Section resources\graphics\groundfx missing in file gamedata/resources.tdf
Section resources\graphics\groundfx missing in file gamedata/resources.tdf

Could anyone help? :(

Posted: 30 Oct 2006, 18:30
by hyinennn
Nevermind, I got the game working now :-)

Posted: 30 Oct 2006, 21:46
by Tobi
for anyone else experiencing this later, no need to res the thread: erasing your 0.72 data tarball and grabbing the 0.73 one from berlios will solve it. (dont forget to copy over mods & maps)