Squadron 42 Playtest Reactions: What Manchester’s Players Loved—and What Needs Work

Eleven firsthand accounts from Manchester: the combat that surprised players, the moments that held them spellbound and the rough edges they want fixed.

For years, Squadron 42’s audience has watched someone else hold the controls. This weekend, invited players finally got their turn—and the most interesting thing they brought back from Manchester is how differently they spent it.

Some lingered aboard the Idris, listening to conversations and trying its distractions. Others pushed further into the missions, exchanging fire with enemies who fought back hard. They returned with stories about beautiful places, convincing performances and a campaign they wanted to keep playing. They also brought specific complaints: awkward instruction, inconsistent bugs, performance trouble and stretches where the spectacle left too little room to play.

Our first Manchester report captured the opening response. With more complete accounts now available, we can look at the people behind those reactions. Here are eleven perspectives on the October 2026 playtest, including what each player enjoyed and what held their experience back.

BoredGamer wanted more time actually playing

BoredGamer’s reaction is easy to misread if you only encounter the walking-simulator clip. In his full account, he repeatedly praises the beauty, atmosphere and enjoyment of the experience. He also wanted more hands-on action during his session. Those opinions belong together.

“It is a very fun game. It is very beautiful. It is very unique.”

BoredGamer, 0:22

What won him over: the shipboard conversations, activities and collectibles gave him plenty to investigate. He liked the cleaner interface, streamlined quantum travel and spectacular ship destruction. His own curiosity slowed him down: he spent time experimenting and exploring rather than following every objective immediately.

What frustrated him: he encountered bugs and a crash, while acknowledging that he deliberately tried to break things. The early spacewalk was especially awkward. By the end, he still felt he had received too little gameplay to make a sweeping judgement about the whole campaign.

His enthusiasm did not amount to a declaration that the build was ready. He wanted further polish and more time with the action. His reaction leaves room for both excitement and impatience.

Inside BoredGamer’s five hours

• The opening verdict was positive. He introduces the game as fun, beautiful and unique. That matters because the walking-simulator description later in the video can sound far more dismissive when separated from the rest of his reaction. His complaint is about the balance of activity he reached, rather than a claim that the whole visit was dull.
• The ship kept distracting him. Conversations, collectibles and recreational activities were things he chose to investigate. Spending time with those details reduced the amount of mission progress he made. His account is therefore especially useful for anyone who tends to search every room before following an objective.
• He experimented instead of taking the quickest route. BoredGamer acknowledges attempts to break things. That gives some context to the faults he encountered, but it does not make those faults disappear. Players will explore, interrupt routines and try unexpected interactions after release too.
• He wanted the campaign to put him to work sooner. Even after enjoying the distractions, he wanted more direct gameplay from the available session. Someone can appreciate an inhabited warship and still want the next sortie to arrive. His reaction captures that tension particularly well.
• Quantum travel felt more streamlined. He responds positively to a less cumbersome interface and travel experience. For a campaign that needs to move between conversations, launches and combat, fewer interruptions could help maintain momentum.
• Visible ship destruction made an impression. The combat presentation was among his positives. His praise concerns what he saw and experienced in the event build; it is not a specification for how every ship or material will behave in the finished game.
• The early EVA sequence was a stumbling block. He found it awkward and frustrating. This is one of the few complaints that recurs across otherwise quite different reactions, making it more significant than an isolated dislike of a particular scene.
• Enjoyment and readiness were separate judgements. He could describe the experience as unusually enjoyable while still saying it needed work. His closing enthusiasm should be read alongside his requests for polish and more time with the action.

Citizen Spooner loved the world—and hit a very rough dogfight

Spooner’s account gives the strongest contrast between the campaign’s appeal and the interruptions that can spoil it. He describes the Idris as a place that felt inhabited, with crew working and talking around him. Launching from it was a highlight; so were the sound, performances and the later rhythm of moving, scanning and shooting.

