• 3 Posts
  • 27 Comments
Joined 3 years ago
cake
Cake day: January 31st, 2022

help-circle
  • Based on the content of the linked post and the evolution of the thread here, the mod team has decided to lock this post. There is an important difference between standing up for people who are marginalized and harassment, which this thread has been more or less equating. Please deal with this topic in a more nuanced manner going forward.





  • I am not an expert and just cobbled this together based on a couple of searches but my guess would be that the adapter is supported by your current kernel drivers but not as well as whatever drivers Windows 10 was able to fetch. It looks to me like MX uses Debian Stable sources, so you may be able to update your kernel beyond what is normally available and see if that helps. If that doesn’t work, based on this post and this post on the TP-Link forums, there’s a github repo that you may be able to install a better driver from. To my eyes there’s fairly good instructions there, including the potential need to disable the driver you’re already using in favor of the new one once you build it.



  • gyrfalcon@beehaw.orgtoLinux@lemmy.mlLooking for a "couch laptop"
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    I bought a used HP Elitebook on eBay for a similar purpose. I can browse and do video calls on a bigger screen when the fancy strikes. Pretty much any used business laptop should work. I think I paid about $300 for mine and I paid extra for particular hardware I thought was neat but you don’t have to. Only thing to keep in mind is the battery will likely be pretty worn.




  • gyrfalcon@beehaw.orgMtoTechnology@beehaw.orgFucking hell
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    Hey this is a great contribution, just wanted to request that in the future you try to have a more descriptive title. Totally understand that it might have slipped your mind on this one, this is a charged topic to say the least, just a note for the future. Thanks!


  • Hey, I know this can be an issue that strikes a nerve. That said, acknowledging nuance is important to having a productive conversation. Judging everyone by a set standard and having unkind words for not meeting that standard even before you know much about the person you are engaging with is not going to be productive, and it’s not particularly nice either.

    To be clear, I do not intend to ask you to tolerate oppression. By all means you should oppose oppression strenuously! But being harsh to someone you disagree with online is not the way to do that. In the future, please try your best to disengage from the conversation for a bit until you are in a better headspace.












  • Not a game dev but I’ve done some programming and I love games so I’ll take a stab. There’s a few reasons I can think of:

    1. That’s how the engine they’re using works. Game engines take a long time to develop, and so if you’re using one off the shelf or from a previous project, it may be from a time when tying behavior to the frame rate was a low overhead tool for timing that would cause few if any issues. Given that Wolfenstein is a Bethesda title and they’ve made many games with similar engine level limitations, this seems most likely to me for this particular case.
    2. They never intended to release it that way, and just set it up that way early in development to start getting to the real gameplay work. Then the deadline came around and it wasn’t a high priority in terms of getting the game out the door.
    3. Probably doesn’t apply to Wolfenstein, but for indie games that have one or only a few developers, none of those people may have done much programming before, instead being more focused on other aspects of game design. So if you’re learning as you go, there’s a good chance some hacky things will make it in to the final product.