Support offer

[Ivanux]

Hello,

Sorry, it seems I reply a bit too late, because Klauss solved your problem.

As far as radeon free driver is concerned, I'm afraid I think It is simply unable to handle Vegastrike at the moment.

But, I'm able to get through the menu to come to the game (which brilliantly runs with... less than 1 FPS on my dev laptop).

FYI:

• Linux Omicron 2.6.32-gentoo-r7 #3 SMP Sat Jun 5 23:09:28 CEST 2010 i686 Intel(R) Core(TM)2 CPU T5300 @ 1.73GHz GenuineIntel GNU/Linux
  
  x11-drivers/xf86-video-ati 6.13.0
  x11-base/xorg-server 1.7.6
  media-libs/mesa 7.7.1
  x11-libs/libdrm 2.4.18_pre20100211-r1
  x11-drivers/radeon-ucode (not installed: r550).

But with an r600, you should probably try to run the official ATI-driver which has a really stronger 3D accel ATM. Maybe it would also solve your issue?

Hope it helps


@Klauss & Chuck: Now that my exams are over, I can get down to business and have a look to the universe generation process.

[klauss]

For the radeons, try lowering or disabling shader settings. It should fix your problem (by sacrificing graphics quality).

We have to develop ATI-compatible versions of the shaders, but we're short on test systems (I have an ATI card, I just don't have it in a development-capable computer atm, nor the time to go switching GPUs on my main development rig).

If there's any shader developer out there, with an ATI rig somewhere running on linux, we would appreciate if he/she could do us the favour of adapting the shaders to be ATI-friendly. It's just editing the fp and vp files in data/programs. However, shaders are not final, so any such adaptation will need to be redone every time we upgrade the shaders (I know... a pain...)

[felixrabe]

Thanks for the answers, and don't worry about response times - AFAIK nobody does this for money and I just started working (for money) and threw a big party yesterday to celebrate this, so was busy anyway.
I think I'll retry in a few days, with less shaders and/or proprietary ATI drivers.
Greetings

[nikai]

Hi there!

I'm using Gentoo as well, with radeon r600 classic kms.
OpenGL renderer string: Mesa DRI R600 (RS780 9610) 20090101 TCL DRI2
Linux 2.6.35-rc6 x86_64 AMD Phenom(tm) 9350e

From X11 overlay:

x11-drivers/xf86-video-ati git
x11-base/xorg-server 1.7.6
media-libs/mesa git
x11-libs/libdrm git
x11-drivers/radeon-ucode

I can run VS without shaders at 800x600, but I'm experiencing GPU lockups in specific situations, like approaching Serenity, or crashing the ship.
https://bugs.freedesktop.org/show_bug.cgi?id=27868#c6

Here are screen shots:
http://vegastrike.sourceforge.net/forum ... at=1112329

[klauss]

If they nail the cause, perhaps we can patch VS not to trigger the bug.

[nikai]

how exactly did you get Vegastrike to compile and run in Gentoo?

I found an old SVN ebuild in the Gentoo Bugzilla, bug 65084, and fixed it to work for me.

Then I applied for a Gentoo user overlay, brushed the ebuild up some more, split it into data and vegastrike, and now I'm maintaining them in my overlay.

I hope they might be useful enough to get a Gentoo user started.

If they nail the cause, perhaps we can patch VS not to trigger the bug.

I never thought of that. Currently the open drivers are quite in flux. The r600 classic driver will soon get replaced with r600 Gallium, and mesa switch to a new GLSL compiler. Maybe this will fix the lockup

Kernel mode switching was the reason that I recently started to have a look at 3D applications. Before that, 3D was so slow and broken in general that I had lost interest many years ago.

[nikai]

Indeed, with the new GLSL2 compiler the GPU lockups have disappeared. Together with this compiler came a regression that caused another segfault, which was fixed yesterday.

So with current mesa-git, Vega Strike is playable at a frame rate of 30+ with the r600 classic driver

I disabled high quality fonts which drop the frame rate to about 3. Shaders appear to just look black, but don't crash the game any more.

[klauss]

Great!

BTW: I'm in the process of committing a new set of shaders, and a fix for that blackness

[nikai]

I'm in the process of committing a new set of shaders, and a fix for that blackness

Thanks! Atlantis is looking great.

Currently I'm playing at 1024x768, 32bit fullscreen, with high quality fonts enabled at 20-30 fps.
Simplest shaders work well at my place. Any better shader crashes like this:

Code: Select all

Compilation of technique fixed successful
0:122(13): preprocessor error: syntax error, unexpected IDENTIFIER

Fragment Program Error: Failed to compile highend
Compilation of technique default failed... trying ../4_ps2.0/default
Cause: Error compiling program vp:"highend" fp:"highend"
Compilation of technique ../4_ps2.0/default failed... trying fixed
Cause: Error compiling program vp:"default" fp:"default"
0:0(0): error: function `textureCubeLod' undeclared
0:9(60): error: type mismatch
0:9(60): error: `return' with wrong type , in function `ambientMapping' returning vec3

Fragment Program Error: Failed to compile ambientmapped_simple
Compilation of technique default_simple failed... trying fixed_simple
Cause: Error compiling program vp:"fixed8" fp:"ambientmapped_simple"
terminate called after throwing an instance of 'Audio::FileOpenException'
  what():  Cannot open "techniques/fixed_simple.technique"

[klauss]

Nice, thanks for the report, I'll try to address those issues.

[Ivanux]

Hi everydoby,

I've just a really simple question: which IDE do you use to edit VS sources?

I tried
- NetBeans for C++: it cannot support such a big project because it analyses the entire project each time a file is saved. Takes ages.
- Code::blocks: but it takes up to 900Mb of RAM and often causes my machine to swap. It is also extremely slow to analyse the project.

I currently use Eclipse with CDT C++ plugin, which runs fine but doesn't do "real-time" code analysis. So you've got to compile to see where errors are. This is a pain in the neck, knowing that VS takes up to 15min to compile on my machine...

So, I'd be interrested to know what you use

Thank you in advance

[klauss]

I use KDevelop, but currently it has the same limitations the Eclipse CDT has (because I have to disable code analysis to avoid some serious crashes).

Although, normally, KDevelop does perform code analysis with the gcc backend, so it's rather accurate and nice. It is slow, but does so on the background. I've been waiting for KDevelop guys to fix the crash, because code analysis is of huge help in VS, because of what you said, and because it assists with code navigation by leaps and bounds, since VS codebase is huge and not very well organized.

[strook]

So you mean kdevelop 3 or 4?
3 Runs on my machine without probs very Fine,
4 crashes recently After some minutes on various Systems.

[klauss]

I use KDevelop 4, but you have to disable background parsing since, as you found out, it crashes with VS.