“I enjoyed what I played today and I want to play more.”

Citizen Spooner, 38:20

The good: responsive weapon handling, lively surroundings and firefights that demanded attention. The combination of scanning, taking cover and advancing began to click as he played.

The problems: one early Gladius encounter felt so laggy that he asked a developer for help. Reloading improved it without fully curing it. He also disliked precise body-by-body looting under fire, found some instruction unclear and thought certain enemy rushes looked clumsy.

His reported frame-rate counter did not explain the poor responsiveness he felt. He left wanting more, but wanted the remaining development time spent fixing these problems.

Citizen Spooner’s detailed observations

• The Idris felt like a place people lived and worked. Crew activity and conversation helped give the ship an identity beyond its corridors and machinery. His enthusiasm is about the people within the setting as well as the visual detail. That is an encouraging response for a story built around service aboard a warship.
• Launching was a highlight. The transition from the ship to flying left a strong impression, supported by the sound and performances surrounding it. It is the sort of sequence where a campaign can give a familiar spacecraft a different emotional weight from simply calling one at a terminal.
• The first dogfight was a serious problem. He describes responsiveness so poor that he sought help from a developer. Reloading improved matters without completely curing them. This deserves more attention than a generic note that a preview build contained bugs: it affected his ability to participate in a major encounter.
• A frame counter did not match the sensation at the controls. Spooner discusses seeing a healthy-looking counter while the action still felt wrong. His testimony cannot diagnose the cause, but it does demonstrate why a single reported FPS figure is not a complete description of the experience.
• The FPS rhythm improved as he progressed. Moving, scanning, taking cover and firing began to work together in a way he enjoyed. That positive account of ground combat sits beside his much rougher early flight experience; neither should erase the other.
• Enemy behaviour had uneven moments. He describes demanding firefights, but also rushes that looked clumsy. The account supports praise for parts of the combat without requiring a claim that every enemy decision was convincing.
• Looting could interrupt a firefight. Having to interact precisely with individual bodies while under pressure was a particular irritation. This is a usability issue as much as a question of realism: the interaction needs to remain manageable when a player is trying to keep moving.
• Some interfaces needed clearer explanation. Equipment selection and instruction created friction. Familiarity with Star Citizen should not be essential to understanding what a single-player campaign wants the player to do next.
• He still wanted another session. His final response was to want more of the game. That makes the criticism useful rather than dismissive: it identifies the things that got between an interested player and an experience he otherwise enjoyed.

Loud Guns found enemies that punished both aggression and caution

Loud Guns went in more interested in Star Citizen’s multiplayer universe than its companion campaign. He came out planning to make time for Squadron 42 at release. His most memorable example concerns a doorway: pushing out got him flanked; hanging back on another attempt brought grenades through it.

“the game just grabbed my full attention throughout the 5 hours”

Loud Guns, 1:46

His highlights: the score, the connection between cinematics and play, reactive enemies and visible ship damage. He also appreciated separate flight and FPS difficulty settings. That flexibility gives a confident pilot who struggles on foot a useful option.

His reservations: the early spacewalk did not clearly explain why he was failing. He saw dropped frames, missing lip movement and a progression problem resolved by loading a checkpoint. He also recognises that a campaign with substantial conversation and cutscenes will not suit every Star Citizen player.

Unlike the more worried accounts, he regarded the faults he encountered as relatively modest beside his enjoyment. His wish list for the Persistent Universe includes the multifunction tool and activities aboard the Idris. Those are wishes, not promises that the same features will arrive in Star Citizen on a particular date.

What Loud Guns brought back from Manchester

