Comment on Open source community figures out problems with performance in Starfield

• Leeps@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Yeah you always have. They’ve been screwing modern graphics features to the old dog for years and hoping it’ll continue to work. There’s some serious limitations in it that another engine would be able to work through for a game like this. Seamless planet travel for one, and less abrupt loading.

  source

  • Cethin@lemmy.zip ⁨1⁩ ⁨year⁩ ago

    People really have no idea about anything in game development. I agree it should have seemless planet travel, but it is not something that an engine “can just do.” It takes so many complicated systems to make that function. There’s no engine that does it out of the box. Basically any engine can do it, but it requires it to be built. The land must be deterministic at all points, it must be able to create chunks accurately for all points (which gets really weird at the poles, but any latitude above 0 because your chunks shouldn’t be square anymore), and they must be able to be streamed in to their correct position seemlessly. It is quite complicated, and there’s no reason the engine developed for an arena shooter (Unreal) would be able to handle it any better than any other engine. It just has to be built.

    source

    • TheDarkKnight@lemmy.world ⁨1⁩ ⁨year⁩ ago

      I guess though I mean it is expected at this stage of game development for this genre to have seamless planet travel. Like it didn’t have to be NMS or Elite Dangerous, they could’ve copied something like how Jedi Fallen Order did it, where basically your ship takes off from the planet, jumps to hyperspace and loads the next one during hyperspace and lets you know when you’re ‘arriving’ (aka when the destination is loaded). It ends up being the same thing as what Starfield basically does but handles it much more deftly.

      Idk, just saying there’s better ways they could’ve handled it even if the engine couldn’t handle seamless planet travel in a traditional sense.

      source
    • colonial@lemmy.world ⁨1⁩ ⁨year⁩ ago

      There’s a reason Hello Games wrote their own engine for NMS. We all know that it was pretty bad gameplay-wise at launch, but under the hood NMS was (and still is) something of a technical marvel. No loading screens except for a disguised one when jumping between systems is quite impressive.

      source

      • Ser_Salty@feddit.de ⁨1⁩ ⁨year⁩ ago

        Also, IIRC, NMS doesn’t have different gravities, right? Been a year or two since I properly played, but I don’t remember ever really jumping higher or being forced to the ground. That’s one of the sacrifices for seamless landing.

        source

        • -> View More Comments
      • Cethin@lemmy.zip ⁨1⁩ ⁨year⁩ ago

        Impressive for sure. They had to choose to not have a lot of things to do it though. They knew what they wanted and did it, which is smart.

        source
    • kogasa@programming.dev ⁨1⁩ ⁨year⁩ ago

      I have no game dev experience but I have a math and software background. I’m just curious about what “it gets weird at the poles” means. If I wanted to (abstractly) generate tiny square chunks of a large sphere, I would generate them as (proper) squares and then pass them through an explicit diffeomorphism to the associated region of the sphere, relying on the relative smallness to guarantee that the diffeomorphism doesn’t change things too much. From a game dev perspective, what approach do you take that causes issues at the poles?

      source

      • BradleyUffner@lemmy.world ⁨1⁩ ⁨year⁩ ago

        Imagine trying to find the intersections of a line or region as it crosses multiple cells of a non-euclidian “grid” near the poles where an entire axis can flip from one cell to the next.

        source

        • -> View More Comments