Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: Fieari on February 21, 2006, 04:46:29 pm
-
I mentioned this briefly in the torrent thread, but thought maybe its own dedicated thread would be a better idea.
I'm trying to get FS2_open to work on my new linux box. I downloaded the torrent correctly, with all the mediavps, cutscenes as AVIs, and derelict and FS1 included. I successfully compiled the latest CVS, downloaded the latest mediavps (beta), and yet I still have this problem. The program starts up correctly, but when I try to start a campaign, I get the following error:
ERROR: "Could not load WarpMap01 anim file" at fireball/fireballs.cpp:690
The mediavps are in the mediavps directory, but it didn't help to copy them to the main directory as the readme suggested. As it's the torrent install, the main directory contains the following files:flags.lch
Fred2.exe
Fred 2_open HTL.lnk
fred2_open_r-20060202.exe
freespace2.exe
FS2.exe
fs2_open
fs2_open_r
fs2_open_r-20060125.exe
fs2_open_r-3.6.7
FS2uninst.dll
launcher6.ini
Launcher.exe
patchw32.dll
root_fs2.vp
server.txt
smarty_fs2.vp
sparky_fs2.vp
sparky_hi_fs2.vp
stu_fs2.vp
tango1_fs2.vp
tango2_fs2.vp
tango3_fs2.vp
Uninst.isu
warble_fs2.vp
It looks to me like I have all the required files. I certainly have the default files, so even if the mediavps weren't being found, it should at least give me the retail graphics, right? So why isn't it working?
fs2_open is just a textfile containing all the commandline options I want: ./fs2_open_r -spec -glow -jpgtga -nomotiondebris -2d_poof -cache_bitmaps -targetinfo -orbradar -ballistic_gauge -rearm_timer -3dwarp -warp_flash -snd_preload
Additionally, when I go to the tech room, none of the ships display, but the glowpoints do. I suspect this may be a related symptom.
Can anyone help?
-
Problem solved. There was a default in a config file that was the source of my problems.
-
Which config file?
-
/data/cmdline.fso
I didn't analyze it in too much detail, but deleting that file solved the problem.
-
Dangit. Actually, it didn't solve the problem. It only brought me to retail defaults... I'm guessing one of those switches in that file told fs2_open to look in that directory for the media files, because now I noticed that the graphics weren't quite up to snuff, so I moved the mediavps to the main direction, and it started the problem again.
Well, at least I -can- play now, but I'd really like those mediavps to work.
-
By systematically adding one media vp at a time, I've determined that mv_textures causes me problems, and mv_effects/mv_adveffects might be causing more. What are the usual system requirements for those files?