Tested on wine 1.1.8, opensuse 11.0, 7600GT, confirmed Allegiance runs. ASGS not tested.
Wine on default settings except for running in a virtual (windowed) desktop mode. Too many bad experiences with games grabbing full screen and not letting go.
I had to use a fresh .wine otherwise I got a C runtime error when I tried to start Alleg. Musta been something else I did.
Install worked and all that. Setting the beta Alleg to full screen caused it to crash. Windowed worked. My joystick's throttle crapped out on me during a training mission, though I can never tell if it's just the scripting on those things. Frame rate was nice and smooth, didn't check the actual value.
Menus (like the escape menu and the F4 inventory) have a 1-pixel wide gap between each entry where I can see the background. No gameplay impact.
Trying to connect to one of the existing beta games gave me a file sync error. Creating a new game gave me the same. It suggested that I delete filelist.txt, but my Alleg directory doesn't have one.
Running Alleg and Amarok at the same time worked just fine for me. I've heard that PulseAudio can be disagreeable, so if Finn's running Ubuntu, that's probably it. Sound settings in Alleg made no real difference. Worked fine for me.
Exiting Allegiance gave me a lovely stack trace in the terminal and a hung program. Clicking the X on the wine window makes it actually close.
State of Allegiance in Linux
-
- Posts: 360
- Joined: Sat Feb 17, 2007 11:18 am
- Location: England
mdvalley, your experience correlates with mine (except joystick (i use mouse) and sound, obviously)
im guessing you tried to create a cc_02 game?
i made that mistake, cc_02b worked fine.
and yup, using pulse, that may be it.
ive submitted to AppDB (its awaiting approval), i stuck it in R4, while technically wrong, it makes more sense since R4 is whats being installed.
made a post there too, giving the same instructions as here (a bit more from the wine POV and in a way that a non-allegger could use it).
im guessing you tried to create a cc_02 game?
i made that mistake, cc_02b worked fine.
and yup, using pulse, that may be it.
ive submitted to AppDB (its awaiting approval), i stuck it in R4, while technically wrong, it makes more sense since R4 is whats being installed.
made a post there too, giving the same instructions as here (a bit more from the wine POV and in a way that a non-allegger could use it).
Last edited by finnbryant on Mon Nov 10, 2008 6:30 pm, edited 1 time in total.
The beta server is running R5, you may need to get the additional artwork files as they were being pushed by ASGS in beta mode. They are NOT on autoupdate.
http://fazdev.alleg.net/FAZ/R5beta_artworkdevfolder.zip
http://fazdev.alleg.net/FAZ/R5beta_artworkdevfolder.zip

DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]