Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: S-99 on October 31, 2007, 05:18:09 am
-
The new version of wine (wine 0.9.46) is really nice. I can run launcher 5.5a and fso 3.6.9 in wine smoothly and easily this time. The last version of wine would only let me run the 3.6.9 executables in wine only after i configured fs2 with the launcher from windows. Anyway, fs2 can finally be run in linux the windows way, with a launcher, and with everything staying inside of the fs2 directory. The fs2 linux experience though while i could accomplish it i didn't really like, and the 3.6.9 binary for linux wasn't stable like the windows version.
When i get around to it i guess i'll finally be able to try out what's in the recent builds forum. I've heard other miracle news of the new version of wine also making fred2 open work as well.
-
with everything staying inside of the fs2 directory
Why couldn't you do this in Linux?
-
With the linux binaries the resolution control and where your pilot files get stored is in your home directory as opposed to the fs2 directory itself when you run it windows. I believe it was something like ~/.fs2_open/data/players/single/ for your pilot files, otherwise the linux fs2 binary wont see your pilot files in the fs2 directory (ie where the game is installed). Not to mention you had to make your own executable text file with all of the tags for utilizing the mvps, this wasn't too difficult as long as you get a list of the tags, but some tags the scp made like smartshields wouldn't work in the linux version.
-
why run it it wine when you can just do a linux compile?
-
I had success with wine, it was 8 years ago, and her name was Emma.....
-
I had success with wine, it was 8 years ago, and her name was Emma.....
I was just thinking the same thing. :lol:
-
why run it it wine when you can just do a linux compile?
Why do a linux compile when the linux binary is out there and runs....unstabley. Running fs2 the windows way is a lot easier.
-
Why do a linux compile when the linux binary is out there and runs....unstabley. Running fs2 the windows way is a lot easier.
It sounds like you just haven't got to grips with the ins and outs of running it on Linux. Having everything in one dir is easy, for instance having a config dir in ~/fs2 dir that's symlinked to ~/.fs2_open. Keep your (default) command line options in <gamedir>/data/cmdline_fso.cfg, and if you're wondering what they are, look here (http://www.hard-light.net/wiki/index.php/Command-Line_Reference).
Running it on top of wine may work and all, but I find it hard to believe it's more stable then running it natively.
-
Not to mention the performance loss :eek:
-
No believe me i got the ins and outs of running it on linux. I got the linux version to see my pilot files and work with the mvps. As far as what most people would say would. And well, the linux 3.6.9 is a lot less stable than windows 3.6.9.
Not to mention the performance loss :eek:
Performance loss with wine? What are you talking about? Wine runs windows programs with no performance loss in linux. You're windows programs run at the same speed they do in wine as they do in windows.
So no, no performance loss at all. I have run the windows executables in wine before, and it ran just as normal as it did on my windows installation.
Besides as opposed to anyone else here, i get to use the fso launcher in linux now too :nod:
-
And well, the linux 3.6.9 is a lot less stable than windows 3.6.9.
Me thinks something is wrong with your Linux setup.
-
You're windows programs run at the same speed they do in wine as they do in windows.
AFAIK there are wrappers between DX <--> Linux stuff, bound to cause a performance hit of some sorts.
-
Well as far as that goes, who said he's using DX?
-
Ok, ok, true, OGL stuff runs quite good. I'll take back the ":eek:" in my first post :P
Its just thatYou're windows programs run at the same speed they do in wine as they do in windows
..is maybe a bit over optimistic :)
-
Probably not universally, but I have seen an app run better in Wine than natively on windows on a few occasions. Specifically, Half-Life 1. Ran amazingly well on Wine, way back when it was still fairly new.
-
On my setup in multiple distros of debian wine runs my win programs with no performance loss that i could detect, they really run the same as they did in xp home when i had it.
It's not at all a performance loss using wine. Now there is say when you're processor doesn't have built in virtualization and i was running my xp home install through qemu that that would definitely have a performance hit.
Besides that, it's just a good thing to know that if people don't like using the linux release of fs2, or have had trouble with it, that there is a pretty nice alternative.
-
I think that it's generally accepted that most Windows apps run through Wine will perform better than they do natively on Windows (subject to Wine version though, sometimes regressions will hurt). But that's not really the point anyway. The point is that a version run through Wine will not perform as well as a native Linux version.
I do see some advantages of using Wine for FSO, but that's only if you don't bother to get a good Linux setup in the first place. A good Linux setup of FSO is far more flexible than you could possibly get running through Wine. It can also be a far cleaner setup than you could ever get with the Windows version.
But regarding the stability issues with the Linux version, this is the first I've heard of any problems, and you have yet to be anything but vague about them. If there is a problem that you want fixed then we need to know what the problem actually is. It could be code related, build related, or simply an issue on your end. I'm sure that at least one of us could help you through it though, if we only knew what help you needed.
-
I'm not really *****ing about the linux version. Just saying that i really didn't care too much for it. I'm sure the moment it gets more mature and gets a linux launcher or somebody make a universal launcher for all os's, then it'll be fine, and i'll switch to it. For now i find that the windows way of doing the game is the way i prefer.
The specific problems i had with the linux build was that i couldn't use the smart shields tag, switching to a different mod or campaign didn't really want to work (i bet somebodies gonna tell me i did that wrong :lol:), after that on some missions especially the nebula missions...the last nebula mission where it froze the whole system was where you find the ntf ship in the nebula, and i believe also on the mission where you kill the ravana in the nebula. It liked to freeze the system a lot on the nebula missions (it'd freeze the system to the point that i'd have to pull a hard restart). I was using feisty fawn ubuntu at the time, and my linux setup was fine. The problem lay in the linux executable. I'm sure the cvs versions for linux work a lot better than the old 3.6.9 for linux (i would have tried a different cvs version, but over the summer there wasn't really much for cvs unless it was windows related).
Anyway...headlines! The windows version of fs2 with mediavps and launcher works fine in wine (to anyone here who actually cares about it which seems like no one). It's interesting, you might even want to try it. Idk if it'd be useful for developers, and idk if it'd be useful for those who fred and test missions. It's nice to know when a linux program gets better especially for those who might have been looking forward to this like say me :D
-
I know that it works fine under Wine, hell, I tweaked the code specifically to make that happen. But I also know full well that it does not work as well as the native Linux version, which I use daily, and I'm sure put through far heavier use than anyone else. The Linux version not only works fine, but I'm confident enough in it to say that of the three supported platforms, the Linux version is the fastest and most stable of them.
I often run the game through Wine to test out Windows builds that I make, not to mention changes to the Windows specific bits of code. But I'm not about to replace using the game with the native binary for the Wine emulation. It simply doesn't work as well, regardless of your experiences with the Linux version so far.
And the Windows version is going to get more and more like the Linux version as time goes on, so be prepared for that. Whatever usage issues you seem to have with the Linux version are just going to come up again with future Windows versions.
i couldn't use the smart shields tag
Care to elaborate on that a little bit more? Were you getting some specific error or something? Or did it just not appear to work? There is nothing OS specific about any of the smart shields code, and I know for a fact that it does work under Linux.
switching to a different mod or campaign didn't really want to work (i bet somebodies gonna tell me i did that wrong )
Yeah, I'm sure that you were just doing something wrong. Although you don't get the simplicity of the Launcher for switching mods under Linux, you can still set it up in a far more powerful way: with separate run directories for each mod, and/or bash scripts for launching each mod, with different cmdline_fso.cfg files ready with default and mod specific options so that you don't have to keep changing your cmdline settings, etc. None of that is easily doable, or even possible in most of the cases, with the Windows builds.
on some missions especially the nebula missions...the last nebula mission where it froze the whole system was where you find the ntf ship in the nebula, and i believe also on the mission where you kill the ravana in the nebula. It liked to freeze the system a lot on the nebula missions (it'd freeze the system to the point that i'd have to pull a hard restart)
Sound familiar, so it's possible that someone else has reported that problem before. It could be either a hardware setup issue (yes, it's possible for Wine to end up not triggering certain problems with your system), or a crash that didn't leave your system in a clean state so that it would drop back to the desktop and give you control again. It's somewhat impossible to say what is going on there without more info though, either a debug log from a crash session, replicating the problem with the -window and -nograb cmdline options, a core dump, or a run through gdb to see if it's a program error.
-
It wasn't really my setup, in the executable text file which had all of the mediavp tags to use the mediavps. Including the tag that tells it to load the mediavps folder. Well for loading another campaign you'd just switch that out for say fsport. I tried that, and it wouldn't want to load. Same thing with the smart shields tag.
Anyway, all of this stuff was like during may or june. It was a while ago. And that's good that the windows builds are becoming more like the linux builds (that way for osx, linux, and windows they'll all have that familiarity). I could reproduce the errors from then since my fs2 directory hasn't been touched since then. But, i don't really want to since i've been doing some distro hopping eager to see what other distros of linux are like and why they're cool.
-
Same thing with the smart shields tag.
You know that smart shields isn't a cmdline option, right? It's set in ai_profiles.tbl instead. Been that way since before 3.6.9.