[–] 2 points 1 year ago

Imo must have specs include SSD (2 TB preferred), and at least 16 GB RAM, but more is better. Also a decent GPU. I still do okay with my old RX 580 but sometimes run into issues and need to turn down settings to get better fps.

I know there are distros meant for newbs and distros meant for gaming, but if you're just starting honestly I would go mainstream with a Debian or Ubuntu, so you can easily get support from others who have asked the same questions.

Debian stable is rock solid and while it might not have all the latest versions of everything in the default repos, it will NOT break. Ever. I've ran it for about a decade now on various machines no issues. I did manage to also get steam and VR working with Debian, but iirc while steam itself is easy and mostly out of the box, the VR needed some installation.

Ubuntu is mainstream but has Snap and snap sucks, but it will also have easy to find solutions if you search for help. But I've also ran into problems with snap versions of programs and tools having odd problems.

My daily driver for gaming had been Archlinux for 7 years, but that broke a few times. Do NOT recommend for newbs as the install was also very manual. Right now I'm on Garuda and have been for probably 4-ish years. If you grab the right installer it actually has a very newb friendly install, but it is Arch -based so while I view it as easy, and I've had no issues whatsoever in those 4 years, I'm reluctant to recommend it for a first distro right off the bat.

So if I were you, I'd start with a distro like Ubuntu or Debian stable, do the stock install but pay attention to what it says about partitioning at the beginning. If it offers to put /home on its own partition, select that, make it as large as reasonable (1/2 to 3/4 disk size). After you get comfortable with your Ubuntu or Debian, then learn about partitioning and look into distro hopping and dual booting. Keep a LiveUSB on hand just in case you break your bootloader, never hurts to have one or more recovery USBs.

  • source
  • [–] 9 points 1 year ago (6 children)

    What are some must have specs in you opinion to run most modern games

    There are none. Choose the best ones to fit your budget.

    would you have a #1 recommend for a prebuilt to get started with?

    I don't really recommend prebuilts. If you look up reviews most of them are just awful. But iBuyPower seems to have a decent reputation. The Steam Machine will be available sometime next year but its a relatively underpowered machine built for the living room. Not sure what your budget looks like or how you plan to play but that could be a good option. However it should be noted that it's not upgradable. I've saved buckets of money by upgrading my PC over the last 20 years.

    As for distros, there is obviously no "best". The most commonly recommended one for beginners is Linux Mint. I recommend Zorin. If you want the best possible gaming performance, you could go with Cachy. It's also available with Steam's "Game Mode", which will give you that handheld/living room experience.

  • source
  • For a heavy duty gaming PC that you want to last many years without having to touch hardware again, I’d recommend 32GB RAM and most definitely go nvme SSD drives (not SATA). No spinning rust drives unless you have a specific use case for media or archive storage.

    As far as the cpu and video card, unless you plan to heavily get into ray tracing in games or play with (gag) “AI”, AMD will be great for both.

    I’d recommend Mint or PopOS for a starter distribution. I do not recommend Bazzite to newbies because an immutable distro adds another level of learning concepts you don’t need at the beginning.

  • source
  • [–] 6 points 1 year ago (2 children)

    People have been recommending bazzite for newbies who want to game. I haven't tries it but have found PopOS to be very easy and stable. Pop does simplify nvidia support as well but I run an AMD GPU for the reasons you mentioned.

  • source
  • [–] [S] 1 point 1 year ago*

    Well, like the examples I tried to give... its fairly common in game dev to set aside a distinct physics thread or set of threads, that run at some fixed number, maybe 30 or 60 fps, to avoid the once very common problem of game physics functions going bonkers with unexpected hardware speeds.

    It also helps with just generally normalizing physics behavior in complex vs simple scenes, lets you just have solid bounds for number of whatever kind of dynamic things possible in an area.

    Or, for doing things like deep simulation, where you run like, an aporixmation, a simplification of many npcs, non rendered, but when a player comes into view of one of them, then they transition from approximately simulated, to fully simulated.

    So like, most games just spawn and despawn like crowds of people by more or less a 'where are you' 'what time of day is it' and 'what npcs should be here', and then it just picks blank templates out of a pool.

    But if you wanted a uh, 1000s of npcs doing a daily routine in a city or landscape, potentially having reactions to other npcs they may meet... thats more like deep sim, thats something you can approximate on a slowed down timeframe, thus potentially shunt off to another segment of threads/hardware, more geared toward regular iterations on a massive dataset, than hyperspecific, hyper fresh data.

    Can also be used with something like dynamic, ambient loot or wildlife or fauna generation/simulation.

    Like yeah, I agree that there are mant uses cases where 10ms is still too much latency, but... why not apply 'foviated rendering' to something like... procedural terrain generation, in chunks/maps/meshes of descreasing size, increasing detail?

    If the player is mostly stationary, not moving rapidly, just slowly build out more detail ariund them, in a circle.

    If they are moving rapidly, prioritize pre caching various detail levels of chunks that they are rapidly moving toward, stop the above naive, layered detail build out process.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (1 child)

    10ms is way too slow for multithreading latency in games. Even 1ms for part of a frame is too slow. At 90hz you only have 11ms per frame.

    Though using your pc as a host for a game server that the frame connects to would be possible. Like a multiplayer game. It could help with offloading some CPU heavy elements. I suspect though that most of the difficulty will be rendering, like in the quest.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago* (last edited 1 year ago)

    Ok, yeah, I mixed up Foveated Rendering and Streaming.

    So what I'm trying to say is that Valve has figured out a generalized Foveated Streaming layer that just works on all games, full stop.

    So, you, a game dev... look at that, and build around whatever they're using in Steam Link to accomplish that... use that as a template/basis to build a sort of dual device , seperated out async threading mode.

    If Steam Link can move data that fast, then build your game/engine from the ground up with that protocol in mind, that you're always gonna have a second hardware instance that you can run some subportion of game logic / engine calls on, some kind of async multithreading.

    Not just native Foveated Rendering in a VR context, but potentially any kind of game/engine level sort of API or... mode or something, that would allow this superfast Steam Link streaming to have a game be ... collaboratively generated by many devices linked with this kind of nearby, wireless speed.


    Maybe a rough analog here would be the difference between a game that is built from the ground up with full Steam Input support, so it gives you more options than if you're just using Steam as an over the top, generalized input translation layer.

    Of course, ... I think basically only Source games actually have full Steam Input support, and I have no idea if this Foveated Streaming thing is... open source or proprietary to Valve.

    If its open, theoretically anyone could try to do this.

    If its proprietary, well then it'd just be Valve.


    Maybe another analogy that comes to mind is a weird, little used way of running ARMA servers.

    So with ARMA games... they're big, fuckass complex, open world milsims, ARMA literally just is the commericial, streamlined version of the much more hardcore milsims they sell to governments/militaries.

    ARMA servers can be ran in a way where you have more than one server doing the actual computations. This mode, these protocols, they do exist in the commerical variants, but they are not well documented, almost nobody uses it, because its quite complex.

    Players will join the main dedicated server, but the dedicated server can also shunt off tasks like simulating the movement patterns of 100s or 1000s of other NPCs to other, synchronized servers.

    So what you as the player join as the dedi, thats basically just coordinating traffic and world states between players, and also NPCs, who are essentially being simulated on their own servers, which are running in a mode that is optimized for just simulating them.

    This is kinda sorta analagous to what I'm trying to describe with the Frame and Machine, its just thst now you as a player, externally networked or not, now you have a two hardware system combo that is cumulatively producing your whole game experience, which theoretically should be possible if you can low level implement whatever protocol Steam Link is doing to be able to stream data both ways so fast, as they are with Foviated Streaming.

    Right?

    Because that Foveated Streaming has to be hooking into actual hardware inputs from the Frame, the eyetracking, then it bounces that to the Steam Machine, does calcs, throws some result back to the Frame, super fast.

    So, it has some low level of hardware input access, and obviously the Frame alters what the display renders based on what the Machine tells it to, so we have two way, super low latency, local wireless communication going on here.

    From the Gamers Nexus interview, basically, this is only possible because the Frame and Machine are talking via a dedicated WiFi7 dongle, that is soley used by them.


    Anyway, no clue if this would actually make in practical sense in terms of trying to take the time to develop it, what the actual gains or benefits would be... I'm just trying to brainstorm out things that may potentially be neat/possible.

  • source
  • parent
  • context
  • [–] 5 points 1 year ago (1 child)

    Basically, the Frame eyetracks you, and it uses that data to prioritize which parts of the overall scene are rendered at what detail level.

    That's an accurate description of foveated rendering, but what the Frame has is foveated streaming. Foveated rendering needs to be incorporated in the game, typically at the engine level. Foveated streaming can happen at the system-wide level because it's not reducing the rendering load, but instead reducing the bitrate of the streamed video when you're streaming wireless VR over wifi from your desktop PC or Steam Machine.

  • source
  • parent
  • context
  • [–] 5 points 1 year ago* (1 child)

    FeX is userland only though, I'm wondering how they're getting it booting arch in the first place since arch doesn't support ARM officially (Arch Linux ARM/alarm is a separate project that has had serious maintainership issues with their packages to the point where a lot of core packages break due to being partially out of date)

  • source
  • parent
  • context
  • [–] [S] 3 points 1 year ago* (last edited 1 year ago) (4 children)

    I mean, yeah, but... I'm thinking like a uh, distributed compute type of model, like you see on scalable server rack type deployments for what we used to call supercomputers.

    If the latency is 10ish ms, thats easily low enough that you could say, split off a chunk of the total game render pipeline instruction set, maybe a seperated physics thread, run the whole game from the x86 Steam Machine, use Steam Link as a communication layer, send x86 to the Frame, which then 'solves' it via the FEX emu-layer, and then the Frame also doesn't do any other part of rendering the game, it just accepts player inputs and then recieves graphical render data.

    Physics runs at only 60fps, rest of game runs at 90 or 120 or w/e.

    Steam Machine is the master/coordinator, Frame is the slave/subject, it has various game processes just distinctly dedicated to it's compute hardware, the Steam Machine is then potentially able to get/use more compute, assuming synchronization is stable, which means overall experienced performance gain, more fps or higher quality settings than just using a Steam Machine.


    They are already kind of doing this via what they are calling Foviated Rendering.

    Basically, the Frame eyetracks you, and it uses that data to prioritize which parts of the overall scene are rendered at what detail level.

    IE, the edges of your vision don't actually need the same level of render resolution as the center of your vision... because human eyes literally lose vision detail away from the center of their vision.

    So, they already have a built in system that showcases the Frame and the Machine rapidly exhanging fairly low level data, as far as a game render pipeline goes.

    I'm saying, use whatever that transport buffer is, make a mode where you could potentially shunt off more data via that buffer into a distributed, sort of 2 computer version of multithreading.

    How is that really different than a game with a multiplayer client/server model?

    Like, all source games are basically structured as mutliplayer games with the server doing the world, and the client doing the player... when you play a single player source game, you're basically just running both the client and the server at the same time, on your one machine, without any actual networking.

  • source
  • parent
  • context
  • [–] 14 points 1 year ago* (1 child)

    So uh, ahem.

    Yes.

    Valve can indeed count to three.

    No, the Steam Controller doesn't fully count. This is 2.5 at best.

    And see how the Steam Frame only has two screens and not three?

  • source
  • [–] [S] 6 points 1 year ago* (last edited 1 year ago) (2 children)

    The Frame uses FeX for ARM emulation.

    Then it does Proton in top of that.

    The Machine is x86, but you can Steam Link stream to the Frame (ARM) from the Steam Machine (x86), or, run some games entirely from the Frame (ARM).

    They very much have been developing / leveraging linux into ARM, check out Gamers Nexus video for some more on that, as well as bunch of other stuff.

  • source
  • parent
  • context
  • [–] 10 points 1 year ago (3 children)

    I know they said they're using fex for x86 emulation but how far down does that go? AFAIK arch Linux doesn't have official arm support yet (alarm exists but they've had a lot of problems keeping packages up to date) so I wonder if Valve is planning on helping with upstream arm support

  • source
  • [–] [S] 13 points 1 year ago* (last edited 1 year ago) (6 children)

    Yes, on the Frame, the VR headset, yes, it uses uh.. PeX, FeX? Something like that.

    x86/arm translation emulation layer, and then also Proton, a translation layer for windows/etc.

    Interestingly... it seems there may be, or maybe potentially could be in the future... some realtime compute sharing going on, if you have a Machine and a Frame.

    Because... you can Steam Link stream from the Machine to the Frame, or run some games off of the Frame itself, which is roughly a very fancy smartphone, in hardware terms.

    Its via a dedicated WiFi 7 streaming dongle... and Gamers Nexus just said thats roughly a 10ms lag, 20ms worst case scenario.

    So... you could theoretically make a specific like, multithreading mode that takes advantage of a Machine + Frame setup.

    No clue if that actually exists or not, but it does at least seem possible.

  • source
  • parent
  • context
  • view more: ‹ prev next ›