Comment on Star Wars: Battlefront Classic Collection used modder's work without credit

starman2112@sh.itjust.works ⁨7⁩ ⁨months⁩ ago

• catloaf@lemm.ee ⁨7⁩ ⁨months⁩ ago

  It’s not a question of capability. It’s a question of cost-benefit spending developer time on a feature not many people would use.

  Couch coop was a thing because there was no way for you to play from your own homes. Nowadays it’s a nice-to-have, because you can jump online any time and play together, anywhere in the world, without organizing everyone to show up at one house.

  source

  • chiliedogg@lemmy.world ⁨7⁩ ⁨months⁩ ago

    It also requires multiple copies of the game.

    source
  • ICastFist@programming.dev ⁨7⁩ ⁨months⁩ ago

    It’s a question of cost-benefit spending developer time on a feature not many people would use

    Which is super ironic when you look at games that had an obviously tacked-on, rushed multiplayer component in the first place, such as Spec Ops: The Line, Bioshock 2 and Mass Effect 3

    source

    • Piemanding@sh.itjust.works ⁨7⁩ ⁨months⁩ ago

      Goldeneye 007. Yeah seriously. The most famous multiplayer game of its generation very nearly didn’t have multiplayer. It was tacked on when they finished the game and had a little bit of extra time and ROM storage.

      source
• ipkpjersi@lemmy.ml ⁨7⁩ ⁨months⁩ ago

  Modern hardware is wasted on modern devs. Can we send them back in time to learn how to optimize, and bring back the ones that knew how to properly utilize hardware?

  I think a lot of the blame is erroneously placed on devs, or it’s used as a colloquialism. Anyone who has worked in a corporate environment as a developer knows that the developers are not the ones making the decisions. You really think that developers want to create a game that is bad, to have their name attached to something that is bad and to also know that they created something that is bad? No, developers want to make a good game, but time constraints and horrible management prioritizing the wrong things (mostly, microtransactions, monetizing the hell out of games, etc) results in bad games being created. Also, game development is more complex, hardware is more complex, and developers are expected to produce results in less time than ever before - it’s not exactly easy, either.

  It’s a pet peeve of mine and I’m sure you meant no harm by it, but as a developer (and as someone who has done game development on the side and knows a lot about the game development industry), it’s something that bothers me when people blame bad games solely on devs, and not on the management who made decisions which ended up with games in a bad state.

  With that said, I agree with your sentiments about modern hardware not being able to take advantage of long-forgotten cool features like four-screen splitscreen, offline modes (mostly in online games), arcade modes, etc. I really wish these features were prioritized.

  source

  • almar_quigley@lemmy.world ⁨7⁩ ⁨months⁩ ago

    I agree with you on this point. I think”devs” is conflated for the developing company and its management and not individual devs.

    source
• barsoap@lemm.ee ⁨7⁩ ⁨months⁩ ago

  4x splitscreen needs approximately 4x VRAM with modern approaches to graphics: If you’re looking at something sufficiently different than another player there’s going to be nearly zero data in common between them, and you need VRAM for both sets. You go ahead and make a game run in 1/4th of its original budget.

  source

  • starman2112@sh.itjust.works ⁨7⁩ ⁨months⁩ ago

    I can’t do that, but you know who could? The people who originally made the game. Had they simply re-released the game that they already made, it wouldn’t be an issue.

    source

    • barsoap@lemm.ee ⁨7⁩ ⁨months⁩ ago

      I can’t do that, but you know who could? The people who originally made the game.

      How to tell me you’re not a gamedev without telling me you’re not a gamedev. You don’t just turn a knob and the game uses less VRAM, a 4x budget difference is a completely new pipeline, including assets.

      Low poly models with textures that quadruple the game’s size are the worst possible middle ground.

      Speaking about redoing mesh assets. Textures are easy, especially if they already exist in a higher resolution which will be the case for a 2015 game, but producing slightly higher-res meshes from the original sculpts is manual work. Topology and weight-painting at minimum.

      So, different proposal: Don’t do it yourself. Scrap together a couple of millions to have someone do it for you.

      source

      • starman2112@sh.itjust.works ⁨7⁩ ⁨months⁩ ago

        Wait, are you under the impression that this is a rerelease of the 2015 battlefront?

        source

        • -> View More Comments
  • MonkderZweite@feddit.ch ⁨7⁩ ⁨months⁩ ago

    and 1/4 of it’s original resolution. Seems doable.

    source

    • barsoap@lemm.ee ⁨7⁩ ⁨months⁩ ago

      Output resolution has negligible impact on VRAM use. 32M for a 4-byte buffer for 4k, 8M for 1080p. It’s texture and mesh data that eats VRAM, texture and mesh data that’s bound to be different between different cameras and thus, as I already said, can’t be shared.

      source
• PillowTalk420@lemmy.world ⁨7⁩ ⁨months⁩ ago

  I would go back in time to 1995 and give John Carmack modern tools and maybe UE5 and see what happens.

  source

  • ICastFist@programming.dev ⁨7⁩ ⁨months⁩ ago

    Even if you gave him a current-day computer to play with (otherwise, even supercomputers of the time would struggle to run UE5), he wouldn’t achieve much, consumer grade computers back then really struggled with 3D graphics. Quake, released in 1996, would usually play around 10-20 FPS.

    source