Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Question Games system requirements ?

Discussion in 'General Discussion' started by komrad2236, Oct 1, 2022.

  1. komrad2236

    komrad2236

    Joined:
    Oct 1, 2022
    Posts:
    1
    Newbie here
    I'm trying to understand, what determines system requirements for a game made in Unity ?

    And once my game is done, how do I know exactly what are system requirements to run that game ?
    Does Unity tell me that after I compile the game or do I run benchmarks manually or what ?
     
  2. Antypodish

    Antypodish

    Joined:
    Apr 29, 2014
    Posts:
    10,594
    You profile your game. You can estimate performance based on your experience.
    But for the most, you test on target audience hardware.
    Either you test yourself, on weakest or target device you are going to support. Or you run playtest with your testers, to find out what you can support.
     
  3. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    4,196
    Yup, keep looking at the profiler while developing. Or at the minimum keep the Game window Stats popup open to see how many ms are spent on CPU and GPU. That gives you an indicator whether you're GPU (rendering, postprocessing) or CPU (scripts, game objects) bound.
     
    BrandyStarbrite and Ryiah like this.
  4. angrypenguin

    angrypenguin

    Joined:
    Dec 29, 2011
    Posts:
    15,519
    This. Under ideal circumstances you don't just test afterwards, you pick a target early on and aim for it.

    The target has two parts:
    - Target hardware specifications. E.g. my game will run in an i3-5157U, 4GB RAM, Intel HD5500 graphics on Win 10. (Clearly not aiming very high with that example!)
    - Target performance requirements. E.g. the game will run at 30fps >95% of the time, and never drop below 10fps except during loading.

    For the target hardware I'd pick something which was easily available to me, so that I could build it into my regular testing. Performance is a feature, and you need to know when it's broken. This has a couple of benefits:
    1. It's far easier than making a game and then trying to figure out what it needs to run on afterwards.
    2. You're likely to better optimise your game, because you have a clear target to hit, and can tell when you're missing.
     
    Socrates and Ryiah like this.