As an anti-aliasing nerd it's sad to say but there is really is only one* good choice left: Just use DLSS

(* and if you aren't on nvidia then sucks to be you, FSR for you I guess)

Just started playing Rust again after like 9 years and holy shit is this game not noob friendly at all

I play(ed) on a relatively chill server where raiding is only enabled in the last week before wipe every month and it's not too many people playing

So I'm out on adventure, I come back and my entire base is raided... Uhm okay, I did sort of have an uneasy feeling that I left the door open when I left so okay, my dumb mistake. Lesson learned: Always make sure doors are definitely closed

So I farmed hours more to get all my stuff back, repaired a vehicle, built a nice little garage, upgraded all my windows to reinforced windows so that nobody can interact with the car or my horse inside the house, just in case that allows you mount and get in the house that way, no clue

This day I log back in. Base completely cleaned the fuck out again

Actually what the fuck man. I did *everything* right, made sure every door is locked and closed, replaced all accessible windows with reinforced ones, had 27 days of upkeep materials and still, my entire progress of 10 hours of playing is gone again

What did I do wrong? After talking with people in chat apparently I had wooden frames for the doors, which apparently are just always destroyable by anyone... Even on a damn server where raiding is disabled. Yea sure makes sense

I like Rust but holy shit, this core game mechanic of raiding is still one I cannot get over. It's so stupid to be cleaned out over night while you're not even online. It's just fucking frustrating to start all over AGAIN farming and farming and farming. I didn't really want to play because the game always looked like a meta gaming sweat fest and this just proves that it's exactly that. You have to know every single meta game mechanic to even have your damn base survive overnight

On a positive note I did figure out that unity's concurrent garbage collection doesn't seem to be a big problem for a proper fps game though, so that's something

The entire GNOME project including gtk is the biggest pile of shit that has ever existed

People hate Amazon, people like to hate on Amazon.
But people also keep buying from Amazon

This morning I took an amazon return package to DHL and literally at 17:00 this day (the same day!) I got the refund to my bank account

What the fuck. I mean yeah I hate amazon as much as the next guy. But that's literally why people are buying from amazon. You can't just say "amazon bad" and then not also appreciate when they are doing something good

Uhhmm... pretty sure this shouldn't look like this

Canonical programming language waifu tier list

HLSL, you little fucker

The bug I was searching for, for a few days now turns out to be a packed uint accidentally stored into a float variable

Not a single peep from the compiler, nothing

It doesn't even have warning flags like -Wconversion

What the fuck. Why microsoft. WHYYY

Some logic I'm developing packs three different states into an f32: NaN means do nothing, +0.0 or positive number means polite request and -0.0 or negative number means force override

Yeah, I don't know what to say...

Let it be known that the smell of mediocre pizza and döner at the same time is something to marvel at. It really smells very good

I don't get it. Bethesda managed to make the best temporal antialiasing solution to ever grace this planet with TSSAA in Doom 2016 and then manage to fuck it up by removing it in favor of forced TAA in Doom Eternal which looks like complete dogshit

WHYYYYYYYY

The graphics were /literally/ the reason I bought the damn game. I just finished Doom 2016 and it was so inspirational for my own game engine, giving me motivation by seen what I can achieve. Doom Eternal is fucking depressing from a technical standpoint

Well at least I know now that my own AA solution is viable and that I can do better than a AAA studio :emotionless-shrug-guy:

Oh wow, fuck Ansible

Turns out there is no way to automatically undo the things it did, because surely nobody would ever want to remove software...

Now I have a half fucked server that I can manually clean up again 👍

Oh my god, GDScript is the single biggest piece of shit scripting language I have ever witnessed. It somehow manages to combine the very worst things of dynamic typing with the downsides of static typing, all in one bundle of utter shit

Imagine you have two game object scripts that want to reference each other, e.g. by calling each others methods.

Well you're outta fucking luck because scripts CANNOT have cyclic references. Not even fucking *type hints* can be cyclic between scripts. Okay no problem, since GDScript is loosely based of Python I can surely just call my method out of the blue without type hints and have it look it up by name. Nope! Not even with the inefficient as fuck `call` method that does a completely dynamic-at-runtime fuck-compile-time-we-script-in-this-bitch function call can find the function. Why? Because the variable that holds a reference to my other script is assumed to be of type Node. The very base class of everything

So not only is the optional typing colossal garbage. You cant even do a fucking dynamic function call because this piece of shit is just C++ in Pyhtons clothing. And nothing against C++ (first time I said that). At least c++ lets me call a fucking function

Does anyone have experience with using Kotlin as a front end language? Seems to have excellent JS interop and I really don't want to deal with the garbage fire that is JS or TS 😬

Trying to get ChatGPT to say inappropriate things is like talking to a fucking twitter user, having to reassure everybody every other sentence that no hypothetical people are being offended and that everything is fine

Mom, pick me up im scared

TIL vanilla Java has the facilities to do (some form) of arbitrary compile time metaprogramming via annotation processors

When your naked sister turns up in a dream that's normally not a good sign

This the place where you get robbed of your organs

Okay maybe that one shader variable was important after all...

Least complex rust type signature

Oh boy I have to interact with some C++ library code again, please kill me now

I was just hit by this wave of depression. I don't even know why to be honest, but somehow it feels like things aren't going how they should

This sucks man

My imperative dumb ass me trying to code in ocaml:
👁👄👁

Some people say linux is better than windows because it's better suited for development work

Let's be honest: It's not linux, the tools just suck ass

And no I'm totally not frustrated with installing ocaml on windows 🤐

In vulkan we don't say it works we say

VUID-vkAcquireNextImageKHR-fence-01287(ERROR / SPEC): msgNum: 207921847 - Validation Error: [ VUID-vkAcquireNextImageKHR-fence-01287 ] Object 0: handle = 0xe7e6d0000000000f, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0xc64a2b7 | vkAcquireNextImageKHR(): VkFence 0xe7e6d0000000000f[] is already in use by another submission. The Vulkan spec states: If fence is not VK_NULL_HANDLE it must be unsignaled and must not be associated with any other queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/...)
Objects: 1
[0] 0xe7e6d0000000000f, type: 7, name: NULL
VUID-vkAcquireNextImageKHR-swapchain-01802(ERROR / SPEC): msgNum: 1050126472 - Validation Error: [ VUID-vkAcquireNextImageKHR-swapchain-01802 ] Object 0: handle = 0xcb3ee80000000007, type = VK_OBJECT_TYPE_SWAPCHAIN_KHR; | MessageID = 0x3e97a888 | vkAcquireNextImageKHR: Application has already previously acquired 1 image from swapchain. Only 1 is available to be acquired using a timeout of UINT64_MAX (given the swapchain has 2, and VkSurfaceCapabilitiesKHR::minImageCount is 2). The Vulkan spec states: If the number of currently acquired images is greater than the difference between the number of images in swapchain and the value of VkSurfaceCapabilitiesKHR::minImageCount as returned by a call to vkGetPhysicalDeviceSurfaceCapabilities2KHR with the surface used to create swapchain, timeout must not be UINT64_MAX (https://vulkan.lunarg.com/doc/view/...)
Objects: 1
[0] 0xcb3ee80000000007, type: 1000001000, name: NULL

and I think that's beautiful

Writing an efficient, modern renderer is truly an exercise of patience. You have a good idea? Hah, fuck you, GPUs don't support that. Okay but what if I try to use this advanced feature? Eh, probably not going to support exactly what you would like to do. Okay fuck it I'm gonna use the most obscure features possible. Congratulations, it doesn't work even on the niche hardware that supports that extension

If I sound jaded, ya better believe I f*cking am! I cannot wait for more graphics cards to support features like mesh shaders so we can finally compute shader all the things and do things the way we want to god dammit

Just finished a little proof of concept of a reprojected multisample antialiasing technique and daaaaamn it's looking good. First time ever a rendering technique I invented isn't complete shit so that's an improvement

It still has some (pretty big) issues with both spatial and temporal ghosting but I have some ideas in the pipeline

I wish I could show you guys comparison images but as it turns out most anti aliasing techniques look pretty good on still frames but only the good ones stand up under motion and I don't know of a good way right now to capture pixel perfect clips like that

Software is such an awe inspiring concept if you really think about it. We literally create our own reality from scratch. Binary for the wrong architecture? Don't worry we can emulate it. Network? Fully software defined. Heck, the servers don't even know if it's real or all in software. You know what? Fuck it! The machine isn't real either! All virtualized or software emulated

I'm really bad at putting things into words but the idea of software truly amazes me

Still having problems with samba doing weird shit. Now looking through the logs and

Hm... *that* doesn't seem right 🤔

Why do SAMBA network drives have to suck this much? Yeah I understand that compiling to a network drive is probably a bad idea just for performance reasons alone but can't you at least not fuck with my git repo?

$ git gc
Enumerating objects: 330, done.
Counting objects: 100% (330/330), done.
Delta compression using up to 24 threads
Compressing objects: 100% (165/165), done.
Writing objects: 100% (330/330), done.
Total 330 (delta 177), reused 281 (delta 151), pack-reused 0
error: unable to open .git/objects/7e: Not a directory
error: unable to open .git/objects/7e: Not a directory
fatal: unable to mark recent objects
fatal: failed to run prune

$ git gc
error: unable to open .git/objects/00: Not a directory
fatal: unable to add recent objects
fatal: failed to run repack

$ git gc
Enumerating objects: 330, done.
Counting objects: 100% (330/330), done.
Delta compression using up to 24 threads
Compressing objects: 100% (139/139), done.
Writing objects: 100% (330/330), done.
Total 330 (delta 177), reused 330 (delta 177), pack-reused 0
Removing duplicate objects: 100% (256/256), done.
error: unable to open .git/objects/05: Not a directory
error: unable to open .git/objects/05: Not a directory