e

  • 2 Posts
  • 59 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle


  • If you are playing games where trackpads are useful, there’s not really another option, so it’s automatically a good value. I know my steam deck experience would have been a whole lot worse without those, and I would probably never consider a gaming handheld without them. But for the gaming I do with an xbox controller, I currently just use it for some video games at my computer (where I have access to a mouse anyways), and maybe split screen with family. I think my Gamesir Cyclone 2 controller (at half the price) is an unambiguously better deal for that, in the premium controller space. If I were using it mostly for couch gaming, that might put the Steam controller in a better position, or if I were mostly playing games that support whatever haptic trigger things Sony has, that controller might be in a better position.

    One of the other more unique features is the tracking in the Steam Frame. It would be cool if they could standardize that sort of thing so it would work with other headsets. I wonder if they’ve considered that.


  • As an amateur computer graphics person, the best way to draw accurate stars is to just pre render it onto a cubemap. But if you really need that subpixel worth of parallax to be completely accurate for every star, there are a couple ways I can think of off of the top of my head. With any you’d want to make sure you only store position, size, and color, since stars are all spheres anyways. With effort, you can be very flexible with how these are stored. (4 bits color temperature, 4 bits size, 3*32 bits coordinates maybe)

    • splat each star into the screen texture with atomics
    • some sort of tiled software rasterization thing, like in Gaussian Splatting

    Worse ideas:

    • instanced hardware rasterization
    • ray tracing

    This is not that well suited to most usual rendering techniques, because most stars are probably going to be much smaller than a pixel. Ray tracing would mean you need to just hit every star by chance (or artificially increase star size and then deal with having tons of transparency), hardware rasterization is basically the same and additionally is inefficient with small triangles. I guess you could just live with only hitting stars by chance and throw TAA at it, there’s enough stars that it doesn’t matter if you miss some. That would react badly to parallax though and defeats the purpose of rendering every star in the first place.

    It’s much more efficient to do a manual splatting thing, where for each star you look at what pixel(s) it will be in. You can also group stars together to cull out of view stars more efficiently. Subpixel occlusion will be wrong, but it probably doesn’t matter.

    This is all just for the viewport, though. Presumably there are other objects in the game besides stars, which need to have reflections on them of the stars. Then that becomes an entirely different problem.

    The real answer though is that you wouldn’t try to render all of the stars, even if you want parallax. Maybe some of the closer and larger ones as actual geometry, simplify a ton of stuff in the background, render things as volumes or 2d billboards, have a cubemap for the far distance, etc

    Edit: also ofc this presumes you know the position, scale, temperature of every star

    I also like the idea of baking all of the stars into a volume in spherical coordinates, centered around the origin



  • Yeah, probably the main reason it’s getting the little bit of praise that it does is that they’re showing it off on games with fairly flat-looking skin shaders. Unfortunately a problem with this sort of thing is that getting that “2023” image is the result of giving a whole team a huge amount of time to model one man’s face. If you’re Bethesda and you just want to get NPCs into Starfield, it would be a similar amount of work. A bit less, since the first people already gave a talk on it, but still much more work then just getting a diffuse BRDF with some subsurface scattering and calling it good. But you also need a process that can be applied to every single NPC…

    And looking at Striking Distance Studios, the company where that 2023 image is from:

    In February 2025, it was reported that most of the studio’s developers had been laid off.

    Yeah, I think it’s safe to say that the work those people put in will never be directly reused.

    Another reason the DLSS version looks a bit more realistic there is because of the specular highlights on the eyes, for example. They probably aren’t reflecting anything real, or else they would be there in the original. But the AI knows that specular highlights add realism and are plausible in this scene, so it puts them there. That’s something that an artist could do if given a specific shot and camera angle, but in the general case they can’t really do that without causing problems.





  • Sure, I could definitely see situations where it would be useful, but I’m fairly confident that no current games are doing that. First of all, it is a whole lot easier said than done to get real-world data for that type of thing. Even if you manage to find a dataset with positions of various features across various biomes and train an AI model on that, in 99% of cases it will still take a whole lot more development time and probably be a whole lot less flexible than manually setting up rulesets, blending different noise maps, having artists scatter objects in an area, etc. It will probably also have problems generating unusual terrain types, which is a problem if the game is set in a fantasy world with terrain that is unlike what you would find in the real world. So then, you’d need artists to come up with a whole lot of datat to train the model with, when they could just be making the terrain directly. I’m sure Google DeepMind or Meta AI whatever or some team of university researchers could come up with a way to do ai terrain generation very well, but game studios are not typically connected to those sorts of people, even if they technically are under the same company of Microsoft or Meta.

    You can get very far with conventional procedural generation techniques, hydraulic erosion, climate simulation, maybe even a model of an ecosystem. And all of those things together would probably still be much more approvable for a game studio than some sort of machine learning landscape prediction.



  • Are there any alternatives that are decently fast for large files? My computer and my phone both get at least 300 mbps from the router, and I have yet to find a local file transfer application that will be anywhere near that fast for large files (destiny, local send, kde connect, might have tried others, I don’t remember)