[draeath]

I also use a built-in RealTeK.
I've tried warsow in feisty and it worked without any slowdowns. Have no idea why fs2 works like a charm in edgy but not in feisty...well but feisty is still beta 

If you've narrowed it down to something in Fiesty file a bug on Launchpad

[chaotic]

Good idea 

btw: when will 3.6.9 Final for Linux be released? 

[taylor]

btw: when will 3.6.9 Final for Linux be released? 

At some point tonight.  I need to do a final test of the installer and then upload, but that's it.

[chaotic]

Yeeehaaaa!  Thanks for your work!

[taylor]

Sorry, but I still haven't had the chance to test it all properly.  I've made quite a few changes to how it works and I don't have time to get a proper setup to test all of the changes as I should.  So I'm just going to upload what I've got, someone can test it, and then let me know.  If it works ok then I'll post the link in all of the proper places.

This is a departure from how I've done it in the past, the 32-bit and 64-bit binaries are in the same installer now.  Hurts for downloaders (23meg file), but it's going to be far easier on me from now on if this works well.  It will only install the files that match your architecture, so it should be just as easy as it used to be.  Two other changes of note:  1) it will install both release and debug builds, but the debug build is optional and can be installed or uninstalled separately, and 2) I have included the xmodmap tweak from the Wiki in the startup scripts, so if you have a ~/.fs2_open/xmodmap in order to use non-US keyboards then the script will make use of it.

Oh, and the only thing that really needs testing is the 32-bit stuff.  That's the only thing that I couldn't test to make sure that it installed all of the proper files.

So, someone grab it and let me know:  http://fs2source.warpcore.org/exes/linux/fs2_open-3.6.9.run


(side-note:  I also updated the OS X build to be current, and also updated the tarball to get rid of some code errors that I didn't notice before)

[ni1s]

-O3 -mtune i686 -msse -mfpmath=sse -pipe -fomit-frame-pointer

Why -mtune, and not -march?

Sorry, but I still haven't had the chance to test it all properly.  I've made quite a few changes to how it works and I don't have time to get a proper setup to test all of the changes as I should.  So I'm just going to upload what I've got, someone can test it, and then let me know.  If it works ok then I'll post the link in all of the proper places.

This is a departure from how I've done it in the past, the 32-bit and 64-bit binaries are in the same installer now.  Hurts for downloaders (23meg file), but it's going to be far easier on me from now on if this works well.  It will only install the files that match your architecture, so it should be just as easy as it used to be.  Two other changes of note:  1) it will install both release and debug builds, but the debug build is optional and can be installed or uninstalled separately, and 2) I have included the xmodmap tweak from the Wiki in the startup scripts, so if you have a ~/.fs2_open/xmodmap in order to use non-US keyboards then the script will make use of it.

Oh, and the only thing that really needs testing is the 32-bit stuff.  That's the only thing that I couldn't test to make sure that it installed all of the proper files.

So, someone grab it and let me know:  http://fs2source.warpcore.org/exes/linux/fs2_open-3.6.9.run


