I know the previous thread died because you're all having SEX, but I was busy changing the thermal paste in my old PC instead. I'm not sure if I did it very well because I can't see through the bastard heatsink, but the temperatures haven't gotten catastrophically worse as far as I can tell. I had a hell of a time getting the heat sink fan back in place, because it has these stupid pins instead of screws and they really didn't want to click into place. This is what I get for doing this on Friday the 13th, but I didn't realize the date until a few minutes ago.
I also broke the clip holding the little fan cable to the motherboard, or rather, the clip that made it impossible to fucking remove, so good riddance. I could barely get a grip on the tiny-ass plug with its sharp-ass corners, and prying a clip away from it at the same time as pulling it out was proving to be such a literal pain that I'm glad the fucker broke. I don't need a tiny little cable being held in place with 9000 pounds of force. It's snug enough. I'm glad this is only my old computer though.

File: 1770878072630368.jpg (646 KB, 1920x1080)

646 KB JPG

There's just something about games running natively on Linux...

File: 1767422452646065.jpg (695 KB, 1920x1080)

695 KB JPG

>>557364146
...Especially when they weren't designed to

File: Screenshot from 2026-02-1(...).png (1.28 MB, 1920x1200)

1.28 MB PNG

>>557364326
based

wish me luck on my date this evening

>>557367797
If serious, good luck and godspeed, and I hope you get to touch a nipple

>>557368575
yes, just it's cold out hoping to get a kiss. maybe nipple will come next date

Anyone tried that GOG version of Dino Crisis on Linux?
Yes, I see there's a Steam version with bizarrely higher system requirements and third-party DRM, but the GOG version is the same price and I assume the Enigma-infected Steam release is just for people who don't know GOG exists.

File: 1770498920570048.gif (732 KB, 400x400)

732 KB GIF

has anyone tried using BB Launcher-Mod Manager for playing Bloodborne on Linux? I followed this guy's guide to the best of my ability. I installed the Microsoft Visual C++ runtime with Wine, but I'm not sure how the BB Launcher appimage would use those runtimes. Any help is appreciated

>>557378024
whoops i forgot to add the link to the video guide
https://youtu.be/ni3AoIvUt0E

>>557378024
Why is skelly guy holding a Pepsi can. You cannot drink it, Mr... You have no digestive system

>>557379865
he drinks it because the carbonation feels funny when it touches his bones

>run updoots and restart
>kde enabled pointer acceleration on its own
what the FRICK

>>557381920
That's really weird. What distro?

>>557381920
Probably update caused your mouse device to change and KDE enables acceleration for all new mice.

>>557385485
Cachy.
>>557385536
It's a GPX superlight, and it's showing in system settings as "Logitech Pro X" which seems different. But I don't remember what it was before exactly. Also it's actually showing up in piper over wireless which is new.

Found a replacement for steamtinkerlaunch's Reshade implementation, LeShade.
Gonna switch to that one because steamtinkerlaunch isn't being developed anymore

Is there anything I should do before installing Lutris?
I know you need to install some other stuff to get some older/newer games to work as well.

>>557392415
32-bit graphic drivers

what's new an exciting for 6.19

File: 1764079345221620.webm (3.87 MB, 1920x1080)

3.87 MB WEBM

Funny little fella
>>557398160
my dkms modules are broken

File: 1754565312520506.webm (3.9 MB, 1920x1080)

3.9 MB WEBM

I am disappointed

>>557398160
Linux color pipeline. It will allow compositors to do hdr tonemapping (and other things) directly with fixed hardware instead of compositing, improving performance and battery usage

File: 1748737158586413.webm (3.91 MB, 1920x1080)

3.91 MB WEBM

>>557401891
Oh, that thing. I guess we're fully ready for KDE 6.6 next week now.

>>557400167
>my dkms modules
Which ones do you use?

>>557390813
>steamtinkerlaunch isn't being developed anymore
Sad if true

