Run spring_multithreaded, with BA

/cheat
/give armbull_dead

Do you see the wreckage or not? Please tell your results and what gfx hardware/driver you have. Thanks!

I can see it:
8800GT
Driver: 8.17.12.8026
Win7 x64

I can see it:
nvidia 6800
driver version: 280.26
win xp 32bit
http://pastebin.com/s9y1t5XU

i can see it:

ubuntu 11.10 64 bit:

[f=0000000] GL version: 4.1.11005 Compatibility Profile Context
[f=0000000] GL vendor: ATI Technologies Inc.
[f=0000000] GL renderer: ATI Radeon HD 5700 Series
[f=0000000] GLSL version: 4.10
[f=0000000] GLEW version: 1.6.0
[f=0000000] GL info: FBO=1 NPOT=1 24bitDepth=0 ATiHacks=1

I see it, too.

ubuntu 10.04 64 bit, spring 84, tested with ba 7.31 and 7.32,
running a Radeon 5770 with Catalyst 11.11

I see it appears too next to commander.

Ubuntu 11.04 64 bits
nVidia Corporation GF104 [GeForce GTX 460]
Prop. drivers.

Thanks, apparently this issue is not a spring bug, but a problem with some graphics drivers only.

I don't see them.
They compare if I create another type of unit

Example: I make 2 Bulldog have a fight. When one of them dies, I don't seee the wreckage. If I create (example) a constructor, the wreckage appears.

I have a Intel Q9300 with a GT 8800 nVidia (driver 260.99).

Edit: SO = Windows XP

Now I try with my notebook too

I cannot see the wreckage.



Maybe it's the same bug that breaks the advmapshading in spring 84.0 and higher. I think it's a spring bug, I don't have any issues with any other applications.

Same problem on my Sony Vaio with Intel i7 and nVidia 425M (driver 259).
SO Windows 7

This means nothing, most other apps/games use DirectX. You would have to find a game using multithreaded OpenGL to compare with.

The different behavior we see for different systems points more towards a driver bug I would say. If this was a threading glitch in Spring code, I would expect the outcome to be random., but it appears to be consistent. You either see the wreckage or not.


Interesting, can anyone else reproduce this?

Ok, fair enough. But then it's probably still not a driver issue, we all use the same nvidia driver. (btw, tested also with 192.<something> with same results), so spring just uses some mode that's not supported by some GPU:s.