LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-16-2020, 10:56 AM   #31
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 777

Original Poster
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
Sad day :(


Bethesda has apparently added the Denuvo anti-cheat update to DOOM Eternal, which has the added bonus that now it will no longer work on Linux.

It looks like Bethesda has a somewhat lackadaisical attitude towards Linux gamers, and that has both good and bad aspects.

The good:
  • Bethesda is apparently not caring one way or another about Linux; they're not taking any legal action against Valve Software

The bad:
  • If Bethesda updates their software, their only apparent concern is how it interacts with Windows; if it breaks things on the Linux side, it's on the Linux (read: Steam) people to fix things.

A lovely situation to be in. Now I'll have to bide my time and wait for yet another fix either from an unofficial source, or Steam (officially).

Cheers!
 
Old 05-16-2020, 01:05 PM   #32
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 368

Rep: Reputation: 242Reputation: 242Reputation: 242
Yes, that's a risk you take when you buy games with the expectation that they are going to run in a translated environment. Some vendors are indifferent, but some are hostile. For example EA's cheat detection software has banned people running through Wine, and EA thinks that's right because it's running in a modified environment and they can't tell if you're cheating or not.

It's always going to be one update away from being broken. Not only game patches, but updates to your system.

I had some of my games broken for months. Wolfenstein II New Colossus (also Bethesda) worked perfectly when I bought it but suddenly started throwing Vulkan errors and wouldn't launch. Mesa eventually fixed it by adding specific workarounds for it.

Some of my old favourites that used to work were broken for months and suddenly Mesa 20.0.1 (not 20.0.0) fixed them. Both F.E.A.R 2 Project Origin and Far Cry 2 had similar problems (corruption and crashing) until Mesa 20.0.1
 
2 members found this post helpful.
Old 05-16-2020, 03:24 PM   #33
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 777

Original Poster
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
I recently acquired a Power Mac G5 single-core 1.8 GHz that I bought for s***s and giggles (read: I bought it because I wanted to have one). I also discovered that UT 2004 was available for it, and so I installed it on the Mac. The combination of the seamless video and audio capabilities of Tiger, as well as its low RAM requirements and the last version to incorporate the Classic Environment, combined with the fantastic gameplay of UT2004, has made me realize that graphical goodness isn't all there is to a great gaming experience.

I really dig the old-school gaming scene, and plan on wasting many hours there until such time as Bethesda gets their heads out of their a**es about this whole anti-cheat thing. Might take a while, though, as the corporate heads are slow about common sense.

NOTE: Classic Environment is used for the Unreal Gold and UT 99 games, respectively.
 
Old 05-16-2020, 03:58 PM   #34
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 368

Rep: Reputation: 242Reputation: 242Reputation: 242
I like me some UT2004 instagib. That's one of the first games I bought for Linux back in the day. I STILL have the same directory that's been copied between computers and Linux distros ever since. Icculus built some 64 bit clients in one of the patches, and all I have to do is drop some working libraries in the program directory (the ones I currently have in there have been working for years) for example a 64 bit libstdc++.so.5

Tons of addon maps (community created) for it. Of course it's rudimentary now (not even shaders at that time, fixed pipeline graphics), but in its day UT2004 was graphical goodness.
 
Old 05-16-2020, 04:32 PM   #35
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 368

Rep: Reputation: 242Reputation: 242Reputation: 242
You just got me thinking about that, I hadn't played UT2004 in a while, and never on this LFS system (I don't play games on this setup, it's my more serious OS). I had the game directory on a storage drive, so all I had to do was copy /home/grogan/.ut2004 from another box and it started up seamlessly.

I just had a couple of fun instagib deathmatches. Love the splatter effects, they still look great :-)

Game will run at whatever resolution you edit in UT2004.ini (FullscreenViewportX and FullscreenViewportY), though some objects might look a bit out of aspect. One thing that comes to mind, if using a round reticle for aiming it might be a bit oval shaped.

