System requirements
For best gaming experience
while exploring Star Citizen
I would like to remind you that it is not advisable to set up a specific configuration for Star Citizen while the game is still in its Alpha phase, especially since such a configuration can quickly become obsolete. However, if you are considering purchasing a new PC or upgrading your current PC and would like to take advantage of the Alpha version, please find below the minimum and recommended specifications provided by CIG.
The "minimum" configuration should allow you to run the game, but it is very demanding and may quickly prove to be limited. I recommend that you aim for the "recommended" configuration for the best experience.
For example, 16 GB of RAM is the "vital" minimum to run the game, but it is better to consider 32 GB.
As with the GPU, it is better to opt for a card with 6 or even 8 GB of VRAM.
SSD support has long been recommended, and today it is a prerequisite. The game continues to grow in size, and while 80 GB used to be sufficient, it is now necessary to have 150 GB of free space, or even double that if you plan to use PTU in addition to LIVE (note that PTU and LIVE can be installed on different drives if necessary).
Some will tell you that it is advisable to place the game on a different medium from the operating system, but this is not an exact science. You will probably find plenty of advice online on how to optimize the game and the hardware configuration to use.
For example, personally, I struggled with a performance issue on the game for several years. It was an increasingly frequent problem that greatly affected the gaming experience, as it took the form of freezes lasting from a few microseconds to several seconds, making FPS gameplay impossible, as well as certain actions in the ship.
From simply tweaking settings to replacing hardware, I tried everything, even completely changing my configuration, without ever being able to get rid of the problem. Nothing was more frustrating than launching the game on a brand new configuration and finding that the bug was still there. The only thing I had never changed was the operating system. Although it was continuously updated, I had stayed with Windows 10. The day I decided to switch to Windows 11, the problem miraculously disappeared...