>>557390813
>>557404447
Any source on that?
I think it was updated not too long ago...

File: 1758348302596659.webm (3.88 MB, 1920x1080)

3.88 MB WEBM

Hey, give it back!
>>557405979
https://github.com/sonic2kk/steamtinkerlaunch/commits/master/
Yeah, 7 months ago, and update was negligible. Anyway, it's a huge barely maintainable bash script that has a lot of legacy shit that is no longer relevant.
I only used it for MO2 integration but now that there's Fluorine-Manager it's no longer needed.

File: 1740081413839725.webm (3.8 MB, 1920x1080)

3.8 MB WEBM

Some mods are fucking with close captions and I tired from finding out which ones.

>>557406413
>Anyway, it's a huge barely maintainable bash script that has a lot of legacy shit that is no longer relevant.
I know, it's just that every time a Linux FOSS software I've used gets abandoned, I get sadder.
I'm still worried about Lutris ending this way too.

Is there any way to mitigate input lag caused by high GPU usage?
I've been testing a few more demanding titles on linux (cachyOS) and I thought my controller was getting stupidly laggy sometimes (and I don't mean silly couple of milisecond latency shits, I mean almost half a second of the analog doing something without me even touching it, even once started just spinning endlessly). I thought to try capping framerates with lower settings, but as I suspected, the input lag problem is generally present not when the framerate is low, but the GPU usage is at around 98 to 100%. Of course it's less noticeable if that happens at high framerates, but the point is it's much more severe than I thought.
I thought it was my gamepad as well, but I tried with my mouse and it wasn't a lot better either. There is definitely some GPU usage being so high it's not letting this thing absorb inputs fast. Any ideas? Any scheduler or whatever I can use to prevent this? CPU usage isn't high.
I'm on AMD. I noticed one thing: It does get worse if I use Proton-GE instead of Proton-CachyOS. So there might be something there.

>>557381920
Ah, happened to me too.
Holy shit, I thought it was a me thing.
It enables high resolution scrolling as well by default, which is gonna throw off people with logitech mice with infinite scrolling. Oh deary me

File: 1749377181150213.webm (3.89 MB, 1920x1080)

3.89 MB WEBM

>>557407551
I'm a big Lutris user, but I think it's no big deal now that we have Faugus launcher. Lutris is also huge pile of legacy trash that is barely maintained lately (and absolutely retarded release schedule).
Faugus + Fluorine is a new meta.

>>557409242
>input lag
wired or wireless?
gpu usage has no effect on input lag

>>557410343
What the hell is a Fluorine
I didn't like Lutris for quite some time. I remember still having to deal with manually creating folders for new prefixes which was kinda dumb. I went to bottles, found it to work much simpler, but it was janky and I remember having a lot of trouble with japanese fonts because they weren't registering correctly. Then I tried Heroic and it worked quite well. Now there's this faugus thing, I'm trying to catch up. What the hell is Fluorine? Is that another thing on top?

>>557410735
I tested both.
I mean I'm having an input lag difference that at least correlates with what I'm seeing on screen. MangoHUD is reporting maxed out GPU usage, I get tons of input lag. If I don't, I don't get the same input lag. If for instance I set graphical settings down, so my FPS go higher, but then I cap the FPS to something similar to what I got before, and the GPU usage goes down to 80% or 70%, the input lag isn't there, is what I'm referring to.
So something is there and I'm trying to figure it out. If it has no effect, then what the fuck else?

>>557411356
wayland or x11?

>>557410343
For obscure Japanese porn visual novel, Lutris is still unsurpassed, unfortunately...

>>557411508
Wayland wine and gamescope (not on a separate session though, might have to try this)
So it's wayland behavior?

>>557410947
>What the hell is a Fluorine
It's a MO2 port for Linux so you don't have to run mod manager through Proton like a retard
https://github.com/SulfurNitride/Fluorine-Manager

