iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
There is no verified best-settings preset for Squadron 42 yet. Steam currently lists a planned Q2 2027 release, and Roberts Space Industries (RSI) said in a February 2026 support article that the game was still in development and unavailable to download. That means no one can honestly publish tested Squadron 42 frame rates, image-quality comparisons or a guaranteed ultra/high/medium preset today.
You can still prepare a sensible starting point. Use your monitor’s native resolution, keep the game’s own render-resolution or upscaling option at its best-quality mode when you need more GPU headroom, and lower texture quality or output resolution only when the eventual in-game VRAM estimate indicates that your graphics memory is close to its limit. This is a cautious extrapolation from RSI’s Star Citizen graphics guidance, not a test of Squadron 42. The final menu may expose different options, and its performance may change substantially between development builds and release.
What can actually be known about Squadron 42 settings today
The central limitation is testability. The title is not currently available to download, so there is no representative retail build on which to compare presets or measure frame-time consistency. A planned release window is not a performance promise: Steam’s Q2 2027 date can move, and the hardware requirements and menu options can change before launch.
Do not treat settings guides for Star Citizen as measured Squadron 42 advice. The two games share technology and are both made by CIG, but a support article written for one title does not prove that the other has the same graphics menu, upscalers, shader compilation behavior, CPU load or performance profile.
#1 Best Overall
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
For now, the useful answer is a method rather than a magic preset: establish that your PC meets the published minimum, begin at native display resolution, use only the upscaler that is actually present in your build, watch the game’s VRAM estimate if one is provided, and change one variable at a time.
Published requirements are not performance recommendations
Steam and RSI publish overlapping but not identical requirement lists. Steam’s game-specific listing is the clearest current source for Squadron 42, while RSI’s December 17, 2025 article describes broader CIG requirements. Neither list promises a frame rate, a resolution, a quality preset or a particular level of image quality.
| Item | Steam Squadron 42 listing | RSI broader CIG guidance (December 17, 2025) | How to interpret it |
|---|---|---|---|
| Operating system | Windows 11 | Windows 10 or Windows 11 | Use the game-specific listing as the more conservative target, and recheck it when the release build is published. |
| Processor | Quad-core Intel Core i7, Sandy Bridge or later, or AMD Bulldozer or later | Quad-core CPU with AVX, AVX2 and FMA3 | A qualifying CPU may still become the limiting part in complex scenes; a minimum specification does not define a target frame rate. |
| Memory | 16 GB RAM | 16 GB or more RAM | Keep other applications closed when testing so the game has as much system memory as possible. |
| Graphics memory | DirectX 11.1-compatible graphics card with 8 GB VRAM | DirectX 11.1 graphics card with 4 GB RAM | For this title, use the current Steam figure of 8 GB VRAM as the relevant game-specific minimum. It is not a recommended GPU tier. |
| Graphics API | DirectX 12 | DirectX 11.1 graphics capability | The final executable and driver requirements take precedence over either preliminary list. |
| Storage | 150 GB available | 150+ GB SSD | Reserve more than the stated allowance for patches and temporary files; an SSD helps load and streaming behavior, not a graphics-setting quality level. |
The apparent graphics-memory discrepancy is why the two lists should not be blended into a single “recommended” specification. The Steam listing says 8 GB VRAM for Squadron 42; RSI’s broader article mentions a 4 GB graphics-memory figure for CIG games. Until an updated, title-specific list replaces them, treat the Steam requirement as the safer baseline for this game and expect the requirements to change.
A provisional starting profile (not a tested preset)
The following sequence is deliberately conditional. It tells you what to try when the final game is available; it does not claim a measured frame rate or guarantee that every control will exist.
1. Select the monitor’s native resolution
Set the display resolution to the panel’s native value first. RSI’s graphics guidance for Star Citizen notes that resolution has a large effect on GPU and VRAM use. Native rendering preserves the intended sharpness and interface scale, giving you a clean baseline before you trade image detail for performance.
Rank #2
- QHD Resolution (2560 x 1440) has 1.7 times the pixel density of Full HD for incredibly detailed pinsharp images
- HDR10 provides brighter highlights and nuanced shadow for added depth - making every scene feel more vivid and realistic
- The 180Hz refresh rate minimizes lag for gameplay with ultra-smooth action. Plus, the 1ms response time helps capture your moves in real-time, allowing you to react fast for gaming precision
- AMD FreeSync reduces choppiness, screen lag and image tearing, ensuring that your fast-paced, complex in-game action is stable with minimal stutter
- Ergonomic stand allows for tilt, pivot and height adjustments to maximize gaming comfort
If the game cannot hold an acceptable frame rate at native resolution, reduce render resolution or enable an in-game upscaler only after confirming that the option is available in your Squadron 42 build. Do not assume a setting name, quality slider or reconstruction method from another title.
2. Use the available upscaler at its highest-quality mode first
RSI’s Star Citizen article says DLSS is recommended for Nvidia graphics cards and CIG-TSR otherwise. That statement concerns Star Citizen and does not confirm either option in Squadron 42. At launch, choose the upscaler that the game actually lists, then begin with its quality-oriented mode rather than the most aggressive performance mode. Compare fine geometry, faces, cockpit text and distant edges at native output resolution.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →If an upscaler introduces shimmer, ghosting or unreadable text, move back toward native rendering before cutting texture quality. A lower internal resolution can improve GPU load while preserving more texture detail than simply dropping every quality control.
3. Keep textures within the available VRAM budget
If the final menu exposes a VRAM estimate or warning bar, keep the estimate below the stated budget and leave room for Windows, capture software and streaming tools. RSI describes its in-game bar as an estimate of use for the selected resolution and graphics settings, not a promise of exact allocation.
Texture quality is usually the most direct control for reducing VRAM pressure, so lower it only when the indicator approaches its limit, when you see texture pop-in, or when the game reports an allocation warning. Lowering textures can make surfaces visibly softer; it is not a free performance gain when the GPU is actually compute-limited.
Rank #3
- Smooth motion: 240Hz refresh rate and fast 0.5ms response time provide crisp visuals and fluid movement with less input lag.
- Seamless gaming: FreeSync Premium and HDMI VRR eliminate tearing for smooth, responsive PC and console gameplay.
- Fast IPS: Faster 0.5ms response with excellent color accuracy across wide IPS viewing angles.
- Rich color: 99% sRGB color coverage delivers vivid, detailed imagery with strong accuracy.
- Eye comfort: TÜV Rheinland 3‑star certified display lowers blue light while preserving color quality.
4. Change one expensive control at a time
The release menu may include shadows, volumetric effects, reflections, ambient occlusion, draw distance or similar controls, but their names and costs have not been documented for Squadron 42. If those controls appear, record the original value, lower one setting, repeat the same scene and compare frame-time behavior. This prevents a broad preset change from hiding which option helped and which one damaged image quality.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
First-launch workflow for a reproducible setup
- Update the platform. Install the game on a current 64-bit Windows installation that satisfies the final published requirements. Update the graphics driver through the GPU manufacturer’s normal channel and reboot before testing.
- Install to an SSD with room to spare. Steam lists 150 GB of available space, while RSI’s broader guidance calls for a 150+ GB SSD. Leave additional free capacity for updates, shader caches and temporary files; do not treat the storage figure as a frame-rate recommendation.
- Close competing workloads. Exit browsers with many tabs, game launchers you do not need, virtual machines and background recording applications. RSI specifically advises leaving VRAM room for software such as recording or streaming tools.
- Run the first pass at native resolution. Choose the display’s native output and the default quality profile. Let shaders or other first-run compilation complete if the game performs it, then use the same save, mission section or benchmark route for later comparisons.
- Check the performance overlay. Record average frame rate only alongside frame-time consistency, GPU utilization, CPU utilization and VRAM use. A high average can still feel uneven if frame times spike during traversal or combat.
- Identify the limiting component. If the GPU is close to full utilization while the CPU has headroom, resolution, upscaling or GPU-heavy effects are the first variables to test. If one or more CPU threads are saturated while GPU utilization falls, lowering resolution may do little; look for a CPU-oriented setting if the menu provides one and reduce background work.
- Try the game’s own upscaler. Enable only an option confirmed in the Squadron 42 menu. Start with its quality mode, inspect motion and text, and then compare frame times in the identical scene.
- Reduce output or render resolution if necessary. Make a small change, such as one available step in the game’s resolution selector or render-scale control. Recheck image quality at the normal viewing distance rather than judging from a paused, zoomed screenshot alone.
- Lower textures only for VRAM pressure. If the VRAM estimate is near its limit, step textures down one level and restart the scene if the game requires it. Keep other settings unchanged so you can see the effect.
- Save a named profile. Record resolution, upscaler mode, texture level, other changed controls, driver version and the scene used. This makes later patches comparable and gives you a recovery point if a new build changes defaults.
How to improve FPS without making the game look bad
When the GPU is the bottleneck
GPU limitation is indicated by sustained high GPU utilization and frame times that improve when resolution or render scale is reduced. In that case, an available quality upscaler is usually the least disruptive first experiment because it keeps the output resolution and interface layout intact. If the image becomes unstable, return to native rendering and lower the most expensive effects exposed by the menu, one at a time.
Do not promise a fixed percentage gain from any change. The result depends on the scene, driver, resolution and final build, and no title-specific measurements are available yet.
When VRAM is the bottleneck
VRAM pressure can appear as allocation warnings, stutter when entering new areas, texture streaming problems or an estimate that exceeds the available budget. Reduce texture quality first if the game’s indicator identifies textures as the cause, then consider a lower render resolution. Keep headroom for recording, streaming and overlays rather than running exactly at the card’s nominal capacity.
When the CPU is the bottleneck
A CPU-limited scene may show a busy main thread and a graphics card that is not fully occupied. Lowering resolution in this situation often changes little because fewer pixels do not remove simulation, animation, streaming or draw-call work. Close background programs, use the game’s own CPU-related options if present, and test busy scenes separately from quiet corridors or menus.
Rank #4
- 27” 240Hz 1500R Curved FHD 1080P Gaming Monitor for Game Play.
- Prioritizes Gaming Performance: Up to 240Hz high refresh rate, more immersive 1500R Curvature, FreeSync, MPRT 1ms Response Time, Black Level adjustment(shadow booster), Game Modes Preset, Crosshair.
- Cinematic Color Accuracy: 130% sRGB & DCI-P3 95% color gamut, 4000:1 contrast ratio, 300nits brightness, HDR, Anti-flicker; Anti-Glare.
- Plug & Play Design: HDMI & DP1.4 & Audio Jack(No built-in speakers), durable metal stand, tilt -5°~15, VESA 100*100mm compatible.
- Warranty: Money-back and free replacement within 30 days, 1-year quality warranty and lifetime technical support. Pls contact SANSUI service support first if any product problem.
When frame rate is acceptable but motion feels uneven
Check frame-time consistency rather than relying on an average FPS number. Streaming, shader compilation, background capture and a CPU spike can create hitching even when the average looks healthy. Repeat the route after caches have settled, keep capture software disabled during the baseline, and compare the same camera movement after each change.
Practical profiles by situation
| Situation | Starting point | First adjustment | What to watch |
|---|---|---|---|
| Meets only the published minimum | Native resolution, default quality, no background capture | Use the available quality upscaler; then reduce render resolution if needed | VRAM estimate, stutter and frame-time spikes rather than a promised FPS target |
| GPU has headroom but VRAM is close to full | Keep resolution and effects unchanged | Lower texture quality one step | Texture sharpness, streaming behavior and whether the warning clears |
| High-end GPU but a busy CPU scene | Native resolution and high texture detail if VRAM allows | Close background tasks and test any CPU-oriented control in the menu | Main-thread frame time and GPU utilization |
| Image quality is more important than peak FPS | Native resolution with the least aggressive available upscaler mode | Lower individual effects only after checking frame times | Fine geometry, faces, cockpit text, motion stability and reflections |
| Recording or streaming while playing | Leave extra VRAM and system-memory headroom | Reduce upscaler or render resolution before cutting textures, unless VRAM is the warning | Capture overhead, encoder use and new stutter under load |
These are decision paths, not tested presets. A machine that exceeds the minimum may still be CPU-limited in a crowded scene, while a lower-resolution display may be GPU-limited for entirely different reasons.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common mistakes and how to recover
Assuming a Star Citizen option is guaranteed
DLSS and CIG-TSR are named in RSI’s Star Citizen guidance, but that does not establish that Squadron 42 includes them. If the option is absent, use the final game’s available scaler or render-resolution control instead; do not install unofficial replacements merely to reproduce a menu from another title.
Reading the minimum requirement as a target
The listed 16 GB of RAM, 8 GB of VRAM and 150 GB of storage describe a floor, not a promise of high settings or a particular frame rate. If performance is poor on a minimum-specification PC, that is not evidence that one hidden setting is wrong; the hardware may simply be operating at the lower boundary.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesLowering every setting at once
A global low preset can make the game look substantially worse without revealing which control mattered. Restore the default profile, change one setting, repeat the same test and keep a written record.
Best Value
- 1800R curve monitor the curved display delivers a revolutionary visual experience with a leading 1800R screen curvature as the images appear to wrap around you for an in depth, immersive experience
- Hdmi, VGA & PC audio in ports
- High refresh rate 75Hz.Brightness (cd/m²):250 cd/m2
- Vesa wall mount ready; Lamp Life: 30,000+ Hours
- Windows 10 Sceptre Monitors are fully compatible with Windows 10, the most recent operating System available on PCs.Brightness: 220 cd/M2
Running at an arbitrary non-native resolution first
This makes it harder to judge image quality and can introduce scaling artifacts. Establish a native-resolution baseline, then change internal resolution or upscaling with the output resolution held constant when the game supports that separation.
Ignoring patches
Development builds can alter shaders, streaming, defaults and requirements. After a major update, retest the same scene and confirm that your saved profile still uses the intended resolution, upscaler and texture level.
Storage and system-readiness note
An internal SSD is a sensible preparation because the published guidance calls for an SSD and at least 150 GB of available space. It can reduce loading and asset-streaming friction compared with a hard drive, but it does not turn a minimum graphics card into a faster one and it is not a substitute for adequate VRAM or CPU capability. Keep free capacity available for patches and avoid filling the drive to its limit.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What to verify when Squadron 42 releases
Before treating any guide as definitive, check the live Steam listing and the current RSI support documentation for the operating-system, CPU, memory, graphics, API and storage requirements. Then verify the actual in-game menu: available upscalers, render-scale behavior, texture limits, frame-rate controls, HDR or display options and any VRAM indicator.
A trustworthy post-release comparison should use the same PC, driver, resolution, scene and camera path for every profile. It should report frame rate together with frame-time consistency, image quality at the target resolution, VRAM use and whether results change between GPU-limited and CPU-limited scenes. Until a representative build can be tested that way, the honest “best settings” answer remains a starting procedure rather than a numbered preset.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