The last 64 bit libraries I updated in its System directory years ago are still working. libSDL looks like I updated it in 2017, it's probably from Slackware. I think I took that libstdc++.so.5 from SlamD64, as Slackware didn't have a 64 bit distro yet at that time.

Code:
Sep 21  2010 libartsc.so -> libartsc.so.0.0.0
Sep 21  2010 libartsc.so.0 -> libartsc.so.0.0.0
Feb 28  2008 libartsc.so.0.0.0
Sep 11  2017 libSDL-1.2.so.0 -> libSDL-1.2.so.0.11.4
Sep 11  2017 libSDL-1.2.so.0.11.4
Sep 21  2010 libstdc++.so.5 -> libstdc++.so.5.0.6
May 25  2006 libstdc++.so.5.0.6
Sep 27  2010 openal.so

Last edited by TheRealGrogan; 05-16-2020 at 04:38 PM.
 
Old 05-16-2020, 04:45 PM   #36
Bindestreck
Member
 
Registered: Jul 2011
Location: Sweden
Distribution: Slackware
Posts: 687

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
If you really really, still, wanna play Doom Eternal, like right now, there are workarounds: https://github.com/ValveSoftware/Proton/issues/3773

Basically, you have to revert the updates.
 
2 members found this post helpful.
Old 05-16-2020, 07:09 PM   #37
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 777

Original Poster
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
Quote:
Originally Posted by Bindestreck View Post
If you really really, still, wanna play Doom Eternal, like right now, there are workarounds: https://github.com/ValveSoftware/Proton/issues/3773

Basically, you have to revert the updates.
Yeah, it looks like you have to continually clean up the "mess" left by the continual updating. What a mess.
 
Old 05-16-2020, 07:16 PM   #38
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 777

Original Poster
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
Quote:
Originally Posted by TheRealGrogan View Post
You just got me thinking about that, I hadn't played UT2004 in a while, and never on this LFS system (I don't play games on this setup, it's my more serious OS). I had the game directory on a storage drive, so all I had to do was copy /home/grogan/.ut2004 from another box and it started up seamlessly.

I just had a couple of fun instagib deathmatches. Love the splatter effects, they still look great :-)

Game will run at whatever resolution you edit in UT2004.ini (FullscreenViewportX and FullscreenViewportY), though some objects might look a bit out of aspect. One thing that comes to mind, if using a round reticle for aiming it might be a bit oval shaped.
Did I mention that UT2004 is gaming perfection? The graphics are still goodness personified, the music score is outstanding, and the taunts are the best I've encountered. Some great examples are:
  • Duck faster next time!
  • Just hold still, and I'll make it quick!
  • Hold still, da**it!
  • Try turning the safety off!
  • Nailed 'em!
  • Kiss my a**!
  • My house!
  • Burn, baby!
  • You die too easily!
  • Suck on this!
  • You fight like Nali!
  • You fight like a girl!

There are probably more I've missed, but irreverent comments like the ones above are part of the very reason we do fragging - stress relief, and what better way to relieve stress than irreverent commenting and blood/gore splattering? And yes, the explosions still look great!
 
Old 05-16-2020, 10:04 PM   #39
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 368

Rep: Reputation: 242Reputation: 242Reputation: 242
Yes, I love the taunts in ut2004. It's not so much what they are saying, but the voices heheh

"You dick!" in that evil voice is probably my favourite.

Gaming perfection... back then those were the only games I liked. I wasn't much into computer games, but Unreal Tournament games were what games were to me. I had UT2003 before that, but by the time I got it working on Linux (needed to actually recompile XFree86 back then, because ST3C had to be enabled for Mesa, it wouldn't dlopen the library... that was why I could never get it to work for my ATI Radeon) UT2004 was out and it didn't need ST3C compression. I bought an Nvidia card soon after that, for Doom 3 and Quake 4.
 