>>557412663
I'm not too well versed on modding in general. Does that work with cyberpunk mods and other games? Or is it more for people who enjoy bethesda games?

>>557412594
Wayland shouldn't be an issue as long you're using anything other than KDE.
Gamescope is broken and in maintenance mode and I'm sure Valve doesn't care about it anymore unless they have an update ready for the Steam machine release.

>>557413278
I tried using GNOME and while I got more consistent frames somehow, I got this weird thing where VRR enabled meant the framerate got halved (so it reported 70fps for instance, but it looked 35 until I alt+tabbed which obviously disabled VRR). That is on wine on wayland mode. Also HDR worked really weird.
I thought of trying Hyprland but last time I tried setting up HDR in there it was a royal mess. I don't think I have any more options.

>>557412895
It mentions Cyberpunk, but I haven't tested it myself. It should behave like original MO2 but being Linux native. I've already tried on New Vegas and everything works, including NXM handling

>>557413798
>I don't think I have any more options.
KDE, HDR works on it.

>>557417030
Ok maybe I'm reading wrong but did you mean to say "Wayland shouldn't be an issue as long as you aren't using anything other than KDE?"

>>557417285
Yeah, I'm a retard, I meant it shouldn't be an issue if you're using KDE, the other DEs are filled with problems, especially GNOME.

File: xlibre.png (403 KB, 1920x1080)

403 KB PNG

>>557361009
Who is gaming on Xlibre here? I tried it out with a 4070 ti super and Deep Rock Galactic worked well except alt-tabbing out made the rest of my computer run slow. Rdr2 would start up but was a mess of screen tearing. Still I think there may be something decent there for people that like to tinker.

File: 1769036547215814.webm (3.87 MB, 1920x1080)

3.87 MB WEBM

Bullseye!

>>557423703
Is this the X11 fork that's making the Wayland community poop their pants in embarrassing rage?

File: 1769123390374943.webm (3.96 MB, 1920x1080)

3.96 MB WEBM

I've got a feeling that text elements like chat and MangoHUD are eating bitrate like crazy.

>>557361009
I want to be a cowboy, but RDR2 won't launch

>>557432271
It's probably the foliage that is eating the bitrate. I believe video codecs are smart with static text

File: 1757383527435129.webm (3.89 MB, 1920x1080)

3.89 MB WEBM

Should've used the rocket launcher more before losing it in the next level.

File: 1748414938311800.webm (3.87 MB, 1920x1080)

3.87 MB WEBM

>retard NPC turns around instead of continuing to run away

File: 1763845712798524.webm (3.86 MB, 1920x1080)

3.86 MB WEBM

Killed myself with the BFG 2 times but was successful on the 3rd attempt.

File: 1769749412634760.webm (3.89 MB, 1920x1080)

3.89 MB WEBM

ENTER!!!

File: 1748848153303437.webm (3.86 MB, 1920x1080)

3.86 MB WEBM

This time, it's not shoot it until it dies, but have to kill mobs to charge up the soul cube to do damage)kill the cyber demon.
And with this the base game is done, onto the expansion next.
Doom 3 is still fun, very replayable unlike some other game from the same year...

File: Alien Breed: Impact | 202(...).png (2.55 MB, 1920x1200)

2.55 MB PNG

It's a bit obnoxious how the background animation of the menu/pause screen works my GPU harder than the game itself with post-processing disabled.

File: Alien Breed: Impact | 202(...).png (2.73 MB, 1920x1200)

2.73 MB PNG

I'm not a fan of this game's camera system, but it looks all right even if it feels like shit.
Not entirely related but being able to see the planet outside the ship is pretty cool too.

>>557428796
You got it. I personally couldn't care less, but it's nice for people who want it.

>>557410343
I'm going to be completely honest, lutris died for me when they started hard depending on that umu crap. I bypass the Steam runtime and use system libraries for a reason.

