Page 6 of 11
Posted: Thu May 01, 2008 8:36 am
by badpazzword
All we have done is launching executables. Wine fails at loading ASGS and no attempt has been done to "fix" this. We've been focusing on Allegiance.exe mainly.
As far as I can see no terms of the ToS have been broken, this thread is perfectly legit and so are our operations. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Posted: Fri May 09, 2008 6:04 pm
by spxza
Hi All,
I've had a bit of experience hammering wine into submission. There is some important diagnostic info that helps with figuring out what is happening:
1) Your distro flavour, version and architecture.
2) Wine version (If you installed from a precompiled package, check your package manager - Synaptic or other flavours)
3) Turn on debugging, and try include the output
4) What builtin libraries you have overriden with native ones.
All of these points are pretty important. An annoyance with wine is that it's version is absolutely critical. There are apps that work perfectly, but break after a minor release. You could try playing with different versions. To do this I HIGHLY advise building from src (and not forgetting to make uninstall).
Overriding the builtin libraries can make or break an app. Play around with combinations of these. Hopefully, with enough people trying to make it work, someone will have success. If you are the lucky one, then please try remember what you did. I will try getting ASGS to run. Gulp.
Oh, please submit your test results to wine's appdb:
http://appdb.winehq.org/objectManager.php?...n&iId=10631
The more test results we have, the more attention we'd get from the wine developers, and get some advertising for Alleg. That is, unless all the results are Garbage.
Posted: Fri May 09, 2008 6:07 pm
by badpazzword
Browsing part of the main menu without being able to load any content except for the credits screen does qualify for Garbage, I'm afraid. /mellow.gif" style="vertical-align:middle" emoid=":mellow:" border="0" alt="mellow.gif" />
Posted: Sat May 10, 2008 7:19 pm
by Tigereye
Good luck getting further with this, guys.
If there is an Allegiance client that runs successfully on other platforms, and it's been shown to work...
Well, as Dogbones said - let's not get the cart ahead of the horse.
Suffice it to say, I dream of the day that I and anyone else in the community can fire up OS X, Linux, or their favorite operating system and join an Allegiance game hosted on our community servers without rebooting into Windows. But before we can even consider allowing such a client to interface with our community's servers, such a client needs to exist first!
--TE
Posted: Sat May 10, 2008 10:17 pm
by badpazzword
Sigh.
http://www.winehq.org/site/winapi_stats
DX9 targeted support's pretty near to completion /doh.gif" style="vertical-align:middle" emoid=":doh:" border="0" alt="doh.gif" />
I might try with Wine 1.0 RC1 later.
Posted: Sat May 10, 2008 11:14 pm
by badpazzword
badp@bPortatile:~/.wine/drive_c/Program Files/Microsoft Games/Allegiance$ wine Allegiance.dx9.exe
fixme:win:EnumDisplayDevicesW ((null),0,0x32f140,0x00000000), stub!
// settings I launched with
err:d3d:WineD3D_ChoosePixelFormat Can't find a suitable iPixelFormat
// whoa.
// hovered on the Training button
// the screenshot dialog seems to affect how the Alleg window is drawn
// the upside down F1 dialog's still there in the training screen
// same upside down artefacting for the loading screen
wine: Unhandled page fault on read access to 0x00000000 at address 0x5d45ad (thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 6108") (4)
Read the Wine Developers Guide on how to set up winedbg or another debugger
--
Whoa. That was pretty bad. The DX7 version just hung up the system. The DX9 version is just bad, and the NULL pointer access is still there.
PS: The screenies above are not Spidey approved. /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" /> Sorry...
Posted: Tue May 13, 2008 5:23 pm
by finnbryant
ouch, that looks pretty bad.
i expect it would look better in cedega since its meant to have good directx support
but i guess the crash would still be there, so i wouldn't bother paying for it.
Posted: Tue May 13, 2008 9:40 pm
by FreeBeer
I wonder if it makes any difference if you try the dx9 alpha client.
Posted: Tue May 13, 2008 9:59 pm
by TheBored
FreeBeer wrote:QUOTE (FreeBeer @ May 13 2008, 02:40 PM) I wonder if it makes any difference if you try the dx9 alpha client.
Reread BP's post (and the screens). He was using the dx9 version /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
TB
Posted: Tue May 13, 2008 10:51 pm
by finnbryant
yep, the normal client crashes in the same place, but doesn't suffer the other bugs mentioned (like the reversed text, wierd button positions etc.)