Step 4 — Setting up a first session and checking it works

It assumes you finished Step 2 with a written note about your hardware, and Step 3 with an account whose email address is confirmed. It is written in general terms that apply to account-based desktop games as a category, because the exact buttons differ between titles and a walkthrough of any one interface would go out of date within a patch or two.

It also assumes you are installing software you chose to install. Nothing in this course scans your computer, tells you that something is wrong with it, or asks you to run a utility. The checks below are things you can observe yourself.

1. Pick a quiet time. Judge the game when the household is not streaming video and you are not tired. A first session at eight on a Saturday evening tells you about your neighbourhood's network, not about the game.
2. Obtain the game from the publisher's own site or an established store. Whichever route you choose, it should be the one the publisher itself points to. Avoid files obtained from anywhere else, because an installer is a program you are giving permission to run.
3. Let the installation and any first update finish before starting. Many games install a launcher that then fetches the game itself, and starting while that is still working is the most common cause of a confusing first failure.
4. Check the graphics driver is current. On Windows, the graphics card manufacturer publishes its own driver software; on Linux, the distribution's own update process usually handles it. An out-of-date driver produces exactly the symptoms people blame on hardware.
5. Open the settings menu before the tutorial. Set resolution, graphics quality and volume first. The section below lists what to look for.
6. Play for twenty to thirty minutes without changing anything, then make one note. Was it smooth, uneven, or unplayable? One sentence is enough, and it is the sentence the rest of this step works from.

Set expectations before you begin, so that a long download does not read as a problem.

The download figure is the one people underestimate. If your connection is modest, start it in the morning and plan to play in the evening; there is no advantage to watching it.

Five settings, in roughly the order they are worth your attention. The names vary between games; the ideas do not.

• Resolution. Set it to match your monitor rather than above or below it. A mismatch makes everything look soft and is often mistaken for poor graphics.
• Overall quality preset. If Step 2 put you between minimum and recommended, start at the lower preset and raise it later. Starting high and dropping down after a bad session muddles the comparison.
• Frame rate limit or vertical sync. Capping the frame rate often makes a modest machine feel steadier and run cooler, even though the number is lower.
• Audio. Set master volume and, if separate, voice chat volume before entering a match with other people rather than during one.
• Privacy and social options. Many online games let you decide who can message you, who can see your profile and whether voice chat is on by default. These are easier to set at the start. For general guidance on online safety settings, the eSafety Commissioner publishes material aimed at adults and families.

Most first-session problems fall into three families, and they have different fingerprints. Telling them apart saves you from changing the wrong thing.

A hardware limit

The picture is consistently uneven — it stutters in busy scenes and smooths out in quiet ones, and lowering the quality preset makes a visible difference. Fans may become loud. This pattern is the machine working at its ceiling, and the remedy is lower settings or a different game, not a different network cable.

A connection problem

The picture is smooth but the game is unresponsive: your input happens and the world reacts a moment later, other players jump between positions, or you are disconnected mid-match. Lowering graphics settings changes nothing, because nothing about the drawing was wrong. If the game displays a latency figure, this is where it is relevant, and if the household is busy, try again at a quiet hour before concluding anything.

A software conflict

The game refuses to start, closes immediately, or reports an error about a missing component or about anti-cheat software. This family is not about performance at all. The publisher's own support pages are the right place for it, because the message text is usually specific and the publisher has seen it before.

Three ordinary habits, none of them specific to games, and none of them presented here as something you must buy.

Keep the operating system and the graphics driver updated, because updates fix the faults that produce odd behaviour in demanding software. Keep the game account's password unique, and if the publisher offers a second factor for sign-in, consider turning it on — a game account with years of purchases behind it is worth as much to someone else as it is to you. And keep a note of which email address the account uses, because in two years you will not remember.

General, vendor-neutral advice on updates, passwords and account security for individuals and families is published by the Australian Cyber Security Centre. We point you there rather than restating it, and nothing in this course suggests your device has a problem or that you need to install anything to find out.

The hypothetical share house starts the download on a Tuesday morning and plays on the Tuesday evening, which is the quietest night of their week. This is invented to illustrate the step; there are no names here and no claims about how anything performed.

The first update finishes while they make dinner. Before the tutorial, they set the resolution to match the monitor, choose the lower quality preset because Step 2 placed them between minimum and recommended, cap the frame rate, and turn voice chat off by default so that the first evening is quiet.

Twenty-five minutes in, they write their one sentence. In their case it reads: "smooth most of the time, uneven when a lot is happening at once." Against their Step 2 note, that is the hardware-limit fingerprint rather than the connection one, so they raise nothing and leave the lower preset alone. They do not chase a fix, because nothing is actually broken — they have simply learnt where this computer's ceiling is, which was the point of the exercise.

You should have played once, deliberately, at a quiet hour, with settings you chose rather than inherited, and you should be able to say which of the three families any problem belongs to.

You should also have resisted buying anything yet. Step 5 is about money, and it is much easier to decide about money before the game has shown you something you want.