Currently studying CS and some other stuff. Best known for previously being top 50 (OCE) in LoL, expert RoN modder, and creator of RoN:EE’s community patch (CBP).

(header photo by Brian Maffitt)

  • 25 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle

  • MHLoppy@fedia.iotoGreentext@sh.itjust.worksAnon downloads free fps
    link
    fedilink
    arrow-up
    32
    arrow-down
    1
    ·
    14 hours ago

    I’ve come across this utility before - using it seems to add input latency according to the reviews it has on Steam. So using it to increase performance isn’t really better than not using it, it’s just a tradeoff.

    If you’re not sensitive to input latency then that’s likely going to be a good tradeoff for you, but if you are (or play competitively) it’s not.








  • I feel like your preference makes sense when aligned from the perspective of a conventional forum-like platform. However I’d argue that that’s missing a core part of what kbin is/was – and by extension what Mbin is – which is the microblog integration alongside the forum-like stuff. With that context in mind, boosts (or whatever term you want to use for “retweet”) make sense to integrate imo.

    Whether or not you think Mbin should try to integrate the microblog side of things is of course a subjective - I personally think it’s a cool idea to try at least, but with how dominant lemmy has become it can be difficult to reconcile differences and incompatibilities between it and other software like Mbin.







  • Thanks for so politely and cordially sharing that information


    edit: I would be even more appreciative if it were true: https://www.rockpapershotgun.com/rocket-league-ending-mac-and-linux-support-because-they-represent-less-than-0-3-of-active-players

    Quoting their statement:

    Regarding our decision to end support for macOS and Linux:

    Rocket League is an evolving game, and part of that evolution is keeping our game client up to date with modern features. As part of that evolution, we’ll be updating our Windows version from 32-bit to 64-bit later this year, as well as updating to DirectX 11 from DirectX 9.

    There are multiple reasons for this change, but the primary one is that there are new types of content and features we’d like to develop, but cannot support on DirectX 9. This means when we fully release DX11 on Windows, we’ll no longer support DX9 as it will be incompatible with future content.

    Unfortunately, our macOS and Linux native clients depend on our DX9 implementation for their OpenGL renderer to function. When we stop supporting DX9, those clients stop working. To keep these versions functional, we would need to invest significant additional time and resources in a replacement rendering pipeline such as Metal on macOS or Vulkan/OpenGL4 on Linux. We’d also need to invest perpetual support to ensure new content and releases work as intended on those replacement pipelines.

    The number of active players on macOS and Linux combined represents less than 0.3% of our active player base. Given that, we cannot justify the additional and ongoing investment in developing native clients for those platforms, especially when viable workarounds exist like Bootcamp or Wine to keep those users playing.