The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Jukebox?
by N. Andrew Walsh on Friday December 4th 2009, 10:19
So, I've managed to get the Dominion 1.0.1 patch working fine, but for an annoying problem: The jukebox doesn't play any of the tracks in the InFlight playlist. It just scrolls through them. Usually, this means that the audio driver is bugged, or the player can't find the file.
I found a few bugs, but if they are related to wine / nvidia or Fedora
i can not tell.
When mining, and "turrets effects" + "effects" is turned on, EVE practically freeze, tho it dont crash, so you can enter settings, and turn "turrets effects" + "effects" off.
And it runs perfectly ... so mining without beam and sound is actually not that bad :D
When in combat, this is no issue ... tho Salvaging has the same prob.
When setting Shader Quality to high, asteroids disappear.
Setting it to medium fixes it.
Info : it runs as smoothly and nice as it does on Windows, same FPS etc.
SiSi client?
by N. Andrew Walsh on Thursday November 26th 2009, 18:36
I'm not sure if this has been asked already or not:
I would like to use the SiSi server from time to time, but the instructions for setting it up use a special call passed to the client via a desktop shortcut (specifically, the IP to the SiSi server).
What's the way to do this under wine? Is there a specific command to match the windows one? That command is (taken from the EVE site):
RE: SiSi client? by Brian Wolfe on
Tuesday December 1st 2009, 13:31
Ubuntu-9.10 + Wine-1.1.32 (any wine version really)
by Scot McPherson on Sunday November 1st 2009, 18:20
The upgrade to ubuntu-9.10 has caused a problem with Eve Online, this is now specifically a wine problem, however it does affect gameplay of eve.
I have a workaround that many people and myself collaborated on, and was discovered by disabling networking while starting eve-online, then reconnecting before logging on.
The problem which occurs before the logon window is displayed, and therefore caused Eve to crash after some timeout period.
What happens is Bits is trying to look for possible upgrades, but it fails to connect properly somehow, disabling DNS, or the network allows it to just fail and move on to the next step.
A much less drastic measure is to configure the prefs.ini file found in local settings/application data to "BitsCancelled=0". Each time Eve is started, it will rewrite "BitsCancelled=1" and you therefore much repeat this step each time you want to start eve.
The following perl command will work if you are in the correct directory:
$ perl -pi -e 's/bitsCancelled=1/bitsCancelled=0/' prefs.ini
This is obviously a work around, and I believe it has something to do with the kernel, as do others, but this should be helpful to people wanted to get online with Eve right now.
