Spring RTS Engine

"Error at position 43 when loading fragment program file unit.fp"

I have tried Spring on 3 different computers, each well capable of running it on full settings, which runs spring fine on max settings with previous versions (Except one), and I have recieved that message every time.

After playing around a bit, I discovered that what was causing the issue was when I had shadows activated in the settings. I can run everything at maximum, and get into Spring and play fine, however, as soon as I activate shadows, Spring will crash while loading, and give me the above error message.

Can anyone help?

Apologies if this has already been addressed.

I have a similar problem in that I cannot access shadows and reflections in the water. When I put these settings on, my game will run; however, when in game, it tells me that I do not have a suitable fragment program and I am missing the OpenGL necessary to display shadowmaps. Does anyone have a solution to this? Where can I download a so-called "fragment program" compatible with Spring?

Fragment programs is the same things as pixel shaders in directx. They are basically small programs that are run at on the gpu for every fragment (about the same thing as a pixel). If you get that error it probably mean your gfx card or the drivers for it doesnt support the fragment_program_shadow extension. I will fix so that it disable shadows automatically instead of giving an error when that happens.

I am running an AMD Athlon 64 3200;
I have a radeon 9800.

I have been able to run shadows with no problems up until the latest release.

Well a radeon 9800 should have no problems with the new shadows, my old 9500 can do it no problems(except speed). So try updating your gfx drivers.

use forceware! not sure whether its for radeon's but it helped my poor old GeForce FX5200 a LOT! :D

Zsinj, the Catalyst 5.8 drivers were released no too long ago. go to http://www.ati.com to find them.

Min3mat forceware is nVidia cards only.

Scratch that, Radeon 9600.

Downloading drivers as we speak. I think this may be the issue, as the computer is very new, and drivers have yet to be updated.

Still, it is strange that a single version leap should break it...

Just as an update, new drivers fixed the issue.

Thanks to everyone who offered their help. :)