• 0 Posts
  • 36 Comments
Joined 2 months ago
cake
Cake day: May 5th, 2024

help-circle
  • Dealing with proton shenanigans is much easier than dealing with all of Windows and Microsoft’s bullshit.

    The windows “desktop environment” is so slow and clunky. It makes game development or really any workflow requiring the use of multiple open directories almost too hard. It makes me wonder how they even develop this piece of shit at Microsoft HQ. Do they have an in-house developers ui that’s maybe a little more efficient? Do they have special accelerated hardware that makes it run faster than fast on the development machines? I guess the windows server ui is faster than the windows 11 ui and maybe it has a better file explorer so maybe that’s what they use.

    When you need to install a program, all the choices available are too spammy and corporate. The hp printer driver is 300mb and takes 15 minutes to install on a ssd on Windows. Meanwhile on Linux you type something like “sudo apt install cups” and 15 seconds later you have printer drivers.

    It’s pretty easy to identify the sweaty mlg titles that lock down everything with windows-only anticheat before buying them. Beyond anticheat games, I can’t even recall a game I couldn’t get running.





  • I’m a die hard Microsoft hater. I haven’t had windows installed on a pc in years. With that being said I use visual studio code because it’s kind of the only text editor that does code completion in the capacity that it does. I can take a class name, type a “.” after it and a scroll view opens up shows every accessible member of that class along with comments and information about all the variables. The amount of time this saves is so huge I don’t even know how you would quantify it. Nothing else has code completion that even comes close to being that good.

    Do non visual studio code users just have to memorize every single function, parameter and return type in their code base? Yeah you can always read the documentation, sure you can always dig through the source code to figure it out every time you forget what data type a parameter is but that takes valuable time.

    If they ever put visual studio code behind a paywall or stop making it for Linux, I’m going to be forced to either switch to windows (which I never will under any circumstances) or make a custom made ripoff clone of that entire intellisense code completion system and hack it into whichever open source text editor I deem is the next best thing.





  • Another part of it is the gpu bios. The gpu bios contains x86 opcodes that it expects the host system to run for gpu-specific functions like video mode switching and probably lots of other stuff. I know that Vesa bios extensions mode switching requires a pointer to the functions in the gpu bios which the cpu runs. I tried to make a platform independent Vesa driver one time and couldn’t figure out how to circumvent using the gpu bios for it since the functions you’re supposed to call are compiled for x86. Even the well-refined projects like Seabios still rely on the VBE pointers for non-legacy video modes.

    Legacy vga does also has a bios but it’s relatively not that difficult to circumvent using the bios on legacy vga cards, only issue is that legacy vga modes are mostly useless.

    I think there’s a newish way of doing this stuff that doesn’t involve Vesa or legacy vga but I don’t know what it is. This I’m sure is only one of the many problems that have to be overcome if someone wanted to hack a 1080ti onto a raspberry pi or something.











  • I’ve never used Lutris but I know cs4 can work in wine, I’ve done it before. (I use Gimp now before anyone points out that I should be using Gimp instead). The method I’ve found for manually getting random wine stuff to work is as follows:

    Step 1. Get winetricks and figure out how wineprefixes work.

    Step 2. Scroll through the winetricks dll menu, make an educated guess on what library to try installing and install it. Direct x and netframework are often the first things I try but c++ runtimes are important too.

    Step 3. Try the program after installing the thing you guessed it needed. If it works better than before, go back to step 2 and repeated until the program works correctly. If its borked so badly it doesn’t even start, delete the wineprefix, go back to step 2 and pick different dlls.

    Pro-tip: test your program by running it in a terminal instead of double clicking an icon. Sometimes when it crashes, it leaves behind useful information such as “error: missing mscorefonfs” or whatever in which case you should see if the thing it’s complaining about is in your winetricks dll menu.