• The campaign changed his level of interest. He arrived with the multiplayer universe as his main attraction and left intending to make time for Squadron 42. That is a meaningful shift for readers who have followed the project chiefly because of its connection to Star Citizen.
• His doorway story describes a genuinely reactive fight. An aggressive attempt exposed him to flanking enemies. Hanging back on another attempt brought grenades into his position. The encounter challenged both approaches, rather than allowing one doorway to become a permanently safe firing point.
• Combat carried consequences he could see. Visible ship damage contributed to his enjoyment. The appeal is easy to understand: a successful hit is more satisfying when the target visibly suffers, although one preview encounter cannot establish the full range of damage simulation.
• The score helped hold the experience together. Music was a conspicuous part of his positive response, alongside the movement between cinematics and play. For a naval adventure, the soundtrack has to support quiet conversations as well as the scale of a launch or a fight.
• Difficulty was not one all-or-nothing decision. He appreciated separate settings for flight and FPS combat. A capable pilot could lower the challenge on foot, or an experienced shooter could make the flying more forgiving. That accommodates different backgrounds without assuming every player arrives with the same strengths.
• The spacewalk needed better feedback. His concern was not simply that it could be difficult. He did not always understand why an attempt failed. Clear feedback lets players learn from a mistake; uncertainty can make the same retry feel arbitrary.
• The bugs were real, but did not dominate his verdict. Dropped frames, a face without matching lip movement and a progression problem all appeared in his account. A checkpoint reload resolved the latter. He regarded these faults as relatively modest compared with the enjoyment he took away.
• He started imagining features in the PU. The multifunction tool and activities aboard the Idris were among the things he would like to see in Star Citizen. They are useful indications of what impressed him, but his wish list is not a development commitment or a release schedule.

Red Monster SC reached enough combat to tell a different story

Red Monster SC describes four or five dogfights during his five-hour session, alongside FPS encounters and exploration. That makes his account a useful companion to BoredGamer’s: the amount of action someone reached varied with their progress.

What stood out: the updated flight experience, quantum travel and ships breaking apart in combat. He enjoyed environmental storytelling during journeys, and the way the campaign introduced the Stanton’s training facilities and equipment choices. Walking with another character carried dialogue and context, rather than feeling like an empty journey to the next marker.

What remains qualified: he says the experience was not entirely bug-free, but does not offer a comparably detailed list of personal faults in this video. He remained optimistic about the remaining development work.

He also discusses a later mission demonstrated by a developer during the studio tour. That was something he watched, separate from his own hands-on session. His praise for that demonstration should be read separately from his own experience at the controls.

Red Monster SC’s account, point by point

• He reached a substantial amount of combat. Four or five dogfights in roughly five hours makes his experience sound very different from the accounts dominated by walking and conversation. It establishes what he reached, without turning his progress into a universal timetable for the opening.
• Travel was part of the attraction. Quantum travel and the updated flight experience were early positives in his account. Rather than treating the journey as disposable time between objectives, he found things to enjoy while moving through the campaign.
• Ship destruction gave battles a visible payoff. He describes ships breaking apart in combat with enthusiasm. This supports the broader pattern of attendees responding strongly to damage presentation, while remaining a report of preview encounters rather than a technical audit of Maelstrom.
• The surroundings carried story. Environmental detail and the places encountered along the way contributed to his interest. That matters in a campaign where the player spends time outside a cockpit: a corridor or journey can develop the setting even before another firefight begins.
• Training and equipment were introduced through the ship. He discusses facilities and loadout choices aboard the Stanton. This gives a more specific sense of shipboard life than the idea of a warship serving only as a backdrop between missions.
• Walking with someone could still feel purposeful. Dialogue and context made those passages worthwhile for him. His account is a reminder that a slower section is not automatically empty; whether it holds a player depends on how much they enjoy the conversation and setting.
• The studio tour included something he watched. His description of a later mission comes from a developer demonstration. It should not be counted as another mission he personally completed. We have left its plot details out of this roundup.
• His optimism about fixes was an opinion. He acknowledged that the build was not bug-free but expressed confidence in the remaining work. The video does not support inventing a list of faults he never described, or treating his confidence as a guarantee of launch quality.

