Not that what FSO does has any bearing on what FSO does, but nevertheless we will (at some point) be doing a "portable" mode for wxLauncher because it has been requested by several people.
derp. i meant to say that i dislike the fact that fso stores stuff like pilots, logs and such into .fs2_open instead of in the directory where the executable and the rest of the important stuff is.
i also find the separation of logs and actually useful **** for debugging from the main executable's location.This does not parse. Please elaborate.
Yes, that does make sense if the game is installed into /usr/games or whatever, which isnt user-writeable. I havent seen anyone say that they installed the game like that on linux so far, and if memory serves, the proper "tutorial" on the wiki is basically "save into whichever folder you want(which, for most people is /home/<username>/whatever ), plonk the exec there, have fun with launching the game"
I should note however, where you install FSO has no bearing on where wxLauncher should be installed. We don't suggest installing wxLauncher in the same directory as FSO. Instead wxLauncher should be installed as a separate application.
of course, i wasnt implying i installed it in the same folder as FSO, just a wish to keep it all contained within a single folder. no worries there as i know nothing will change there on the FSO side.
also, i do not know if its been requested already, but a box for manual resolution entry in the launcher would be swell No it has not been requested. But I don't see us adding that feature either because the resolutions that we list are requested from the video hardware/software. If a resolution is not in the list then it is probably not a resolution that you want to use anyway.
At least one boneheaded version of the nVidia Linux drivers has a very minimal set of supported resolutions (i.e. 7) which doesn't include my standard res for a 16:10 window (1440x900) - in fact the only widescreen res was fullscreen
oh its even better on my end. i'm running a dual-screen setup. twinview of course, you know how many resolutions i have? One.
, 3200x1080, because 1920x1080 + 1280x1024
I had to define an additional metamode just to keep applications from fullscreening to both monitors, and then i always lose the secondary monitor for the time the fullscreen app is running, due to the way the metamode is set up. I havent found a solution yet, but i also havent searched that much for it either.
those suggesting nouveau/gallium will be shot dead.
Having said that, you can probably edit profile or set your resolution manually on the custom flags. The flag is -res <width>x<height> IIRC and it will override the resolution set by wxLauncher via the other mechanism.
If you manually edit the profile file will the next change you make to the profile overwrite your change?
Thanks for the tip about the -res flag, I'll have to try it out.
thank you for that. i always forget about that flag -.- (mighty useful when trying to run windowed)