does any one of you guys know how to play manhunt on linux? I can't do it for the life of me

>>557448370
I've never tried the game, but it seems I have it in my Steam library (though I don't remember when I got it). I could try it later tonight. But I'm probably just going to start off with whatever tweaks are recommended on ProtonDB which you can go see for yourself if you haven't already:
https://www.protondb.com/app/12130
At a glance, it looks like a real bitch to run. The latest report intrigues me, with its editing of the executable. I don't really understand exactly what that command does in detail, but the alternative seems to be downloading a fixed version from somewhere other than Steam, which seems riskier than what looks like a command to insert some null bytes into the .exe file.

>>557448370
This game will not boot on modern operating system because of Razor1911 leaving a hidden signature in the exe file.

This was fixed by the community, make sure to grab fixes from https://www.pcgamingwiki.com/wiki/Manhunt

>>557449741
>could try it later tonight
Good news: It's later tonight.
I haven't started downloading it yet though.

>>557443442
Man I really need to replay this, original or bfg edition?

File: MANHUNT | 2026-02-14 22-5(...).png (2.6 MB, 1920x1200)

2.6 MB PNG

>>557468364
Rather than following the latest ProtonDB report to the letter (which includes using Proton 9.0-4), I kept the game on my default compatibility tool which is Proton 10.0-4. (I tend to use the latest "stable" i.e. numbered version and I think that's it.) I tried launching the game "out of the box" just for good measure, but knowing that:
>several reports recommend Wine DLL overrides for d3d8 and ddraw
>several reports recommend renaming some included testapp.exe to replace the included manhunt.exe
>several reports recommend some "Manhunt Fixer" patch (this and the file renaming might be mutually exclusive)
>that latest report recommends not only renaming testapp.exe to manhunt.exe but also modifying the executable to disable anti-piracy measures which break saves (which is extra annoying because I won't really know if I need this until I run into whatever issue "breaks saves" is describing)
Anyway, just running the game with no changes brought up a launcher window in which I selected my native resolution as the screen mode... and from there, I was able to launch the game, and get as far as the main menu... and from there, I hit "play" and clicked through the brightness setting screen and selected a difficulty mode and started a save file... and then watched a cutscene, and started the gameplay...
Uh, isn't the game supposed to be way more broken than this? Yes, I know that the anti-piracy measures will break saves according to the latest ProtonDB report, but I literally did nothing here except launch the game -- no Wine DLL overrides, and no executable renaming. I guess I'll play for a bit and see where it stops working.
Obviously this is 4:3 stretched to 16:10 so I'll want a widescreen patch, but the game isn't crashing or anything. Did recent Proton updates fix the issue described by the "out of the box it just crashes" report for Proton 9.0-4 from 8 months ago?

File: MANHUNT | 2026-02-14 22-5(...).png (2.49 MB, 1920x1200)

2.49 MB PNG

>>557470130
Well, it crashed during gameplay, specifically while I was picking up and then putting down a body. Attached screenshot of execution cutscene unrelated.
So I guess there's some instability, at least. Still better than "doesn't run at all" which is what I assumed would be the out-of-the-box experience. Again I haven't done any tinkering yet.

File: MANHUNT | 2026-02-14 23-2(...).png (2.56 MB, 1920x1200)

2.56 MB PNG

>>557471190
Crashed in the same area again. So maybe this crash IS the anti-piracy fuckery that needs to be fixed by renaming and/or modifying executables. I guess I'll try using testapp.exe instead, but rather than renaming files, maybe I can just put this in the launch options to make Steam run testapp.exe directly:
>bash -c 'exec "${@/manhunt.exe/testapp.exe}"' -- %command%
Trying that now...

File: MANHUNT | 2026-02-14 23-2(...).png (2.5 MB, 1920x1200)

2.5 MB PNG

>>557472441
Yup. With the launch options replacing "manhunt.exe" with "testapp.exe" in the game's run command, I got past the gate in the previous screenshot (which, in addition to the crash that happened near there, wasn't opening before -- which is likely a broken anti-piracy thing, now circumvented by using the other executable which has no anti-piracy measures or something).
After a fight tutorial, I saved before quitting, so we'll see if I can load the save. That latest ProtonDB report had some note about the anti-piracy breaking saves, and it fixed it by not only using (by renaming) but also modifying the alternative executable...?
I'm a little confused by what exactly these tweaks are supposed to do. So I went to PC Gaming Wiki which has a LOT of shit about this game. Here's one note about the Manhunt Fixer patch, which I'm not using but the bulk of this is still relevant:
>Manhunt Fixer makes the game run through testapp.exe by renaming it to manhunt.exe to fix these issues since it bypasses the anti-piracy measures. However, the renamed executable may cause the game to refuse to launch due to Data Execution Prevention (DEP) being triggered since it's a literal crack of the game that rockstar put into the legitimate version of the game. This was reportedly fixed on Windows when using the steam version of the game, however this issue may still be present; (DEP is a part of Windows anti-virus protection).
Okay, so I'm using testapp.exe and thus bypassing the anti-piracy measures, and the remaining issue is that testapp.exe is an actual pirate copy which triggers anti-virus shit? Is the
>printf "\x00" | dd of=manhunt.exe bs=1 seek=2270 count=2 conv=notrunc
in the ProtonDB report (where manhunt.exe is the renamed testapp.exe) meant to remove the part that the anti-virus doesn't like?
Anyway... it seems to be working for me just by using the cracked (lmao) executable.

File: MANHUNT | 2026-02-14 23-4(...).png (2.21 MB, 1920x1200)

2.21 MB PNG

Well I was able to load the save with no problem. Here's me fucking up at stealth.
So I guess the game works just by making Steam run the cracked executable, which apparently doesn't work for others because of anti-virus stuff (and I assume that's what >>557450586 meant but I don't know what security thing on Linux would actually search for some warez group's signature and prevent this from running).
If there are minor graphics bugs (e.g. maybe this film grain effect isn't supposed to look so ass), then I don't know because have no frame of reference, having never played the game before. But as far as being able to run it, I don't see the big deal. Sorry >>557448370 if you had more trouble than this.

>>557474686
thanks for your help! I'll try playing it again now :) I remember my game crashed a lot, especially in the area with gate on this screenshot >>557473924

>>557475167
I don't know what other issues might crop up later, or might happen on different hardware or whatever. There are apparently multiple issues, and I have no idea how to guess which of them are
>simply not an issue on Linux
>not an issue anymore with the latest Proton
>already fixed by game patches (e.g. see the "reportedly fixed" in that PCGW quote)
etc., and I still don't know what the Wine DLL overrides for d3d8 and ddraw all over the ProtonDB reports are supposed to fix. I apparently didn't need them unless I just haven't noticed what they fix.

>>557475167
Also, simply doing the file renaming like
>mv manhunt.exe renamed.exe
>mv testapp.exe manhunt.exe
is probably sufficient to get Steam to use the other executable, despite my preference to use the arcane launch options in >>557472441. I just wanted to leave the game files as unmodified as possible.

File: Screenshot from 2026-02-1(...).png (44 KB, 746x572)

44 KB PNG

Oh, I see. The "Manhunt Fixer" patch includes a d3d8 wrapper. That would probably explain the Wine DLL overrides for d3d8 in the ProtonDB reports. And any ProtonDB reports that recommend overriding d3d8 despite not using the patch are probably just "monkey see, monkey do".
I'm not sure about the ddraw override but maybe it's also included in this or some other patch which I'm too lazy to install right now.
The game doesn't contain any ddraw.dll or d3d8.dll out of the box, so I'm pretty sure the overrides wouldn't make sense unless these files are being added by something.

File: Screenshot from 2026-02-1(...).png (63 KB, 755x747)

63 KB PNG

Manhunt Fixer might be worth using if the audio glitches happen on Linux. I wasn't paying much attention to the audio so I can't say if I already encountered any.
As for the "AI bugging out", it looks like this is a high-frame-rate issue caused by Vsync for old games being broken on modern Windows, but I don't think the game was actually exceeding 60 FPS for me. This might not be an issue on Linux.

File: MANHUNT | 2026-02-15 00-2(...).png (2.27 MB, 1920x1200)

2.27 MB PNG

Steam's frame rate display shows it's running at 60 fps, so the broken-Vsync/high-frame-rate issues and resulting AI bugs are probably not a thing in Proton.

>>557448309
>lutris died for me when they started hard depending on that umu crap. I bypass the Steam runtime and use system libraries for a reason.
There's UMU_NO_RUNTIME environment variable and proton-cachyos already running without runtime (giving it installed on CachyOS since CachyOS ships patched umu that allows proton-cachyos to run without a runtime).

>re-post my post to fix a mistake
>pick up extra (You)s from references to my own post because of the copy-paste
>have to re-post again
I apologize for shitting up the archive but at least 4chan isn't refusing to let me delete my posts today.
One more note about Manhunt for >>557448370 >>557475167:
I tried and failed to find any other documentation of that latest ProtonDB report's claim that one should run
>printf "\x00" | dd of=manhunt.exe bs=1 seek=2270 count=2 conv=notrunc
after renaming testapp.exe to manhunt.exe, so I still don't know exactly what effect it has or why I need it. (To be clear, I didn't run that command before the testing done above; I only told Steam to run testapp.exe via launch options.) The report says the command "rewrites the executable so that anti-piracy measures are always disabled" but I thought disabling the anti-piracy was the whole point of renaming testapp.exe (supposedly a cracked pirate copy) to manhunt.exe in the first place, so what the frick.
Anyway, running what is supposedly a warez group's cracked executable seems a bit sketchy even if Rockstar thought it was good enough to pass off as their own, and that ProtonDB report's further modification of the cracked executable implies there's something still subtly wrong with it (with no clue what that might be), so I wanted to try another fix.
There is a patch which apparently circumvents the anti-piracy measures in the original executable:
>https://github.com/Fire-Head/MHNoDRM
So I removed the launch options given in >>557472441 (thus setting the game back to its normal state), downloaded "MHNoDRM.asi" from that GitHub repo, and dropped that file into the game folder. This appears to be working, as it fixes the crash and locked gate at >>557472441 without any need for switching executables, which is nice. And I reckon this patch is at least as trustworthy as a cracked executable distributed by a lazy publisher.

>>557481513
>>https://github.com/Fire-Head/MHNoDRM
Works only for the Steam version though.
Other anon didn't say which version he has.

File: 1741611319099469.webm (3.93 MB, 1920x1080)

3.93 MB WEBM

Let me handle this

File: 1742968358708089.webm (3.87 MB, 1920x1080)

3.87 MB WEBM

That was a nice three-pointer

>>557468397
Original with dhewm source port.

File: 1758467303299756.webm (3.9 MB, 1920x1080)

3.9 MB WEBM

WTf, who would design to access stash this way?

I remember playing Eduke32 at work on a Windows PC with 1440p 60 Hz monitor and Nvidia card, and it felt like having an input lag at fullscreen without vsync. But when I connected same monitor to a CachyOS PC with even older Nvidia card everything was fast and smooth even on Wayland and without direct scanout (I guess direct scanout doesn't work on proprietary Nvidia drivers). How could this happen? Aren't we supposed to have higher input lag from forced Vsync on Wayland?

File: 1751340139144675.webm (3.87 MB, 1920x1080)

3.87 MB WEBM

>>557491390
>>557491567
>>557491713
Wow, what fucking niggers. No matter, I'll just post my webms again.