Enderprize found a warship she wanted to explore

Enderprize’s immediate reaction after five hours is warm, animated and full of small discoveries. The radar, the gym, people moving through the Idris and the way quantum travel worked all stayed with her. She talks about a game that felt much more coherent and polished than the Star Citizen experience she was used to, while still identifying visual faults.

Her description of it as feeling finished is a personal comparison with other games she has played at launch. It is not a declaration that development is complete. What makes the account valuable is the detail behind that enthusiasm: she describes the controls she used, the things that diverted her and the problems she actually encountered.

The details that caught Enderprize’s attention

• The sound helped sell the setting. She singled it out early in her response, alongside the general fidelity of movement and interaction. Her comparison with Star Citizen was strongly favourable, although it remains an impression of the build she played rather than a controlled comparison between the two games.
• Scanning worked as an investigative tool. She describes an on-foot scan revealing conduits within walls while looking for a flight recorder. That is a concrete example of environmental interaction giving the player a reason to study the surroundings instead of simply following a corridor.
• The Idris was busy enough to distract her. Seeing people throughout the ship was a highlight. She repeatedly found herself pursuing details away from the immediate objective, then remembering that she also wanted to make enough progress to tell her audience about the game.
• The gym was more than scenery. She describes using a treadmill with a holographic route and interacting with training dummies. These are the small shipboard activities that explain why some attendees spent a surprising amount of their session exploring.
• Her flight controls were comfortable. She used a pair of VKB joysticks and appreciated having fewer buttons to manage while retaining decoupled flight. Her account is particularly relevant to stick users, but it should not be used to dismiss a different experience reported by someone on keyboard and mouse.
• Quantum travel included active steering. She describes following a route while avoiding luminous obstructions, comparing part of the experience with Elite Dangerous’s Supercruise. The comparison describes how it struck her; it does not mean the two systems work identically.
• She did not encounter a familiar navigation workflow. She says she did not see the usual mobiGlas-and-starmap plotting process in what she played. That observation is limited to the session and should not become a categorical claim about every interface in the campaign.
• Her main faults were visual. Cutscene graphics occasionally hiccupped, and restarting a checkpoint corrected one area that looked wrong. She was unsure whether graphics settings could have helped. The important distinction is that she enjoyed a comparatively smooth session, not that she proved the absence of more serious bugs.

Her response is one of the most enthusiastic in this group, and the reasons are recognisably personal. She had comfortable controls, enjoyed wandering the ship and found the presentation convincing. For someone hoping Squadron 42 will make an Idris feel like a posting rather than a vehicle, that is an appealing account.

DaPoets was pulled into the story, then nearly stopped at the spacewalk

DaPoets normally wants friends alongside him when he plays. Squadron 42 surprised him by making him care about a character and a story he was experiencing alone. His account is enthusiastic about the places, the sound and the flying, but it also contains one of the sharpest complaints from the weekend. The early EVA sequence left him repeatedly dying without understanding how to succeed.

That contrast gives his reaction its value. He wanted to keep playing almost everything around the spacewalk; the spacewalk itself brought him close to giving up. Someone who enjoyed the wider game can still identify a section that badly needs attention.

What stood out during his session

