Author Topic: Playing on wine (Linux/GNU) [ONGOING]  (Read 3100 times)

0 Members and 1 Guest are viewing this topic.

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #15 on: August 11, 2016, 05:50:58 PM »
some wonder why bother to play on Linux?

so far i found:
1. game latency differs locally on same machine (it's just funny)
2. FPS wildly change from 60 to 17 FPS, yet 17 FPS is still usable for brawling in light mechs? on Windows 25 meas it barely so?
3. The CPU seems to be used quite less then on windows (30% evenly spread vs 90% on one core and 20% on others evenly spread)
4. Game starts faster and smoother on wine and HDD than natively on SSD  ???

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING] 64bit and 32compat - multilib
« Reply #16 on: August 11, 2016, 06:11:37 PM »
the file i use to start my game on Linux/wine-staging instead of supplied launcher

filename:[MWLLgame.sh]
Code: [Select]
#! /bin/bash

v=0.3-alpha
#cleaning leftovers from late dinner ;)
killall Crysis.exe
killall -9 Crysis.exe
#cleaning shader cache for better performance each time
rm -r ~/Documents/My\ Games/Crysis\ Wars/Shaders/*

# reducing what wine spews at us
export WINEDEBUG=fixme-all

#uncnfirmed spead tweak:
#  export thread_submit=true

# switch comment whats appropriate
#  export WINEARCH=win32
  export WINEARCH=win64

# we controll which directory we want be runned by the script 
  export WINEPREFIX=~/.wine

#this can really beak things if enabled but try it?
#  export MESA_DEBUG=1

# we the humans check here wht renders our stuff
# if not "Gallium" then it's software = too slow
REND=$(glxinfo | grep "OpenGL renderer" | awk -F: '{print $2}' | awk -F"(" '{print $1}')
echo "Renderer:"$REND
echo "if the above is llvm and not an actual card the game will not work"

#here we do "magic" to run DX9 (only supported so far)
#and tell Srysis we want the MWLL mod not the OEM game :^)

OPT="-dx9 -mod MWLL"

case $WINEARCH in
win64)
     echo 64bit
     #here I cleverly avoid calling the path with my user name :)
     cd "${WINEPREFIX}/drive_c/Program Files (x86)/Electronic Arts/Crytek/Crysis Wars/Bin64"
     #here i cleverly ask to show the path so we see what WINEPREFIX was called
     pwd
     wine64 "C:\Program Files (x86)\Electronic Arts\Crytek\Crysis Wars\Bin64\Crysis.exe" $OPT # &> MWLL_debug.log
     #if uncommented, the last line's comment dumps a log file to the game folder - might prove usefull or a vaste of disk space
     ;;
win32)
     echo 32bit
     #here I cleverly avoid calling the path with my user name :)
     cd "${WINEPREFIX}/drive_c/Program Files/Electronic Arts/Crytek/Crysis Wars/Bin32"
     #here i cleverly ask to show the path so we see what WINEPREFIX was called
     pwd
     #here (hopefully) no shit hits the fan, and we land in game menu
     wine "C:\Program Files\Electronic Arts\Crytek\Crysis Wars\Bin32\Crysis.exe" $OPT # &> MWLL_debug.log
     #if uncommented, the last line's comment dumps a log file to the game folder - might prove usefull or a vaste of disk space
     ;;
esac
# to restore resolution put here what's appropriate or leave as is and just uncomment
#xrandr -s 0 # last good resolution
i have ~/bin in my user's path and save this file there
so all i type is :
Code: [Select]
$ MWLLGame.shor I made a launcher on my toolbar as can be seen on my attachment (XFCE desktop btw)

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #17 on: August 11, 2016, 08:40:00 PM »
corruptions that occur:

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #18 on: August 11, 2016, 08:43:21 PM »
good n nice stuff:
(note FPS) finky HD6770

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #19 on: August 12, 2016, 06:49:38 PM »
more garbles from 64bit Linux/Wine:

i noticed some fun facts:
The garbled items are _copies_ or so called instances of objects, not all copies are faulty
Sometimes the copies just "cure" out
Sometimes not
Once corrupted, the more chance it will get corrupted again, or until it "cures"
 what gives?  ???

Offline Bird_Thing

  • Recruit
  • *
  • Posts: 88
  • l33tp0intz: +7/-4
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #20 on: August 23, 2016, 09:14:08 PM »
Good news:
Had some free time (finally!) and got back to this.
I made a new "experiments" partition with Linux Mint's recent KDE Beta release installed. That OS uses the Ubuntu 16.04 package base and linux kernel 4.4, without which the galleon nine-related packages won't function properly.
I then opened up the terminal and entered (as described here):
Code: [Select]
sudo add-apt-repository ppa:wine/wine-builds
sudo apt-get update
sudo apt-get install --install-recommends wine-staging
sudo apt-get install wine-staging-amd64
Then did some research on getting gallium up and running (eventually wound up here) and found I had to type:
Code: [Select]
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo add-apt-repository ppa:oibaf/gallium-nine
sudo add-apt-repository ppa:commendsarnex/winedri3
sudo apt-get update
sudo apt-get upgrade
I took out the
Code: [Select]
&& sudo apt-get install wine1.9 in the last line as wine was already installed via "sudo add-apt-repository ppa:wine/wine-builds" and "sudo apt-get update".
Next, I followed Fire's steps:
Code: [Select]
WINEARCH=win32 winecfg
sudo apt install winetricks
winetricks directx9
After all of the above was completed, I went to winecfg, went to the Staging tab and - though I couldn't get all of the options like "Enable VAAPI as backend for DXVA2 GPU decoding" - selected "Enable Gallium Nine for better D3D9 graphic performance."
That's pretty much all there was to it, aside from lot's of digging around on the internet.
I downloaded (well, moved from my other Linux partition to this one) the MWLL combined installer ran the "setup.exe" through wine, and applied the gamespy fix through wine as well.
After that, I just went to the location of the "MWLL.Launcher.exe", ran that through wine, and the game started working just fine. Connecting to servers works mostly fine (map changes work, though I did have one instance where a match timer ended but the map didn't change until I joined the fight - not sure if that's an issue on my end, though).
I did have the graphics glitches Fire mentions, though it seems maximizing the resolution (it was at 1024x768 by default) helped a little in reducing them, though they still accumulate over time.
Also, exiting the game works perfectly well for me, be it through ALT+F4 or the proper disconnect/exit game method.
« Last Edit: August 23, 2016, 09:38:57 PM by Bird_Thing »

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #21 on: August 23, 2016, 10:02:32 PM »
first of all i congratulate You and welcome to Linux gaming of this game (a special club, we use Radeons, right?)
 :D
then i notice You do actually run on 64bit and DX9 (as I see screenshots)

and You still owe us the whole config for those excellent  80 FPS

what gives?

CPU
GPU
kernel?
Mesa?
X's ATI driver?
wine is 1.9.15? (i know it's staging)
is it smooth to play? how does it compare to Win?

and shoot the glitches and everything else :)
does it make recording?

could you please also:
Code: [Select]
$glxinfo | grep "OpenGL renderer"and report ? :)

re game exit:
i was referring to using the console command QUIT, it just hangs most of times :/

Offline Bird_Thing

  • Recruit
  • *
  • Posts: 88
  • l33tp0intz: +7/-4
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #22 on: August 23, 2016, 11:13:57 PM »
Thanks for the congrats! ;D

So, system specs:
RAM: 8 GB
CPU: AMD FX 6300 @3.5 GHz
GPU: AMD R9 270x (2GB GDDR5 RAM)
Kernel: 4.4.0-34-Generic
Mesa: 12.1.0-devel
X ATI Driver: Not sure what you mean, but "lspci -nn | grep VGA" returns
Code: [Select]
VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810]
Wine: 1.9.17
I think wine 1.9.15 and newer is where things start to work.
All hardware is stock; no overclocking or other special tricks.
The game does indeed play smoothly, and it plays mostly just like it does in Windows (aside from the graphics bugs).
I haven't tried recording anything yet, but I'll try later this week.
Code: [Select]
glxinfo | grep "OpenGL renderer" returns:
Code: [Select]
Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-34-generic, LLVM 3.9.0)

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #23 on: August 24, 2016, 10:56:12 AM »
Your Debian/Ubuntu/Mint HOWTO is of great importance for the most Linux Gamers come from those distros  8)

for ATI driver i found it on various readouts and HOWTOs.
I find mine by examining the X log:
Code: [Select]
less /var/log/Xorg.0.logand there i seek for radeon
type [/] and type [radeon] and [n] for advancing to find:
Code: [Select]
[    27.547] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[    27.569] (II) Module radeon: vendor="X.Org Foundation"
[    27.569]    compiled for 1.18.3, module version = 7.7.0
[    27.569]    Module class: X.Org Video Driver
[    27.569]    ABI class: X.Org Video Driver, version 20.0
so there is module version = 7.7.0 and that's just above 7.6 the minimal required :)

mine other readouts:
RAM 4GB DDR2 @800
CPU Xeon X5640 quadcore @3.16 (no OC due to MoBo power topped)
VGA MSI HD 6770 1GB DDR5

kernel (uname -vrm): 4.4.14 #1 SMP Fri Jun 24 13:30:15 CDT 2016 x86_64
Mesa: mesa-11.2.2-x86_64 & mesa-compat32-11.2.2-x86_64
(for 32 bit games on 64 OS)
X ATI driver : 7.7.0
vdpau and DRI: dri2 for my card only :( (AIGLX someting?)
Code: [Select]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] [1002:68ba]wine 1.9.15

the directX9 and CCMT options toggle each other, the others seem to be 64 bit dependent (GTK3)?

GLX renderer:
Code: [Select]
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0, LLVM 3.8.0)
You should be on DRI3 there, and that's just great :)
Does Your FPS compare to Win equal?  :o Which is faster X or Win?

Offline Bird_Thing

  • Recruit
  • *
  • Posts: 88
  • l33tp0intz: +7/-4
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #24 on: August 24, 2016, 05:47:37 PM »
Ok, so
Code: [Select]
less /var/log/Xorg.0.log returns
Code: [Select]
[    46.490] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[    46.582] (II) Module radeon: vendor="X.Org Foundation"
[    46.582]    compiled for 1.18.3, module version = 7.7.99
[    46.582]    Module class: X.Org Video Driver
[    46.582]    ABI class: X.Org Video Driver, version 20.0
after searching for the right lines.

Also, it seems there's not a big difference in performance between running MWLL on Linux versus Windows, at least for me.
My system monitor (conky) shows the whole Crysis.exe program takes up 18-20% of both RAM and CPU usage. I think it's about the same on Windows.

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #25 on: August 24, 2016, 05:54:23 PM »
so, save the odd glitches, the performance is about equal?
same here too
 :)
Hope others (if any) report here too
 :D

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #26 on: August 25, 2016, 11:49:30 AM »
 :o woe and behold :o :
i had some afterthoughts
 ::) ??? :-\
the glitch in the game occurs exclusively on "instanced" objects
and only on those created while in game (run time instances, not spawn(init-) time instances).

i think its about preserving processor registers and states when switching "context", like interrupts and system calls.

Somewhere the states don't get preserved right when making these instances and some "wild" data (zeros?) get in the instance memory pointers of some sort.

This makes for those odd shapes and "memory dump" textures on them.

I witnessed on some occasion, the wild shapes can be cured by them selves (some sort of refresh?)

While being wild, the game has no problems processing it, just players suffer  ::), but on occasion it cures.  ???

It has nothing to do with rendering it is an memory+game+wine effect

If it's part of wine it's not changed form1.9.15 to 1.9.17 apparently?

just more two cents

edit: memory "vectors" changed to "pointers"
« Last Edit: August 25, 2016, 11:56:38 AM by cest73 »

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #27 on: August 27, 2017, 11:18:43 AM »
this is merely a heads-up, not a full report really:

Lately I've acquired tow VGAs:

1. Nvidia GTX-650 (Gainward) 2GB DDR5 ("Kepler 107" GPU)
2. Radeon HD7770 (OEM=???)  1GB DDR5 ("Cape Verde" GPU)

Both active cooled, operational and with an 6pin power plug (besides the PCIx16 power)

I've made both adapters run under Linux and windows (7), both on 64bit installs (i swithced to 64bit completely on *x86)
I've made the Nvidia run under both nouveau and OEM binary blob (latest to the time of download)
The Radeon, sadly, couldn't be tested to OEM drivers, as frglx fails to compile on recent Linux releases (abandon ware?)
 :-\
I've made videos of the install process:
https://youtu.be/VMo_7jDPpB4  <-- long-watch 15 mins!  8) take popcorn

And I plan to further post videos of the various combinations of drivers and VGAs.


The glitches seem to be due to Cyrengine <-> X11-driver interaction as they 100% "disappear" on the nvidia OEM binary driver?

the performance of the Open source driver seems to be as follows:
AMD/ATi:
radeon - on par or slightly below windows OEM drivers, works 'out of the box'
Nvidia:
noveau - 25% of windows OEM performance (11 FPS here), works 'out of the box'
nvidia - sub par performance vs win OEM, but glitch free operation, can be installed only in root maintenance mode and init 3 level (however this is called on systemd distros).

Stay tuned...

Offline cest73

  • Star Captain
  • ***
  • Posts: 750
  • l33tp0intz: +21/-19
  • there are links in my signature -->
    • MW:LL game status online (kudos: Spooky)

Offline Bird_Thing

  • Recruit
  • *
  • Posts: 88
  • l33tp0intz: +7/-4
Re: Playing on wine (Linux/GNU) [ONGOING]
« Reply #29 on: September 03, 2017, 01:30:00 AM »
Made backups of my instructions as well, just in case.