Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] 19 20 .. 23 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 32 post(s) |
Lucius Kalkoken
Ubiquitous Hurt The WeHurt Initiative
2
|
Posted - 2017.02.02 20:23:44 -
[511] - Quote
Both linux and mac use wine to run Eve, and the mac version is officially supported. So unless CCP decides to drop the mac as officially supported, you are right in that d3d9 will likely stay around until d3d11 is up and running properly.
That being said, wine has been running into issues trying to support d3d11 and that has mostly been due to the mac. Since the mac drivers don't support higher OpenGL versions (or have limitations/bugs that apple won't fix), they need to implement support for Metal on the mac. So instead of d3d11 => OpenGL it'll be d3d11 => Metal.
The good news is that Metal is very similar to Vulkan, the bad news is that time can only be spent once. People are always being pulled off to work on other projects, so progress is slow. You can't get new office versions working if you work on metal, and no metal if you work on d3d11, etc. You can check implementation progress on https://www.winehq.org/winapi_stats If you search for 'd3d' there, you'll see d3dx11 to be at most 27% done. What exactly Eve requires I don't know, but seeing as only very few games work with d3d11 at the moment, I think there is a long way to go.
On the other side I heard someone wanted to pick up developing the d3d11 state tracker for gallium (mesa). It's currently suffering from bit-rot, but you never know. On the whole I don't expect Eve to run d3d11 this year. I'd love to be surprised though.
There is no shame in not knowing, only in not wanting to know
|
Neuntausend
Rens Nursing Home
1393
|
Posted - 2017.02.03 00:45:35 -
[512] - Quote
Lucius Kalkoken wrote:On the other side I heard someone wanted to pick up developing the d3d11 state tracker for gallium (mesa). Not sure that's a good thing, though.
|
Pootis Spencer
Deep Space Research Inc.
0
|
Posted - 2017.02.03 13:33:40 -
[513] - Quote
Yaleesha Awesomecake wrote:Pootis Spencer wrote: I'm using clear Ubuntu 14.05. x64
I'm on a Debian-derived distro as well. For me this worked:
- In the top right theres a little E (eve logo) icon. Click show in file browser -> launcher logs
- It should open in a text editor. For me, the log was located in: /home/username/.local/share/CCP/EVE/Launcher
- Scroll down, look for "wine" *tab* "error" messages, with text like "failed to load .so lib"
- In my case it was a library called libldap_r-2.4.so.2. Depending on your distribution, it might be a different library/libraries.
- In a console, type "sudo apt install libldap2-dev:i386". Use the tab key to do some autocompletion if you're unsure about the exact name. The :i386 part is important to add, as you want the 32-bit version of the library.
Hope this helps. Ty 4 ur advise. Do as you say, but now it just ended with Setting up libsasl2-modules:i386 (2.1.25.dfsg1-17build1) ... Setting up libldap2-dev:i386 (2.4.31-1+nmu2ubuntu8.3) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... And nothing happens next. |
Narabri Beerbaum
Tukanas Innovations
0
|
Posted - 2017.02.06 21:44:43 -
[514] - Quote
Worked perfectly. After messing about with playonlinux and wine tricks, I consulted a friend and he pointed me here. Can't believe how easy this was - thank you muchly :-) |
Vincent Eneticum
Know your Role League of Unaligned Master Pilots
1
|
Posted - 2017.02.07 16:35:30 -
[515] - Quote
minor issue on debian stretch hereGǪ launcher doesnt start and logs this into the log file
EDIT: starting the evelauncher.sh with QT_LOGGING_RULES=qt.network.ssl.warning=false it starts but doesnt show the website
2017-02-07T17:32:45.672Z qt.network.ssl warning QSslSocket: cannot resolve CRYPTO_num_locks 2017-02-07T17:32:45.672Z qt.network.ssl warning QSslSocket: cannot resolve CRYPTO_set_id_callback 2017-02-07T17:32:45.672Z qt.network.ssl warning QSslSocket: cannot resolve CRYPTO_set_locking_callback 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve ERR_free_strings 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve EVP_CIPHER_CTX_init 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve sk_new_null 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve sk_push 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve sk_free 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve sk_num 2017-02-07T17:32:45.673Z qt.network.ssl warning QSslSocket: cannot resolve sk_pop_free 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve sk_value 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSL_library_init 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSL_load_error_strings 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSL_get_ex_new_index 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSLv2_client_method 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSLv3_client_method 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSLv23_client_method 2017-02-07T17:32:45.674Z qt.network.ssl warning QSslSocket: cannot resolve SSLv2_server_method 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve SSLv3_server_method 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve SSLv23_server_method 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve X509_STORE_CTX_get_chain 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve SSLeay 2017-02-07T17:32:45.675Z qt.network.ssl warning QSslSocket: cannot resolve SSLeay_version
|
Chuck Tetakel
University of Caille Gallente Federation
0
|
Posted - 2017.02.09 03:25:48 -
[516] - Quote
Heyho,
If you are on NixOS or have the nix package manager installed you can use this nix-expressions to install the Eve-Launcher. Because of some broken packages it requires some recent nix-channel like unstable, so either override the pkgs attribute or add a channel called nixos-unstable $ nix-channel --add https://nixos.org/channels/nixos-unstable nixos-unstable Also the expression either installs all dependencies in a fhs chroot (meaning the packages get symlinked where on would expect them in a fhs like environment), but i also fiddled a little bit with patching the binaries and libraries and on systems other than nixos i expect it might work (big problem being that on nixos the wine binary downloaded through the launcher can't find an interpreter).
One way to install the expression:
$ nix-env -f ./eve.nix -i
(there are probably a lot of dependencies that could be thrown out, Also currently everything is thrown into $out/bin which is far from perfect ( should be an easy fix though ), I will probably clean it up later ) |
Yuki L'Avalier
Garoun Investment Bank Gallente Federation
0
|
Posted - 2017.02.09 04:32:07 -
[517] - Quote
Arch linux, eve launcher don't work with native wine (version 2.1 "use custom wine" )
in log "wine client error:0: version mismatch 513\524" e t.c. |
Chuck Tetakel
University of Caille Gallente Federation
0
|
Posted - 2017.02.09 12:28:50 -
[518] - Quote
Yuki L'Avalier wrote:Arch linux, eve launcher don't work with native wine (version 2.1 "use custom wine" )
in log "wine client error:0: version mismatch 513\524" e t.c.
Remove or move ~/.eve/wineenv , to something like ~/.eve/wineenv-ccp and start the Eve Launcher. .wineenv will than be recreated using the wine you specified, so the versions match. Afterwards you might want to transfer over your eve configurations from the old wineenv folder. |
Confluence Eullon
Order In Disorder Curatores Veritatis Alliance
0
|
Posted - 2017.02.09 12:34:50 -
[519] - Quote
so everything worked perfectly on my relatively new installation of mint 18. 1 problem, 15 minutes in the game is still 'Processing bulk data'. Could this simply be a hardware problem? or do I need to change or install some software.
My PC has 6 gigs ram, 2.4ghz core 2 duo, 2 gig 7770 oc edition. so pretty old, Eve ran without a problem on windows though. |
Blade Kanjus
EVE University Ivy League
0
|
Posted - 2017.02.10 23:30:00 -
[520] - Quote
Would anyone be so kind to walk me through step-by-step process to run Eve?
I'm new to linux (runing ubuntu 16.04). I've got some experience with scripts.
This is mostly so I, and other noobs, can learn some linux skills. (Goal number two is to play Eve!)
I know this is a huge ask....but would be grateful for anyone who likes to teach. |
|
Blutjetz
Viziam Amarr Empire
0
|
Posted - 2017.02.11 06:41:20 -
[521] - Quote
Is there anyway to know when you are making an updated version of this great launcher? I am wondering 'cause I have created a AUR for your launcher ;) |
Vodnik Theseus
The Scope Gallente Federation
0
|
Posted - 2017.02.11 13:16:10 -
[522] - Quote
Blutjetz wrote:Is there anyway to know when you are making an updated version of this great launcher? I am wondering 'cause I have created a AUR for your launcher ;) I'm using your AUR package, and I'd just like to say thanks. |
Victoria Zongo
Derelik Privateers
0
|
Posted - 2017.02.11 21:55:34 -
[523] - Quote
Confluence Eullon wrote:so everything worked perfectly on my relatively new installation of mint 18. 1 problem, 15 minutes in the game is still 'Processing bulk data'. Could this simply be a hardware problem? or do I need to change or install some software.
My PC has 6 gigs ram, 2.4ghz core 2 duo, 2 gig 7770 oc edition. so pretty old, Eve ran without a problem on windows though.
Indeed, it took 45mins for exiting the "processing bulk data" stage, but then it worked fine. This works great in Linuxmint 18.1 Xfce 64bit edition.
Thank you for this great tool |
Maresse en Tilavine
Breaux-Pliese Consortium
6
|
Posted - 2017.02.14 10:07:12 -
[524] - Quote
Ran the Linux launcher today after a friend pointed out it existed (Didn't know about it until now, go figure ). I saved a debug log in the hopes of helping further development: Launcher log 2017-02-14 (Dropbox)
I'm running a Frankenbuild of BunsenLabs built on Debian 8 with SteamOS repos added for updated Nvidia drivers. |
Mephasor Maidan
Aliastra Gallente Federation
0
|
Posted - 2017.02.16 01:42:56 -
[525] - Quote
Linux Mint 18.1 64bit
Downloaded, extracted, started and am playing right now. No problems whatsoever.
Great job! Thank you |
phlatch
O C C U P Y Test Alliance Please Ignore
0
|
Posted - 2017.02.18 19:46:18 -
[526] - Quote
Blutjetz wrote:Is there anyway to know when you are making an updated version of this great launcher? I am wondering 'cause I have created a AUR for your launcher ;)
http://binaries.eveonline.com/evelauncher_linux_release.json |
Vincent Eneticum
Know your Role League of Unaligned Master Pilots
7
|
Posted - 2017.02.19 18:58:27 -
[527] - Quote
just a headsup, atm the launcher doesnt work with OpenSSL 1.1 (which is now default on my system, Debian Stretch)
changing the symlink /usr/lib/x86_64-linux-gnu/libssl.so to link to /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 instead of /usr/lib/x86_64-linux-gnu/libssl.so.1.1 fixes it for the momentGǪ |
Ravow
Booster del Norte
35
|
Posted - 2017.02.20 13:29:17 -
[528] - Quote
It really really really need a way to have the normal "pre-launcher" era LOG..
The normal logs that show on the terminal when you launch anything manually with wine and that obey to envvar to add more debug.
Logging is required with specific envvar (not winedebug) to fix a problem in the Nine state tracker that exist since about two month.
no log, no fix. And as soon as I can't revert the commit that cause the bug because of some dependency, I drop my subs, that it.. I will not play at 40 fps. It was possible to debug back in 2006 up to when CCP forced us to use that launcher... |
Neuntausend
GoonWaffe Goonswarm Federation
1601
|
Posted - 2017.02.24 05:45:36 -
[529] - Quote
You can in principle still run the exefile.exe in the bin folder directly. You can just not log in through it. Maybe that will suffice?
Out of personal interest, what is this problem in the Nine state tracker you have mentioned? |
Ravow
Booster del Norte
36
|
Posted - 2017.02.24 18:11:04 -
[530] - Quote
Neuntausend wrote:You can in principle still run the exefile.exe in the bin folder directly. You can just not log in through it. Maybe that will suffice?
Out of personal interest, what is this problem in the Nine state tracker you have mentioned?
The problem is that it crash EVE when you try to see a wormhole (it show on the overview but not on the screen as it crash I think while loading the volumes textures. To debug that, I have to go see a wormhole while having all the debug switch set to debug Gallium-9 and of course, I have to be able to get that raw log. So I have to be logged in and using the launcher that mask everything, unfortunately. |
|
Lucius Kalkoken
Ubiquitous Hurt The WeHurt Initiative
2
|
Posted - 2017.02.25 12:40:17 -
[531] - Quote
Ravow wrote:Neuntausend wrote:You can in principle still run the exefile.exe in the bin folder directly. You can just not log in through it. Maybe that will suffice?
Out of personal interest, what is this problem in the Nine state tracker you have mentioned? The problem is that it crash EVE when you try to see a wormhole (it show on the overview but not on the screen as it crash I think while loading the volumes textures. To debug that, I have to go see a wormhole while having all the debug switch set to debug Gallium-9 and of course, I have to be able to get that raw log. So I have to be logged in and using the launcher that mask everything, unfortunately. https://github.com/Frosty-nee/rlel
It'll probably work in wine directly, but it also shows how to launch the client manually. Which is basically just giving it the SSO token to use with some other settings switches.
Good luck!
There is no shame in not knowing, only in not wanting to know
|
Gallente Citizen 830016900
Federal Navy Academy Gallente Federation
0
|
Posted - 2017.02.27 16:49:37 -
[532] - Quote
Attempting to execute the launcher ./evelauncher did not work.
Had to bash evelauncher.sh
bash evelauncher.sh [0227/104441:WARNING:resource_bundle.cc(291)] locale_file_path.empty() for locale Installed Qt WebEngine locales directory not found at location /home/justin/evelauncher/translations/qtwebengine_locales. Trying application directory... Qt WebEngine locales directory not found at location /home/justin/evelauncher/qtwebengine_locales. Trying fallback directory... Translations MAY NOT not be correct. [0227/104441:WARNING:resource_bundle.cc(291)] locale_file_path.empty() for locale
Hope this helps. |
Yuki Renard
Dusk Mirror
0
|
Posted - 2017.02.28 13:30:53 -
[533] - Quote
It would be good to add to the launcher option "Start in a separate X server" |
Ravow
Booster del Norte
36
|
Posted - 2017.03.01 03:31:23 -
[534] - Quote
Yuki Renard wrote:It would be good to add to the launcher option "Start in a separate X server"
Yep, Adding a way to use envvar would fix that too. You could set it to DISPLAY=:1.0 (for the second Xorg, first "screen") |
Ransu Asanari
V0LTA WE FORM V0LTA
517
|
Posted - 2017.03.01 06:19:25 -
[535] - Quote
Got the launcher working on SteamOS on an Intel NUC5i5MYHE. Was easier than I thought:
- Exit Steam Bigscreen Mode to Desktop Mode
- Open Xterm using ALT+F2 (I fixed getting the normal terminal to open with this)
- Set password for desktop account in terminal
- Set proper resolution and configure SteamOS-Tools repository
- Install playonlinux and wine (apt-get install playonlinux)
- Download Launcher, extract, run, and let it update.
- Login on launcher, run, and success!
Got Teamspeak3, Chrome, game emulators, and a bunch of other stuff running on the desktop. I set EVE to run as a borderless window, and turned down the graphics settings, but it worked rather well considering it's only an Intel HD Graphics 5500 on-board.
Seeing how easy this was, it's definitely one step closer to switching completely over to Linux on my main desktop.
Thanks for the launcher CCP Snorlax! |
Pootis Spencer
Deep Space Research Inc.
0
|
Posted - 2017.03.02 11:33:44 -
[536] - Quote
Hello Again. Now I receive such logs when I'm trying to launch EvE http://i64.tinypic.com/34sjsxh.jpg |
Ravow
Booster del Norte
36
|
Posted - 2017.03.03 18:28:05 -
[537] - Quote
Look like you ran out of Video drivers!
Install a proper driver for your Video card (Open Source with gallium-9 for AMD, Proprietary from Nvidia for Nvidia) and retry! |
Cryptic Sharvas
Hedion University Amarr Empire
0
|
Posted - 2017.03.06 23:14:49 -
[538] - Quote
I'm currently running Ubuntu Studio 16.04 with 2 AMD 280x video cards, and 3 monitors
The game launches and runs great on one monitor, however if I switch to another window, the game automatically minimizes.
Is this normal?
I'd like to run the game while I do other stuff on the computer, but I would like to keep an eye out for trouble or a full venture miner.
thanks. |
Lucius Kalkoken
Ubiquitous Hurt The WeHurt Initiative
2
|
Posted - 2017.03.06 23:23:12 -
[539] - Quote
Cryptic Sharvas wrote:I'm currently running Ubuntu Studio 16.04 with 2 AMD 280x video cards, and 3 monitors
The game launches and runs great on one monitor, however if I switch to another window, the game automatically minimizes.
Is this normal?
Yes, this is normal. Switch Eve in the ESC menu to use a fixed window and it'll work as you want it to.
There is no shame in not knowing, only in not wanting to know
|
Ranzabar
Aliastra Gallente Federation
166
|
Posted - 2017.03.11 22:28:43 -
[540] - Quote
You've made me a very happy Capsuleer.
Reporting that the launcher works great with Linux Mint 18.1 Cinnamon as long as you install the WineHQ stuff before you run it.
While I know the Linux crowd is way smaller than the MS crowd, CCP should still support this officially. IMHO - (which is worth nothing)
Abide
|
|
|
|
|
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] 19 20 .. 23 :: one page |
First page | Previous page | Next page | Last page |