(side-note:  I also updated the OS X build to be current, and also updated the tarball to get rid of some code errors that I didn't notice before)

A quick $ chmod +x fs2_open-3.6.9.run && ./fs2_open-3.6.9.run gave me this,

Code: [Select]

Verifying archive integrity... All good.
Uncompressing FreeSpace 2 Open...
/home/ni1s/.setup12001: error while loading shared libraries: libgtk-1.2.so.0: cannot open shared object file: No such file or directoryWhich is not surprising, considering I don't have GTK+1 installed. Don't most people have GTK+2 now a days?
I can of course --target foo and take what I need, but that kinda nullifies the point of the installer. So can we up the GTK+ dep. a bit?

[ni1s]

The builds appear to work fine, the only problem I have is with the BtRL mod, where the debug build will crash on mission load with:

Code: [Select]

ERROR: "Unrecognized operator.  In sexpression: ( when     ( and        ( key-pressed "Shift-Pad +" )        ( key-pressed "Shift-Pad Enter" )     )   
( send-message        "Green 2"        "High"        "Open Comms Menu"     )    ( change-iff " at mission/missionparse.cpp:5798I am using the x86 builds.

[chaotic]

The startscript doesn't work here...

Code: [Select]

Couldn't run FreeSpace 2 Open (fs2_open.bin). Is FSO_DATA_PATH set?
/usr/local/bin/fs2_open: 3: cannot open /home/chaotic/.fs2_open/xmodmap.save
FSO_MODMAP=/home/chaotic/.fs2_open/xmodmap: No such file
when I try it with ./fs2_open in my fs2 directory it works...

PS: does this final still need -jpgtga or is it just like in the cvs?

[ni1s]

The startscript doesn't work here...

Code: [Select]

Couldn't run FreeSpace 2 Open (fs2_open.bin). Is FSO_DATA_PATH set?
/usr/local/bin/fs2_open: 3: cannot open /home/chaotic/.fs2_open/xmodmap.save
FSO_MODMAP=/home/chaotic/.fs2_open/xmodmap: No such file
when I try it with ./fs2_open in my fs2 directory it works...

Does $ export FSO_DATA_PATH="/path/to/fs2" && ./fs2_open work?

[taylor]

Which is not surprising, considering I don't have GTK+1 installed. Don't most people have GTK+2 now a days?
I can of course --target foo and take what I need, but that kinda nullifies the point of the installer. So can we up the GTK+ dep. a bit?

That's just the dependency of the installer binary.  I really do need to rebuild them with GTK2 support, though I haven't ever tested that and I'm not sure how complete that support is at the moment.

PS: does this final still need -jpgtga or is it just like in the cvs?

Yeah, it still uses/needs -jpgtga.  You can just use -img2dds, which implies -jpgtga, since that option is supported by both older and current builds.

[draeath]

-O3 -mtune i686 -msse -mfpmath=sse -pipe -fomit-frame-pointer

Why -mtune, and not -march?

Instead of trying to explain it myself, I'll quote the GCC manuals:

-mtune=cpu-type
    Tune to cpu-type everything applicable about the generated code, except for the ABI and the set of available instructions.
-march=cpu-type
    Generate instructions for the machine type cpu-type. The choices for cpu-type are the same as for -mtune. Moreover, specifying -march=cpu-type implies -mtune=cpu-type.

Basically -mtune optimizes code for a specific chip, where -march builds for it. (mtune remains compatible, march does not)

[chaotic]

Does $ export FSO_DATA_PATH="/path/to/fs2" && ./fs2_open work?

It works only for one session...when I restart my Computer, problem is back

Yeah, it still uses/needs -jpgtga.  You can just use -img2dds, which implies -jpgtga, since that option is supported by both older and current builds.

OK, thanks 
Does fs2_open save all my settings? So one time, I've to give it all options I like to use and never again? For the cvs, I used a startscript like it is discriped in the wiki:

#!/bin/bash
cd /path/to/your/freespace/
./fs2_open_r spec -glow -mipmap -missile_lighting -dualscanlines -targetinfo -rearm_timer -ballistic_gauge -3dwarp -warp_flash -snd_preload -env -alpha_env -mod mediavps

I dont need such a script any more I think?

[taylor]

It doesn't save your options, but there is no real reason to put them in a script, just use the cmdline_fso.cfg files instead.  For instance, I have generic options in ~/.fs2_open/data/cmdline_fso.cfg, things that aren't mod specific.  For things that may be mod specific, or that use separate directories anyway, I set those options in the games data/cmdline_fso.cfg file.  For stuff that's really specific, and that I may not want on all of the time, I'll specify either in a startup script or just on the command line.

When the game loads it parses the game's data/cmdline_fso.cfg first, then ~/.fs2_open/data/cmdline_fso.cfg, then the command line itself.  If you have different settings for the same option (such as -ambient_factor) specified in multiple places, it will use the setting from the last one read.  That will help you out when you tend to use most of the same options all of the time (like -spec, -glow, -img2dds, -3dwarp, -2d_poof, etc.) since you only have to specify them the once and it will always be able to use them.

[chaotic]

Thanks for your help taylor!!! Really great community here 

Now only that "FSO_DATA_PATH-Bug" needs to be fixed...or is it only my problem?

Edit: hmm well, I put all the Options I want into ~/.fs2_open/data/cmdline_fso.cfg except for "-mod mediavps"

Now, when I wanna play Inferno: Alliance, I type "fs2_open -mod INFA"  -> Everything works fine

Now I try DerelictSCP with "fs2_open -mod DerelictSCP" -> mediavps aren't loaded...but in Derelict's mod.ini I got "secondrylist = mediavps;" -> It works when I type "fs2_open -mod mediavps,DerelictSCP" but where is the need for a mod.ini then?

When I put "-mod mediavps" into cmdline_fso.cfg I have no planets in the space-background

[taylor]

Yeah, I'm going to look into that FSO_DATA_PATH issue when I get time later tonight.

mod.ini files aren't used by the game though, only by the Windows launcher.  That's one of the reasons why I hate mod.ini files, they are generally useless because they have no ties to the game itself.  Hence why I'm working on a totally new system of ini files which is tied directly to the game and a newer/better launcher. 

For Derelict though, use -mod DerelictSCP,mediavps, since you want Derelict primary in the mod list.  Although the -mod option is stackable (individual -mod commands are added together on load) there is a load order issue when you put them in the cmdline_fso.cfg files.  I just relalized that today and have coded up a fix for it.  It's not a big deal, it just gets the priority wrong.

[chaotic]

OK, thanks again 

[taylor]

I've got a 64-bit version of the GTK2 installer up and running (for the first time without a constant segfault).  I need to build the 32-bit version and then I'll put up a new installer for you guys to test.  I also fixed the menu location issue, so it will go into the place that current/newer versions of GNOME use (and what freedesktop.org specifies).

I'm pretty sure that I got the FSO_DATA_PATH thing dealt with as well.  Like friggin newbie I left off a couple of quote marks in the script.  I feel like a moron.


EDIT:  Installer at previous link has been updated.  Like before, the 32-bit version is completely untested.  Let me know if there are still any issues remaining.

[chaotic]

I tried the 32bit-Version but still:

Code: [Select]

Couldn't run FreeSpace 2 Open (fs2_open.bin). Is FSO_DATA_PATH set?
/usr/local/bin/fs2_open: 1: cannot open /home/chaotic/.fs2_open/xmodmap.save: No such file

[taylor]

Damn.  Uh, does FSO_DATA_PATH/fs2_open.bin exist, and is it set as executable?  What is the /path/to/fs2 (wondering if it's failing to setup correctly for some reason)?

[chaotic]

The Path is "/media/big/fs2/", the fs2_open.bin exist and is executable