I have two ideas with the purpose to lessen the frustration of new users and to lower the burden of spring devs to deal with the same issue over and over again. What do you think?test-app
Could the spring devs write a small *.exe that can be run independently from the engine and that does some opengl-shader-woodoo? It should crash in the same way as spring does with bad drivers/gfx cards.
This exe could then be distributed with the lobbies and would run at installation time - previous to users trying to play! The lobby could then present the user with a nice window explaining them the situation.
This would produce less frustration than having users register to a forum, search a log file on their hard disk, C&P it somewhere and then finally be told to buy a new gfx card.spring compatibility DB
Lobbies could collect success/fail data and store it in an online DB:
os | patch level | gfx-card | pci-id | driver | driver version | spring settings | success/fail | comment
After some time collecting data it should produce a "spring compatibility DB". This could be referenced at the download page of engine and lobbies.