Par Online Games VIP Editorial
·
IGN reports crashes, freezes, stutters, and frame drops in Star Wars: Zero Company across several PC setups, even after a day-zero patch.
IGN's Jacqueline Thomas reports that Star Wars: Zero Company has produced a wide range of technical problems during her early PC testing, including crashes, freezes, microstutters, driver failures, and lost progress. The issues appeared across several systems rather than being limited to one graphics card, operating system, or performance tier.
Thomas says she has spent about five hours with the game and is enjoying its turn-based design and story despite the instability. IGN's report is an analysis of that testing, not an OnlineGamesVIP hands-on verdict. It also notes that IGN reviewer Dan Stapleton has not encountered the same depth of problems, so the reported experience is not presented as universal across every PC.
The immediate PC takeaway is that performance and reliability may vary sharply between configurations. IGN's testing covered a high-end Razer laptop, a Lenovo Legion Go 2 running Bazzite, a Steam Machine, and a powerful desktop with an RTX 5090. Even after Bit Reactor released a day-zero patch, Thomas says crashes, freezes, and frame drops continued to occur.
IGN's Jacqueline Thomas began testing Star Wars: Zero Company on a Razer Blade 16 equipped with an RTX 5090 and a Ryzen AI 9 HX 370. At 1600p, the laptop achieved what she described as a decent average frame rate, but that result was accompanied by noticeable microstutters, particularly during cutscenes.
Thomas also reports driver crashes on the Razer laptop. In the most severe example, attempting to load the game caused the laptop to restart. IGN's report says this behavior did not occur with other games on that system at the time of testing. The account does not identify a specific driver version or confirm whether the restart was caused by the graphics driver, the game, or another software interaction.
The Lenovo Legion Go 2 presented a different challenge. IGN's Thomas was running Bazzite, a Linux-based operating system, and found that the game required 800p resolution and the lowest settings to reach a playable frame rate. Under those conditions, she reports approximately 25 to 30 frames per second.
Thomas says that frame rate was acceptable to her for a turn-based game, but crashes made the handheld experience much more serious. The game reportedly locked up at the end of a mission, forcing a hard restart and costing her progress. IGN's report says this happened four times before she stopped using that setup for the game.
On a Steam Machine, Thomas encountered a crash on the same level. In that case, IGN says the system produced an error report that could be sent to the developer. Thomas suggests the Linux environment may be connected to these particular failures, but the report does not establish that as a confirmed cause.
Her desktop test used an AMD Ryzen 7 9850X3D, 32GB of RAM, and an RTX 5090. With the game at 4K and Ultra settings, DLSS set to Quality, and frame generation disabled, IGN reports a performance range of about 70 to 80 frames per second. Thomas describes that result as playable, but says the game froze during the middle of a turn in her first mission on the desktop.
The reported problems matter because they do not follow a simple low-end versus high-end pattern. IGN's Jacqueline Thomas saw reduced performance on a handheld, but also experienced crashes and a freeze on systems with much more capable hardware. That distinction is important for PC players: buying or using a faster graphics card may improve frame rate, but IGN's testing does not show that it guarantees stability.
Operating system support is another relevant variable. The Legion Go 2 and Steam Machine tests were conducted with Linux-related setups, and the failures on those systems may involve compatibility layers or platform-specific behavior. However, IGN's report does not name the exact compatibility technology, configuration, or Linux component responsible. It would be premature to treat Linux as the sole explanation for all of the crashes.
The Razer Blade 16 result also shows why average frame rate alone is not enough to judge a PC release. IGN reports a decent average at 1600p, yet the same test included microstutters and driver-related restarts. A player can therefore have an apparently strong performance result while still facing problems that affect loading, cutscenes, or the ability to launch the game reliably.
On the desktop, the reported 70 to 80fps result at 4K with Ultra settings indicates that the game can deliver a playable frame rate on very high-end hardware under the tested settings. It does not establish a recommended specification, a universal 4K target, or a guarantee that similar systems will perform identically. IGN's account connects that result with a freeze during play, which makes frame rate only one part of the PC experience.
Thomas also places the game in a wider discussion about Unreal Engine 5. In IGN's article, she argues from her own recent PC testing that several games not using Unreal Engine 5 ran well across a broad range of hardware, while Star Wars: Zero Company and another example, Halo: Campaign Evolved, reinforced her criticism of Epic's engine. That is her analysis, not a confirmed statement from Bit Reactor or Epic that the engine caused the reported problems.
IGN's Jacqueline Thomas says Bit Reactor released a day-zero patch intended to fix some problems. The source does not list the patch's version number, release date, individual fixes, or supported platforms. It also does not provide a developer explanation for the remaining crashes, freezes, stutters, or frame drops.
That missing information limits what PC players can conclude from the report. The patch shows that post-launch technical work is already taking place, according to IGN, but it does not show how many reported issues were addressed or whether the fixes apply equally to Windows, Linux-based setups, handheld devices, and desktop configurations.
IGN's report also does not provide a repeatable benchmark suite. There is no comparative table covering multiple resolutions, graphics presets, processor classes, or graphics cards. The published testing is useful as a record of problems encountered on named systems, but it should not be treated as a complete performance guide.
Players should also separate progress loss from ordinary frame-rate dips. A lower frame rate may be manageable in a turn-based game, as Thomas notes in her discussion of the Legion Go 2. A crash at the end of a mission is more disruptive because it can remove completed progress and require a hard restart. Those are different categories of issue, and the source provides evidence for both.
Analysis: Before buying or committing to a long campaign, PC players should verify the game's current stability on their exact hardware and operating system. IGN's testing suggests that the same title can behave differently on a laptop, handheld, Linux-based machine, and high-end desktop. The report does not support assuming that one successful test, or one failed test, predicts every setup.
Players should first check whether their operating system and device configuration are officially supported, because IGN's source text does not establish the status of Bazzite, the Steam Machine setup, or other Linux configurations. If a player uses a handheld, the reported 800p and lowest-settings test provides a reference point from IGN, but not a guaranteed target for another device. The 25 to 30fps figure belongs to Thomas's Legion Go 2 testing and should not be generalized to all handhelds.
It is also worth checking whether a current patch has installed before beginning a serious play session. IGN says Bit Reactor's day-zero patch addressed some problems, while Thomas continued to see technical failures afterward. That means the patch is relevant context, but not proof that the game is stable on every PC.
For anyone testing the game, frequent manual saves are a sensible precaution if the game allows them. This is practical advice based on IGN's report of lost progress after mission-end crashes, not a confirmed workaround from Bit Reactor. Players should avoid treating it as a fix for lockups or driver restarts.
Finally, frame-generation and upscaling settings should be evaluated separately from stability. IGN's desktop result used DLSS Quality with frame generation disabled, and the article does not compare that configuration with frame generation enabled. Players should therefore avoid assuming that changing either setting will resolve crashes, freezes, or driver problems.
The supplied catalog does not include Star Wars: Zero Company, so it cannot be linked as a playable catalog entry here. For players looking for other Star Wars games in the catalog, Star Wars: Episode I: Racer and Star Wars: Rogue Squadron are relevant alternatives. Their inclusion does not indicate that they share Zero Company's PC issues or offer the same turn-based format.
What remains unknown
IGN's Jacqueline Thomas expects Star Wars: Zero Company to become more stable over time, but the source does not provide a timetable for future updates. There is no confirmed information here about the next patch, the number of affected players, the frequency of the reported failures outside Thomas's testing, or Bit Reactor's diagnosis of the problems.
The report also leaves several practical questions unanswered. It does not specify the game version used for every test, identify the graphics driver involved in the laptop restarts, explain the exact Linux compatibility setup, or establish whether the mission-end crash is tied to one level. It does not confirm whether the same issues affect console versions or other platforms, either.
Those details are worth watching because they would help separate isolated configuration conflicts from broader PC problems. Until that information is available, the clearest confirmed picture comes from IGN's testing: Star Wars: Zero Company can run at a playable frame rate on powerful hardware, but technical reliability has varied across the tested systems, and a day-zero patch has not eliminated every problem reported by the publication.