[DivisionByZero]

So I just updated my system and it's been giving me headaches. Luckily, I can get things to compile now (thank you, everyone who helped), but there are graphics errors.

since this isn't a compile problem, so far as I can tell, it gets a new thread.

anyways, I first noticed it during the training missions looking at the nebula backgrounds.  The texture would appear to be connected to a triangle that was moving around with the camera all weird. I didn't think much of it as I could turn off planet/nebula backgrounds in the game.

But, when I try looking at some of the ships in-game, they have missing textures or have these weird poly's coming out at all sorts of angles.

I'd love to post a screenshot, but I don't know if printscreen is working because I don't know where the screenshots are supposed to be stored (I feel like an idiot at the moment, btw) and I must not be looking the right way through the forums.

Anyways, here's the relevant system specs:

Machine specs:
OpenSUSE 10.3 distribution
kernel 2.6.22.9-0.4
gcc 4.2.1
Intel 945GM integrated graphics card (laptop)
"intel" driver
It's a widescreen display (1200x800 capable)

FS2 stuff:
HEAD version (as of 11:15pm(CST) Oct. 13, 2007
1024x768
glitches no matter what cmd-line options I put in.

Any help is greatly appreciated. I can't (apparently) use 3.6.9 because the Mesa update screwed with some of the GL calls and such...

[DivisionByZero]

this may also be related:

I've determined that mediavps isn't loading correctly/playing well on my machine by comparing what my game looks like to the screenshots that have been posted around. when I add the cmd line parameter: -mod mediavps the game loads, but when I try to look at ships, all their textures are gone. The only things remaining are the lights blinking here and there and maybe a cockpit on one or two of the ships. If I try looking at the larger ships, I wound up getting a segmentation fault and having to restart x.

Given the above info, any thoughts on how to solve my problem(s)?  By the way, this was the case before I upgraded to Suse 10.3 as well... wondering if there's some weird tricks I need to do with my vid card to get this working...

[Jeff Vader]

I could be wrong, since Linuxes might have their own thingies that mess things up, but the part about missing textures on ships suggests that you're not running the game in OpenGL. If Printscreen works in Linux like it works in Wind'ohs, the screens are saved to \freespace\screenshots or something like that.

Edit: That integrated Intel graphics card doesn't sound good. It might be that it's drivers just don't support OpenGL properly, which in turn leads to broken graphics.

[Turey]

I could be wrong, since Linuxes might have their own thingies that mess things up, but the part about missing textures on ships suggests that you're not running the game in OpenGL. If Printscreen works in Linux like it works in Wind'ohs, the screens are saved to \freespace\screenshots or something like that.

Linux doesn't have D3D.

[Jeff Vader]

...oh yeah. Too obvious for me to figure out. But printscreen works similarly, right?

[castor]

I'd love to post a screenshot, but I don't know if printscreen is working because I don't know where the screenshots are supposed to be stored

Look at ~/.fs2_open/screenshots

[DivisionByZero]

castor, you're awesome.

here are the screenshots showing my problems.

When I use -mod mediavps in the command line, here's the result:
https://netfiles.uiuc.edu/mjaworsk/shared/Pictures/FS2/screen1.jpg

just the little lights that blink and tons of missing textures.

The other two are without even trying to call mediavps
If I have planet/nebula backgrounds enabled and look at them, they give this weird polygons everywhere
https://netfiles.uiuc.edu/mjaworsk/shared/Pictures/FS2/screen2.jpg

When I pull up some of the ships in game, they have all sorts of errors in them. It happens in-game as well, not just in the viewer. Here's the Fenris just for illustration
https://netfiles.uiuc.edu/mjaworsk/shared/Pictures/FS2/screen3.jpg

[DivisionByZero]

Just a quick update:
I have a build of both HEAD and 3.6.9 and both of them give the same behavior. Later today when I have some more free-time, I'm going to try and install Mesa 6.5.3 and see if the issue is with that item... unless someone thinks that's monumentally unwise.

EDIT:
Before I roll back to mesa 6.5.3 I thought I'd give the software rendering a shot to see if ti made a difference.
I appended -nohtl to the commandline and all the ships render normally. I still have a lot of errors/missing ships with the -mod mediavps command.

The weird quirk here is that no primary weapons fire shows up anywhere, though it appears that missiles do fire.

[DivisionByZero]

As I'm slowly de-n00bifying on matters linux and computers in general, I think I've identified a potential problem...

I think that the "Direct Rendering Interface" (dri) isn't finding my video card correctly.

The Mesa page says to make sure that dri is working correctly, so I followed the links to this page:
http://dri.freedesktop.org/wiki/DriTroubleshooting

so I run dmesg | grep agp and I get back that it finds my video card alright:
"agpgart: Detected an Intel 945GM Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xc0000000"

then I run dmesg | grep drm and I get:
"[drm] Initialized drm 1.1.0 20060810
[drm] Initialized i915 1.6.0 20060119 on minor 0"

AH HA!

drm thinks I have an i915 when I really have an Intel 945GM.

I'm figuring out how to install the latest drm build to see if that fixes the problem, if not, I'll submit a bug report.... though one of their pages says that my chipset is supported.

I'm kind of posting out loud in the hopes that this helps some other poor shmuck somewhere down the line...