Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: TheBlackParrot on August 18, 2013, 06:14:30 pm
-
This is happening in both 3.7.0 RC2 and 3.6.18, and I can't figure out why. :confused: I've re-installed it multiple times to no avail.
http://i.imgur.com/a9QqitU.png
I'm on Arch Linux with the 3.10.6-2 kernel from the core repo, and I originally installed FS2O through fs2_open, fs2_open-data, and wxlauncher from the Arch User Repository. Straight up executing ./fs2_open_3.7.0_RC2_DEBUG from a terminal has no difference.
I'm using the GOG version of FS2 as well.
Video drivers are xf86-video-intel 2.21.14-2 on an Intel GMA 965.
http://pastebin.com/UxwsFC5s is my fs2_open.log
The only textures/images/whatever that seem to be doing this are the warp textures, ship damage, and explosions.
-
With an Intel video card, you may need to add "-no_glsl" to your command line options.
-
With an Intel video card, you may need to add "-no_glsl" to your command line options.
Still ocurring with -no_glsl
edit: actually they're not appearing at all now with that
-
Sorry, that's me out of ideas, you'll need someone who knows OpenGL better than I do.
-
OpenGL Version : 2.1 Mesa 9.1.6
Those look like very old graphics drivers - can you get newer ones for your card? If not, you could try running the exec with -nohtl, but be prepared for a performance hit.
-
OpenGL Version : 2.1 Mesa 9.1.6
Those look like very old graphics drivers - can you get newer ones for your card? If not, you could try running the exec with -nohtl, but be prepared for a performance hit.
They're only 9 days old: https://www.archlinux.org/packages/extra/i686/xf86-video-intel/
https://www.archlinux.org/packages/extra/i686/intel-dri/ is 18 days old
https://www.archlinux.org/packages/extra/i686/mesa/ same for mesa.
I'm not noticing much of a performance hit, but -nohtl is only removing more things. Those textures still appear missing too.
Could it be corrupted files?
-
Your log tells us your files are not corrupted. If anything, you could remove tangoA_fs2.vp and tangoB_fs2.vp as they are useless, but they're not the cause of your trouble.
The cause of your trouble is trying to run an OGL-based game on an old-gen intel integrated card with mesa linux drivers.
You'd have more luck trying to stop a submarine going at full speed with a spoon. While underwater. I know, I've been there. With that exact same card IIRC.
Unless you can find better (proprietary ?) drivers, I'm afraid you'll either have to either run this on windows (which definitely has more reliable derptelgrated drivers), or get a better comp altogether.
-
Your file counts and checksums on the retail files look to be correct (Though, you don't need to have TangoA and TangoB present, they can be safely removed).
I'm guessing a P4-Prescott era processor. And the 965GM Series Intelgrated is quite frankly not the best graphics hardware, especially when it comes to OpenGL which yours is barely managing to support 2.1, which should be perfectly fine in terms of "necessary" technical requirements.
Especially considering that you are still utilizing Retail data for the models and textures seems to indicate to me that the OpenGL drivers or hardware capability just really isn't up to snuff in this regard.
-
Your file counts and checksums on the retail files look to be correct (Though, you don't need to have TangoA and TangoB present, they can be safely removed).
I'm guessing a P4-Prescott era processor. And the 965GM Series Intelgrated is quite frankly not the best graphics hardware, especially when it comes to OpenGL which yours is barely managing to support 2.1, which should be perfectly fine in terms of "necessary" technical requirements.
Especially considering that you are still utilizing Retail data for the models and textures seems to indicate to me that the OpenGL drivers or hardware capability just really isn't up to snuff in this regard.
It's a Core 2 Duo T7500, definitely not a P4 haha.
Should I just use an older version or am I just completely out of luck?
I could try running the Windows version through Wine too although I doubt it would run as well as the native Linux version.
-
You could try an earlier version of FSO, it might work OK. However, running the Windows FSO binary under Wine probably won't help (although it won't hurt to try, and performance should be near native, I ran all of WCS:DD under Wine with no notable difference performance difference between it and normal FSO, although I was using a nVidia 450GTS & binary blob drivers). The problem is likely the Mesa Intel drivers that you're using.
-
Ya, running on wine won't fix the underlying "your drivers are ****" issue.