• The character gave him a reason to continue.His usual preference is for multiplayer with friends. Here he found himself invested in what would happen to his own character. That is a more telling compliment than another comparison of graphical detail: the campaign had persuaded someone who did not normally seek out this kind of game.
• EVA overwhelmed the rest of his complaints.He describes at least 22 deaths, uncertainty about the route and assistance from a developer. His frustration was severe enough that he wanted the section substantially changed or removed. That is his proposed remedy, rather than a claim that the developers have agreed to it.
• Puzzles made him work for progress.He enjoyed spending time on more involved problems and the satisfaction of finally solving them. The slower moments were not all passive for him; some required thought and experimentation.
• The armoury was a pleasure to use.Trying weapons and finding out how they felt was one of his highlights. It gave him something to enjoy between the larger scenes, rather than simply a menu to clear before the next mission.
• Sound survived his close attention.He deliberately listened for problems and did not notice an audio fault. That is a strong personal endorsement, although it cannot establish that every sound or scene is finished.
• The presentation was impressive, with visible hitches.He praises the overall experience but recalls stuttering immediately before major explosions. We would not turn his event-machine frame-rate observations into a prediction for an ordinary home PC.
• Flight was something he wanted to return to.He enjoyed the more straightforward feel of flying in atmosphere and space. His wish to have that experience in Star Citizen is enthusiasm for what he played, not confirmation of a Persistent Universe update.
• The later demonstration widened his impression.Part of his closing excitement follows a presentation after the hands-on session. Those scenes should not be added to the list of missions he personally completed.

GFA wanted the room to disappear—and, for a while, it did

GFA describes becoming so absorbed that he forgot he was playing in a room full of other people. The acting, cinematography and places he could explore drew him in. Then a cutscene framed a chair where his character should have been, and the illusion broke. His immediate reaction contains both sides of a cinematic game: how completely it can hold someone, and how conspicuous a small visual mistake becomes when the camera asks them to watch closely.

He also wished the event had devoted less of its limited time to material already shown publicly. That is a criticism of what he got to sample in five hours. It should not be mistaken for a rejection of a story-led campaign.

The balance GFA found

• Immersion was his first major positive.The surrounding event stopped occupying his attention. He was following the game rather than constantly thinking about the unusual circumstances of playing it early.
• Minor bugs could have a large visual effect.The absent character in a cutscene did not prevent him from continuing, but it interrupted the sense of being present. His example is specific enough to explain the problem without exaggerating it into a broken campaign.
• He would have allocated the preview differently.He wanted to spend more of the session beyond the familiar prologue. Repeating an introduction already watched online is a different experience from discovering it for the first time at home.
• Linear did not mean having nothing to investigate.He describes a directed campaign with space to look around within its environments. That suited him: the story could lead somewhere without every room feeling like a passage he was expected to sprint through.
• Selected sections left him wanting the joins.The event moved players between parts of the campaign. His enthusiasm for those pieces does not settle how naturally the complete story will connect them.
• He was still working on a puzzle when time ran out.Wanting another five or ten hours was his clearest response to stopping. He was keen to continue, while acknowledging that he had only just emerged from the experience and still needed time to reflect.

Hugo Lisoir and CaMaK welcomed the changes, but disliked tutorials breaking the mood

The French-language debrief on Hugo’s Hugo Loisir channel brings two attendees into the conversation. Both had just finished five hours. Their excitement is obvious, but they open with a useful warning: this is a strongly narrative experience, and someone looking for immediate, constant action may struggle with its pace.

They were pleased to revisit a visibly improved prologue. Where GFA would rather have spent his limited session elsewhere, this discussion finds value in seeing how the familiar material had changed. The account below summarises their shared conversation; it does not assign every overlapping remark to one speaker.

Their opening debrief, in detail

• They saw a campaign designed around the player.Early discussion praises changes from Star Citizen that made controls and information easier to understand. Familiarity with the PU was not enough to skip every tutorial, because the two games did not behave identically.
• The options were easier to navigate.They liked the clearer menu presentation and the range of adjustments. French subtitles were available in the build they played; they do not establish the availability of a French voice track.
• Flight and FPS difficulty could be chosen separately.They explain the attraction of lowering one while keeping the other demanding. They also describe being able to change difficulty during play, rather than being stuck with an opening choice.
• The sound made the opening feel more forceful.Passing ships, gunfire and explosions were particular highlights. Quieter conversations aboard the Idris also helped create a place worth listening to.
• Faces looked improved from the 2024 demonstration.The discussion praises greater detail and more convincing facial presentation. This is their visual comparison, not a claim that every character has received a particular technical replacement.
• The on-rails battle felt better paced.They describe a shorter sequence, more debris and assistance from allies, allowing the scene to advance without requiring the player to finish every target alone.
• Tutorial interruptions were a frustration.An explanatory screen could cut across a moment that had built a strong atmosphere. Their preference was for instruction that felt more naturally part of the action.
• Performance praise came with conditions.The conversation describes broadly fluid play on powerful event hardware, alongside less smooth cinematic moments. That is useful testimony about the session, not a substitute for release benchmarks.

