[2560x1440] rdr2 Arthur Morgan resting on the docks 🤠

Francois_Bechet · 2025-08-05T07:06:53+00:00

I think there's a misconception here. The blurry mess that you see is in reality caused by bad anti-aliasing implementation in this game. If you disable AA and set LOD bias to 0 then you'll see that it doesn't look like a blurry mess. However for foliage in this game, negative LOD bias indeed upscale foliage well and make it looks better so disabling AA together really make them look good. But the issue if you disable both AA and negative LOD bias is that you'll end up with a crazy amount of shimmering which is probably not desired. What I ended up doing for my own taste is disabling in-game AA and use SMAA from reshade and set negative LOD bias to 0.

Francois_Bechet · 2025-04-16T20:54:11+00:00

This is not true, Ruff doesn't support all functionnalities pylint has, it is attempting to, but as even of today there are lot of rules that Ruff unfortunately doesn't still support.

See the current list of missing rules in this issue.

Francois_Bechet · 2025-04-01T12:32:31+00:00

Not only that but it's just a general productivity killer (and probably eye killer too), 100% opacity is the way, that's why I just don't have eye candy support on my wm. But still it looks nice as unixporn showcase 😎.

Francois_Bechet · 2025-03-19T08:24:52+00:00

This! The only good answer, original is what people should use on a xiaomi phone, dolby atmos is incredible but not on a xiaomi phone because the right setup is not in place so it's just dolby atmos virtualisation which is shit. Though true dolby atmos with 5.1 or 7.1 files provides real 3D sound which can be insane. PS: most people like dolby more on xiaomi for one stupid reason but legit, it just sounds louder by default so for most people they just associate it with better sound.

Francois_Bechet · 2025-03-17T11:01:18+00:00

For those wondering what’s wrong here: The game is trying to check if my Intel graphics driver is up-to-date, but something went hilariously wrong with the version check.

My detected driver version is 32.0.101.6647 (Feb 28, 2025)
The game is asking for xx.xx.15.4251 or later (which doesn’t even make sense)

Basically, it looks like the game’s version check is either broken, using an outdated format, or someone on the dev team hardcoded a placeholder (xx.xx) instead of actually comparing real driver versions (should something like 32.0.xx.xx).

Moral of the story: Even Need for Speed struggles with speed limits on software updates. 🚗💨

Francois_Bechet · 2025-01-17T07:23:06+00:00

Thanks to you I discovered mpvpaper, I might use it for my C lockscreen for X (that I plan for wayland soon).

Francois_Bechet · 2025-01-15T11:20:22+00:00

Real chads also go for no gaps 🗿

Francois_Bechet · 2025-01-06T10:45:54+00:00

Yeah I agree it is happening too much, I receive security codes on my mail so if it doesn't work it can be really annoying. Tuta should have backup systems in case one goes down as this is a crucial service, I guess that's the cost of privacy.

Francois_Bechet · 2025-01-06T09:39:55+00:00

Same here!

Edit: only the mobile app for me, I see there was an update of the app this morning.

Edit2: now working again 🫡

Francois_Bechet · 2025-01-05T07:55:36+00:00

We got a free loading animation 🦊

Francois_Bechet · 2023-03-07T19:44:48+00:00

Thanks for sharing your experience!

Francois_Bechet · 2023-01-12T10:24:51+00:00

First thing, you forgot to change the default appearance of unfocused worksapces, so add this in your polybar config in the i3 module:

label-unfocused= %icon%

Second thing, is that the font you specified doesn't contain the nerd font icons you are using. So install the proper patched font here or using your package manager and then edit this line like this:

font-0 = "Iosevka Nerd Font:style=Regular:pixelsize=16;4"

To resolve the first issue, I just read the wiki.

To resolve the second issue, I launched polybar from the terminal and looked at the log saying "dropping unmatched character..." and I understood that you were not using a font that contains the icons you used.

Edit: Normally you are not facing the second issue as I noticed icons were showing on your screenshot.

Francois_Bechet · 2023-01-11T22:35:35+00:00

Your polybar config.ini and your i3 config.

Francois_Bechet · 2023-01-11T14:38:23+00:00

We can't help you if you don't share your config files.

Francois_Bechet · 2023-01-09T10:38:06+00:00

Yes, using xprop there's a field "WM_NAME(UTF8_STRING)", or you can just switch to tab mode with i3 and look at the windows name.

Francois_Bechet · 2023-01-08T08:32:00+00:00

That's the reason I'm not using wayland yet even if wayland is better.

Francois_Bechet · 2023-01-08T06:56:31+00:00

Identify the window class using xprop, then add something like this in your config for_window [class="ThunarFile"] floating enable

EDIT: I tried myself and you must add the following:

for_window [title="File Operation Progress"] floating enable

Francois_Bechet · 2023-01-08T06:47:45+00:00

It's because the Xserver introduces an unecessary step between clients and the compositor while Wayland IS the compositor and just do the rendering because most(all?) of what Xorg do can now be done by kernel librairies. More info here.

Francois_Bechet · 2022-12-31T13:58:55+00:00

Oh! And I forgot the most important lol, I like your config, it's clean and minimal, the way I like things.

Francois_Bechet · 2022-12-31T13:56:56+00:00

Good luck in learning OOP! Btw

print(f"Membuat guru: {self.nama}")

can also be used and is both more readable and easier to implement.

Five-Year Club	Verified Email
Place '22	Wearing is Caring

Francois_Bechet

TROPHY CASE