Spring RTS Engine

Hey there,

I've a major problem! Since I've changed my Graphiccard from a Nvidia Geforce GTX 285 to an AMD HD 5850, Spring always crashin' after creating sky (at the moment he normaly should display the battlefield). First, I was successful fixing that by simply re-install Spring, but since I've installed the third monitor (using Eyefinity, 6036x1080), he's crashing at this point again.
Reinstalling the game doesn't fixed it this time. It's unnecessary to set the resolution to 1920x1080 (vga driver's detecting resolutions which fits better on one monitor and just duplicating it instead of stretching it), It's still crashing. I'm using Win7 x64.

I don't have much experience with amd/ati and spring together. What can I do?

Kind regards,
Serry

1. bad gfx decision

2. -> start spring.exe -> Edit Settings -> Set AtiHacks=1

Atihacks is already activated.

then the following is valid

This stack trace indicates a problem with your graphic card driver. Please try upgrading or downgrading it. Specifically recommended is the latest driver, and one that is as old as your graphic card. Make sure to use a driver removal utility, before installing other drivers

or just play with the spring settings until you found combinations that work

First mistake, buying ati. AMD = good. ATI = fail.

If you need proof: http://store.steampowered.com/hwsurvey/

Forboding Angel wrote:First mistake, buying ati. AMD = good. ATI = fail.

If you need proof: http://store.steampowered.com/hwsurvey/

You do realize that the brand "Ati" no longer exist right?

Ok, for the pedantic Italian...

AMD CPU's = good

AMD GPU's = fail

Forboding Angel wrote:Ok, for the pedantic Italian...

AMD CPU's = good

AMD GPU's drivers = fail

fix'd

Yeah, good point, I'll give ya that one.

Forboding Angel wrote:Yeah, good point, I'll give ya that one.

Good news recently, the word is getting out about ati/amd drivers sucking because of Brink not working well with them. I don't know details but bad press is bad press.

They have notoriously bad drivers for OpenGL - I know that much form various Devs notes.

Hey guys, I need your help again, I'm totaly distressed. I thought I fixed the problems: Bump-Mapped water causing the game to crash at start, also some LUAs affect some quite interesting things, so I deactivated them.

But last Match some minutes ago, there where new errors. At the beginning, I had this shiny bubbles on my minimap again (they where gone for a while since I used the Red Lua UI (BA) instead of the IceUI. I wasn't able to fix that (unless I deactivated all lua's which could possibly affect the minimap, while stopping the game and annoy all other players), so I need to play with it (I could deactivate the LUA Interface completely, but....no).
Then, In the middle of the game, it crashed. (not a "normal" crash, the game was frozen, and I had problems to reach the Task Manager to stop spring by manual). A nice windows from the CCC was shown where he reported some issues with the Displayport I've had never heard before (It's attached).

Someone have an idea? I just don't know how I could fix this, this graphic card wearing me down, crashing all the time in several games (mainly Spring and TM United Forever, but also Portal 2), cause graphic bugs. It would be a bad idea to downgrade the driver, I guess the eyefinity support isn't well supported on older driver versions. I already tried the most fancy resolutions, like set the vCore of this card higher than normal (Sometimes, this helps to let a card runs more stable). Haven't the money to change my graphic system.

Someone have a solution? I become desperate with this.
And sorry for my possibly bad english this time, I'm asleep at the switch.

nearly all known problems with ati + solutions are here:
http://springrts.com/wiki/FAQ:trouble#ATI.2FAMD

your error-message is because a error in the graphics-driver. maybe your gpu is getting to hot?

Edited

AHA!

Turn off "Use Pixelbuffer objects" in spring settings.

I figured that since it was a graphic driver error, maybe something had been enabled/disabled that was causing the problem. Turns out, I just had to disable using pixelbuffer objects, and that solved the problem! Yay. :D