Karolinger’s enthusiasm came with a specific bug list

Karolinger played with mouse and keyboard on Wingman difficulty. His written account praises responsive combat and clearer flight interfaces, while recording faults serious enough to require reloads and staff help.

• Combat:enemy revives and damage to armour helped encounters feel active.
• Localisation:German menus, signs and subtitles accompanied English voices, with some missing strings.
• Recovery:progress survived the restart, but repeating unskippable scenes was frustrating.
• Scope:he played selected sections and later watched a separate developer demonstration.
• Video:his presentation uses archival 2024 footage; it is not a recording of the new hands-on session.

Two backers add a quieter perspective

The creator videos are only part of the weekend’s response. Two detailed written accounts explain why a comparatively directed campaign can still feel absorbing—and why enjoying five hours does not settle every question about the finished game.

The disagreements tell us more than a score would

The most useful question is not whether Manchester produced enough glowing quotes. It is whether these accounts help someone decide what sort of game they are looking at.

A slow opening can be absorbing and still feel slow

There is no need to choose between the people who enjoyed wandering the ship and those who wanted the campaign to move along. Both responses make sense. A naval adventure needs time to introduce its crew, establish routines and make a posting feel like somewhere worth returning to. It also needs to give the player enough agency that those introductions remain engaging.

For readers who relish character conversations and exploring a detailed setting, that slower pace may be a major attraction. Anyone hoping for near-continuous sorties or firefights should pay particular attention to the accounts above. Enjoying Star Citizen does not automatically mean wanting the same thing from a single-player campaign.

Strong combat does not excuse unclear instruction

A dangerous enemy and an unclear control prompt create very different kinds of difficulty. The former can make a victory satisfying; the latter can leave a player wondering what the game expected. That distinction is especially important in an opening intended to welcome people who have never touched the Persistent Universe.

The practical question for release is how reliably Squadron 42 teaches its own systems. A newcomer should be able to learn through the game, without having to know a Star Citizen keybind already or ask a developer standing nearby. That is where specific feedback about the spacewalk, equipment screens and early encounters is more helpful than another argument over whether the game looks impressive.

One successful session cannot speak for every PC

These reports offer a reason to be interested, not a hardware buying guide. Even within an organised event, players describe different faults and different impressions of responsiveness. The sensible next step for anyone judging performance is to wait for repeatable testing across released hardware configurations and a release build.

Nor can a selected handful of missions tell us whether the campaign sustains its momentum, pays off its characters or stays technically dependable from start to finish. Those are questions for a full review. The weekend has made the game easier to discuss in concrete terms; it has not made those questions disappear.

A campaign worth being curious about

For us, the appeal of Squadron 42 has always included the chance to inhabit this universe at a more personal scale: a berth aboard a warship, a wingman whose voice becomes familiar, a mission that gives the next launch a purpose beyond filling a cargo hold. The reactions from Manchester give that prospect more substance.

They also give the developers a demanding list of things to get right. Beautiful scenery cannot rescue a broken encounter, and a likeable crew cannot make every long conversation interesting. We want the final game to earn the hours it asks us to spend with it. There is enough enthusiasm here to make that an exciting prospect, alongside enough specific criticism to keep expectations grounded.

New to the two games? Our Star Citizen vs Squadron 42 guide explains the campaign, multiplayer universe and how they relate. For the release announcement, see Squadron 42’s arrival on Steam.