|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Neuntausend
GoonWaffe
Goonswarm Federation
90
   |
Posted - 2014.07.31 13:20:00 -
[1] - Quote
I haven't tried it myself, but Win32 Steam itself works well (with dwrite disabled) and so does Eve. Just give it a go, and report back. You may have to disable the Steam Overlay, but apart from that, I don't see why the Steam version shouldn't work. |
Neuntausend
GoonWaffe
Goonswarm Federation
100
|
Posted - 2014.08.13 05:43:00 -
[2] - Quote
Those scripts are definitely not needed, but it is a lot more convenient to have some kind of script to launch the game. In any case, you should tell us, what exactly is not working. Just from "It's not working" I could as well gather that there's a power outage, your computer is not running and you are posting this from a mobile phone. ;)
Please start Eve from a terminal, typing something like this:
WINEDEBUG=-all wine "/path/to/eve.exe"
and/or
WINEDEBUG=-all wine "/path/to/exefile.exe"
And copy/paste the output. |
Neuntausend
GoonWaffe
Goonswarm Federation
109
|
Posted - 2014.08.14 02:11:24 -
[3] - Quote
So I suppose the game itself works then? You can skip the launcher by running exefile.exe directly, if the launcher acts up. It resides inside the bin/ folder in the eve directory. That way you will only have to run the launcher every once in a while to update the game.
As for the launcher issues themselves - issues like that have been very common with older wine versions (<1.6) and the launcher is still a piece of crap and acts up every now and then, even on current wine versions. I can't really guess why it's not working for you. If you followed Kismeteers guide, it shouldn't act up all that often. The only thing I can suggest is that you make sure you don't have anything weird installed in your wine prefix and that there are no dll overrides in winecfg. From my experience it's a good idea to have Eve in a clean wine prefix for itself with no other windows software installed in it. You could also try deleting your launcher cache which I believe resides in Eve/launcher/cache, but that's just another shot in the dark. Besides that, no idea right now, sorry.
Oh and by the way, by setting WINEDEBUG=-all, you actually remove most debugging information instead of adding it (note that you don't actually "run" WINEDEBUG, as it's not a script or program. You merely set a variable by that name to "-all" - read: "minus all"). I like to do that, because wine more often than not just spams hundreds of "fixme:" messages that may be useful for wine developers, but usually don't contain anything useful for us mere mortals and make the output bigger and harder to read. Sadly your output doesn't show anything obvious like I sorta hoped it would (it usually does). You are however getting "'CreateActCtx' failed" and I can't check if I am getting it as well, as I am not in reach of my linux machine right now, but I don't think it's related. |
Neuntausend
Rens Nursing Home
119
|
Posted - 2015.04.20 13:37:51 -
[4] - Quote
That videocard might actually be a little too old, it has to be almost as old as Eve itself, if I'm not mistaken. But as far as I know, many repositories contain fglrx-legacy, maybe that works? |
Neuntausend
Rens Nursing Home
141
|
Posted - 2015.06.06 14:23:01 -
[5] - Quote
That happens sometime, and I haven't found a reliable way to avoid this every time. Hasn't happened to me lately, but I haven't been using unity in a long time.
Try fixed window mode ingame or a virtual desktop in winecfg set to your native screen resolution. |
|
|
| |
|