TASClient + wine : SubClassUnicodeControl error

[nano]

Hi,

I'm playing spring on linux (using TASClient+wine to launch a linux binary), but since the last upgrade I get this error from wine when starting TASClient : Internal Error: SubClassUnicodeControl.Control is not Unicode.
Do someone have an idea of what I could do to get past this ?

Thanks

[Relative]

I can't help, someone else might be able to, but there is a native java lobby client for linux called AFlobby. Its still in beta, but fully functional as a lobby client, just lacking a couple of hosting features:

http://spring.clan-sy.com/phpbb/viewtopic.php?t=8691

[YokoZar]

It's a bug in Wine, and unfortunately is not fixed in the new version I'm about to release today: http://bugs.winehq.org/show_bug.cgi?id=8948

You'll need to use 0.9.40 for now until 0.9.43 comes out.

[nano]

Thanks for the advices, downgrading wine worked well but I had some java errors with AFlobby. Anyway I can play now :)

[AF]

nano, if you can be bothered asking for help to get a non native application to run using a wrapper for a large closed commercial API, that has numerous issues even on windows, why is there no thread for AFLobby, a lobby that runs natively under linux?

[Relative]

nano, if you can be bothered asking for help to get a non native application to run using a wrapper for a large closed commercial API, that has numerous issues even on windows, why is there no thread for AFLobby, a lobby that runs natively under linux?

I'll answer that for you:

1.) Something is wrong with his java/aflobby installation, which would be a hassle for him to fix, but lucky for him TASclient+wine "just works".

2.) He is familiar with TASclient+wine.

3.) Aflobby is still in beta, whereas TASclient isn't.

[tc-]

SpringLobby works if you just want to play, but the hosting feature is still in early development and we are currently working on it.

There are download and installation instructions on the site if you are interested.

[nano]

Hi,

You've got it right Relative. I don't play very often so I don't want to spend much time trying to make AFlobby work whereas wine + TASClient "just works".
But as soon as I hear AFlobby gets more stable I'll try it again.
I also hope spring gets a bit more stable because I get random crashes every few games :s

[beejayzed]

Are you using beryl/compiz? I find it is very stable when compiz fusion is disabled.

[nano]

I don't use compiz or beryl so that's not it. I'm playing on an up to date ubuntu feisty. I also tried it on my gentoo but I always get sync errors. It seems to come from my gcc flags, which I don't want to change.

[AF]

If you get the same crash repeatedly, what you do is you tell the developers and they fix it. If you keep quiet about a bug it never gets fixed.

How am I supposed to fix something if nobody tells me about it?

[YokoZar]

Newest Wine (0.9.43) has fixed the regression, TASClient just works again.

[semi]

I don't use compiz or beryl so that's not it. I'm playing on an up to date ubuntu feisty. I also tried it on my gentoo but I always get sync errors. It seems to come from my gcc flags, which I don't want to change.

Yeah, spring compilation options basically make or break your sync. Compile everything else as you wish, but for spring you really seem to need exactly same compiler and settings as the prebuilt release packages. Maybe something else works too but it's just pushing your luck.

[own3d]

It seems relevent to ask what these compile flags are since I often get these errors too.

[Tobi]

Optimization and debug levels shouldn't matter. I once tested this entire matrix of a lot of gcc versions with a lot of optimization options versus each other, and every tested GCC >= 4.0 (4.1.2, 4.2.0 and a dev build of 4.3.0 I think) with every optimization option (-O0 -O1 -O2 -O3 -Os) synced against each other (apart from 4.3.0 build crashing instantly if built with -O3, but remember it was a build of GCC trunk..).

The scons buildsystem does not inherit compiler flags from environment variables (if it does, that is a bug), so the only way to change them is by hacking the buildsystem or explicitly using the scons configure option to add them (not sure I added that option though )

The compiler flags when compiling with the default settings to scons configure are:
-fsingle-precision-constant -frounding-math -fsignaling-nans -mieee-fp -O2 -pipe -fno-strict-aliasing -fvisibility=hidden -mfpmath=387 -pthread