Old 05-17-2020, 12:03 AM   #40
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,555

Rep: Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347Reputation: 2347
Just saw this thread after asking for a refund for Doom Eternal from Steam. Seems the latest update stops it running on Linux.
Not sure how Valve will respond but had to ask the question since I've only owned it for few weeks.
Seems that EA are very anti-Linux and like to break Linux compatibility wherever they can. Not really sure who at EA has this issue and why.
 
Old 05-17-2020, 12:23 AM   #41
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 777

Original Poster
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
DOOM Eternal Anti-Crack Reversal Tutorial

According to the steps laid out (in bits and pieces!) in the linked thread, it is possible to revert back to the previous working version, and configure Steam such that it will not update again, leaving the game in a playable state. It was successful on my system.

Steps:
  • Copy and paste the following script into your favorite text editor:
    Code:
    #!/usr/bin/env bash
    
    set -e
    
    # doomgrader required config
    STEAM_USERNAME=xxx
    STEAM_PASSWORD=xxx
    
    # doomgrader option config
    DOOMGRADER_ROOT=~/doomgrader
    STEAM_PATH=~/.steam/steam/steamapps/common
    
    # doomgrader internal paths
    DOWNLOAD_PATH=$DOOMGRADER_ROOT/files
    DEPOTDOWNLOADER_PATH=$DOOMGRADER_ROOT/depotdownloader
    
    # make doomgrader directories
    mkdir -p $DOOMGRADER_ROOT $DOWNLOAD_PATH $DEPOTDOWNLOADER_PATH
    
    # download, extract and make depotdownloader executable
    pushd $DEPOTDOWNLOADER_PATH
    
    wget \
    https://github.com/SteamRE/DepotDownloader/releases/download/DepotDownloader_2.3.4/depotdownloader-2.3.4.zip \
    -O depotdownloader_2.3.4.zip
    
    unzip depotdownloader_2.3.4.zip 
    
    chmod +x depotdownloader
    
    # download the depots
    
    ./depotdownloader -app 782330 -depot 782332 -manifest 4641765937586464647 -username "$STEAM_USERNAME" -password "$STEAM_PASSWORD" -remember-password -dir "$DOWNLOAD_PATH"
    ./depotdownloader -app 782330 -depot 782333 -manifest 4686311672633195957 -username "$STEAM_USERNAME" -password "$STEAM_PASSWORD" -remember-password -dir "$DOWNLOAD_PATH"
    ./depotdownloader -app 782330 -depot 782334 -manifest 2624212357815850298 -username "$STEAM_USERNAME" -password "$STEAM_PASSWORD" -remember-password -dir "$DOWNLOAD_PATH"
    ./depotdownloader -app 782330 -depot 782335 -manifest 8671913471625122045 -username "$STEAM_USERNAME" -password "$STEAM_PASSWORD" -remember-password -dir "$DOWNLOAD_PATH"
    ./depotdownloader -app 782330 -depot 782336 -manifest 4248922069342282231 -username "$STEAM_USERNAME" -password "$STEAM_PASSWORD" -remember-password -dir "$DOWNLOAD_PATH"
    ./depotdownloader -app 782330 -depot 782339 -manifest 8937962102049582968 -username "$STEAM_USERNAME" -password "$STEAM_PASSWORD" -remember-password -dir "$DOWNLOAD_PATH"
    
    # copy game files to steam dir
    # coming soon
  • Name it doomgrader.sh, make it executable, and place it in a directory of your choosing.
  • Edit the script and add your username and password, as these will be needed to authenticate your script to the Steam servers.
  • You will need a program, dotnet-runtime, which contains the program dotnet, to complete the process. This can be downloaded from SBo using Alien BOB's tutorial for downloading and setting up sbopkg.

    Quote:
    If you did not yet install sbopkg, download and install it now (the current version of sbopkg may differ from the package version in the example below):
    Code:
        # wget https://github.com/sbopkg/sbopkg/releases/download/0.38.1/sbopkg-0.38.1-noarch-1_wsr.tgz
        # installpkg sbopkg-0.38.1-noarch-1_wsr.tgz
    If you are running Slackware-current instead of a stable release like 14.2, then you need to edit the following two files before you run sbopkg for the first time:
    Code:
        # vi /etc/sbopkg/sbopkg.conf
        # vi /usr/sbin/sqg
    … and change the lines:
    Code:
        REPO_NAME=${REPO_NAME:-SBo}
        REPO_BRANCH=${REPO_BRANCH:-14.2}
    to:
    Code:
        REPO_NAME=${REPO_NAME:-SBo-git}
        REPO_BRANCH=${REPO_BRANCH:-current}
    When that’s been taken care of, we need to initialize the local sbopkg database by letting it clone the git repository of slackbuilds.org. Next we run the SlackBuild Queuefile Generator (sqg) script which is part of the sbopkg package. The sqg script examines the “.info” files of the complete slackbuilds.org locally downloaded copy. It uses the dependency information inside these info files to generate “queue files”. A queue file contains the list of packages which have to be built before the actual program you are interested in… aka “the dependencies”. This saves us from reading these info files ourselves to find out what it is that we need to build and in what order.
    Code:
        # sbopkg -r
        # sqg -a
    After you have initialized the sbopkg program this way, you could now simply run:
    Code:
        # sbopkg -k -i dotnet-runtime
  • After the dotnet-runtime package is installed, then you can run the script. Note that this process will take some time, as upwards of 36GB of files are needed to replace all of the files needed to revert to the previous working version.
  • These files will be placed in ~/doomgrader/files. Run the following commands to copy these files to the working DOOM Eternal directory of Steam:

    Code:
    cd ~/doomgrader/files
    cp -Rv * ~/.local/share/Steam/steamapps/common/DOOMEternal/

