Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Orpheus on November 13, 2010, 03:45:39 pm
-
I have a working install of FSO, that works without the mods. However, when I activate mods, I get 497 errors. One of the most obvious results is that I don't see any models when I go to the technical database in the Menu screen. Just a few dots and that's it.
Screenies:
http://www.siebring.org/bestanden/Freespace%20folder.png <- My freespace folder
http://www.siebring.org/bestanden/screenprint%20game.png <- screendump from the ingame error
http://www.siebring.org/bestanden/mediavps_3612.png <- mediavps_3612 folder
-
I've been working with this guy and he seems to be doing a lot of things right. I wonder if it's a problem with the Linux launcher script?
He also built his own executable, I believe.
-
If retail works but mediavps are throwing all those warnings it sounds like file corruption somewhere in the mediavps. A fs2_open.log would help.
-
I've been working with this guy and he seems to be doing a lot of things right. I wonder if it's a problem with the Linux launcher script?
He also built his own executable, I believe.
how can the script be complex? you just point it to the executable and add the commandline options.
nvm, re-read your post, you said launcher script, not startup script :p sovvie
-
I just downloaded a debug executable. Running it give me the same 497 errors. How can I make a log file with the errors in it?
-
Please read the thread marked "READ BEFORE POSTING" stickied here.
-
It's automatically been generated for you. Search for fs2_open.log, post it here in
code tags
-
more info, finally I did run the debug executable. Too many errors to fit in this message, so the log file can be found here (http://www.siebring.org/bestanden/fs2_open.log)
-
Unable to find extension "GL_EXT_texture_compression_s3tc".
Please install driconf and switch on texture compression support.
-
Orpheus, are you perchance running the windows executables through wine on linux?
Also, as a side note, why run through the Mesa opengl interface? My advice is to use the ATI drivers for your GPU.
-
Except, fglrx doesn't work for a GPU that old, and the radeon drivers are ****e.
-
Also I think The_E's last suggestion fixed everything and he's now happily playing.
-
Oy. We had 0rph3u5 and now we have Orpheus. How are we doing to tell them apart? :nervous:
-
TBP badge since there won't be any more of those.