Now, to effectively disable updates in Steam (unofficially):
From https://old.reddit.com/r/Steam/comme...ate_this_game/
Quote:
Right click on the games, click on updates and then switch it to only update when i launch the game. Start playing your games in offline mod after this.

Or in the steam settings on the launcher click steam (top left corner), settings, downloads. Under downloads click only auto update games between and set a insanely small time like 2:00am-3:00am. Make sure its not a time your going to be using steam. Then set the bandwidth limit as small as possible.

Your best bet is to just launch steam in offline mode. Easiest way (to my knowledge) is to make sure steam dont start when your computer turns on. Disable your wifi temporarily, launch steam it will try and update, when it cant it will ask if you wish to start in offline mode click yes or whatever. Re-enabling wifi may connect steam so setting the download times will still be helpful.
Hopefully this messy workaround will not be needed for long, but we'll see.

NOTE: There is also an appmanifest file for the reverted DOOM Eternal in the linked thread. You will need to copy it to ~/.local/share/Steam/steamapps/, where the appmanifest files are stored.

Rip and tear, until it is done!

Last edited by 1337_powerslacker; 05-17-2020 at 12:28 AM.
 
3 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Vulkan API specification 1.2 released, new NVIDIA Vulkan Beta driver up LXer Syndicated Linux News 0 01-18-2020 06:50 AM
[SOLVED] Unable to run Vulkan in Slackware64-current with amdgpu ScrambledLogic Slackware 15 09-26-2018 12:32 PM
LXer: Vulkan at GDC videos now up, with Valve talking about porting Source 2 to Vulkan LXer Syndicated Linux News 0 03-19-2016 11:53 AM
LXer: Vulkan 1.0 and Vulkan SDK Announced for Linux and Windows LXer Syndicated Linux News 0 02-17-2016 02:43 AM
ZDoom 2.2.0 & Eternal Doom IV Raymond C. Glassford Linux - General 0 07-08-2008 09:49 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:22 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration