PC targets
What PC specs does Black Flag Resynced need?
The listed tiers scale from 1080p Low at 30 FPS up to 4K Ultra at 60 FPS. Start with the resolution and frame-rate target, then compare CPU, GPU, RAM, SSD, and graphics features.
| Tier | Target | GPU check |
|---|---|---|
| Minimum | 1080p, 30 FPS, Low | GTX 1660, RX 5500 XT, or Arc A580 |
| Recommended | 1080p, 60 FPS, Medium | RTX 3060, RX 6600 XT, or Arc B580 |
| High | 1440p, 60 FPS, High | RTX 3080 or RX 6800 XT |
| Ultra | 4K, 60 FPS, Ultra | RTX 4090 or RX 7900 XTX |
Requirement pattern
What every PC tier has in common
Even before choosing High or Ultra, the listed requirements point to a modern Windows PC with enough memory and SSD space for the remake.
Settings choice
Which PC tier should you start with?
Choose the tier closest to your GPU and monitor instead of starting at Ultra by default.
- Start at Minimum only if your GPU sits near GTX 1660, RX 5500 XT, or Arc A580 and you can accept 1080p Low at 30 FPS.
- Start at Recommended if your system is near RTX 3060, RX 6600 XT, or Arc B580 and you want 1080p Medium at 60 FPS.
- Start at High if your target is 1440p at 60 FPS and your GPU is near RTX 3080 or RX 6800 XT.
- Start at Ultra only if your GPU class is near RTX 4090 or RX 7900 XTX and you want 4K at 60 FPS.
Post-launch PC check
Use the frame-rate target before changing settings
A September update is a reason to recheck a stubborn performance problem, not a reason to copy a new preset without testing. Choose the display target, confirm the current store requirements, and change one graphics variable at a time.
Current build Title Update 1.0.7 Treat the official update notice as the point at which a persistent issue deserves a fresh comparison. Next handoff Confirm the platform Store, Steam Deck, and console status belong on the platform page.
- Record resolution, frame-rate target, GPU, RAM, and free SSD space before changing settings.
- If a route stutters, confirm the intended GPU and close capture or overlay tools before lowering every option.
- Drop one tier first, then retest the same city, sea route, or weather condition.
- Use the official or store listing for requirement changes; use this page for the decision between targets.
Performance interpretation
Will your PC run Black Flag Resynced at 60 FPS?
A requirement tier describes a target, not a guarantee for every scene. Match your monitor goal to the closest listed tier, then test a repeatable city or sea route before changing several settings at once.
- Record resolution, frame-rate goal, GPU, RAM, and available SSD space before installing.
- Use the listed GPU tier as a starting point, not as a promise for every weather or city scene.
- Change one setting and repeat the same route so the result can be compared.
- Check the official or store listing again when a patch changes requirements or compatibility.
| Your target | Start from | First safe adjustment |
|---|---|---|
| 1080p / 30 FPS | Minimum · Low | Keep the target and verify stability before raising effects |
| 1080p / 60 FPS | Recommended · Medium | Lower one expensive setting if the same scene dips |
| 1440p / 60 FPS | High · High | Compare resolution scale before dropping every preset |
| 4K / 60 FPS | Ultra · Ultra | Check GPU headroom and ray-tracing cost first |
| Steam Deck | Steam listing status | Confirm current compatibility before tuning a desktop preset |
PC buying and tuning
Read the requirement table as a target, then test one repeatable scene
Steam's current listing gives a concrete baseline: Windows 10 64-bit or Windows 11, 16 GB RAM, a 65 GB SSD install, and a Core i7-8700K/Ryzen 5 3600 with GTX 1660/RX 5500 XT/Arc A580 for minimum. The recommended list moves to an i5-10600K/Ryzen 5 3600 and RTX 3060/RX 6600 XT/Arc B580. Treat those as starting points for a target, not a promise for every city, storm, or ship encounter.
Steam listing Windows, CPU, GPU, RAM, SSD The Steam listing is the clearest current requirements reference and should be rechecked when the store page changes. Official feature Upscaling and frame generation Ubisoft's launch guide notes upscaling technologies, frame generation, software ray tracing for non-RT hardware, and handheld presets.
- Install to an SSD and leave room beyond the listed 65 GB so update and shader work are not competing with a full drive.
- Use the official CPU and GPU tier as a starting point, then record resolution, frame-rate target, and actual scene behavior.
- Change one setting per test; changing resolution, ray tracing, upscaling, and shadows together hides the real bottleneck.
- Ubisoft scopes the one-time online installation and offline-campaign statement to PC; test the same PC account and save after updates, and check console licence rules separately.
| Target | Official starting point | Expert test |
|---|---|---|
| 1080p / 30 FPS | Minimum tier, 16 GB RAM, SSD, GTX 1660-class GPU | Repeat one dense city and one open-water scene before raising effects |
| 1080p / 60 FPS | Recommended tier, RTX 3060/RX 6600 XT/Arc B580 class | Watch the same movement route and sea approach for frame-time dips |
| 1440p / 60 FPS | Use the High tier as the comparison point | Lower resolution scale or one expensive feature before dropping every preset |
| 4K / 60 FPS | Use the Ultra tier only with substantial GPU headroom | Check ray-tracing cost and sustained frame time, not a short menu scene |
| Steam Deck | Steam lists Verified and Ubisoft lists handheld graphics presets | Confirm the current store status and use the handheld preset before desktop tuning |
60 FPS troubleshooting order
Change the least destructive setting first
When a PC route stutters, lowering every option at once destroys the information needed to fix it. Start with the requirement target, then test storage, GPU load, resolution scale, ray tracing, and overlays in a controlled order.
- Use the Steam CPU/GPU tier to choose a starting preset, then test a dense city and open water.
- Keep resolution and target FPS fixed while changing one setting.
- Record whether the limit is GPU, CPU, storage, shader compilation, or an overlay before buying hardware.
- Recheck the store requirements after a large update; do not treat a launch screenshot as a permanent specification.
| Symptom | First check | Next change |
|---|---|---|
| Long loads or streaming hitch | Game is on the SSD and the drive has free space | Move the install or free space before lowering graphics |
| GPU-bound frame dips | Resolution, ray tracing, and upscaling target | Lower one expensive feature or resolution scale |
| City-only stutter | Same route, same weather, and background capture tools | Retest after closing overlays and recording software |
| Steam Deck black screen | HDR state and current patch | Apply the official 1.0.7-era fix path before changing presets |
| Unstable 60 FPS | Frame-time consistency rather than menu average | Choose a stable 30/40/60 target instead of chasing a peak |
Black Flag test card
Use the same four scenes before changing your whole preset
A requirement tier is a starting point, not a benchmark. Keep one short route card for the places that stress different parts of this game: a dense city, open water, a fort approach, and a boarding or memory transition. Repeat the same card after one setting change so the result stays useful.
- Save the test card beside the platform, driver, preset, and current build so a later patch can be compared with the same conditions.
- Use a stable frame target as the finish line. A steady 30 or 40 FPS route is a valid result when an unstable 60 FPS target makes sailing or combat harder to read.
- Change one variable per retry: resolution scale, ray tracing, upscaler mode, frame cap, overlay, or background task. Record the first change that improves the symptom.
- Once all four scenes pass, stop tuning and move to Walkthrough or Map. PC Specs should hand off to play instead of becoming an endless settings loop.
| Scene | Write down | Pass signal | If it fails |
|---|---|---|---|
| Dense city traversal | Resolution, frame target, route, and whether capture tools are active | The same rooftop or street line has no repeatable hitch | Check SSD space, overlays, and streaming before lowering every effect |
| Open-water sail | Weather state, camera direction, and target frame cap | The sea route remains stable while turning and approaching land | Test one expensive effect or cap change, then restore the rest |
| Fort approach | Distance to the fort, mortar use, and opening exchange | The approach keeps the chosen target without a sudden frame-time spike | Compare resolution scale or ray tracing while keeping the route fixed |
| Boarding or memory transition | Loading point, crowd or enemy density, and frame-time behavior | The transition and first close encounter stay responsive | Check background software and CPU or memory pressure before buying a GPU |
Performance comparison
Separate low frame rate from uneven frame delivery
A steady low frame rate and a mostly smooth route interrupted by hitches need different tests. Use a short repeatable route through a dense city such as Havana and a separate sailing segment. These are suggested comparison scenes, not measured benchmarks from this site.
Requirements Current Steam listing Compare official system requirements before buying hardware. Device Review platform limits Separate Windows PC, console, and Deck decisions.
- Write down resolution, preset, upscaler mode, frame generation state if available, and the route before changing anything.
- Frame budgets are 33.3 ms at 30 FPS, 25 ms at 40 FPS, and 16.7 ms at 60 FPS. These are 1000 divided by target FPS, not a claim that your system meets them.
- Restore a setting when the comparison does not help. A stable cap is a separate choice from reducing visual quality, and available caps depend on the device and display.
| What you observe | One useful comparison | What to conclude cautiously |
|---|---|---|
| Low FPS through the whole scene | Lower render resolution while keeping the route and other settings fixed | A clear improvement suggests GPU load matters; it does not isolate a single graphics option |
| Hitches only when entering a new area | Repeat the same short traversal after it has loaded | A smoother second pass points toward loading or compilation work, not necessarily insufficient average GPU speed |
| Hitches begin with capture or overlay software | Repeat once with that tool closed | Keep the change only if the same symptom improves |
| No useful change after reducing resolution | Restore the original value; check background load, memory, storage, and drivers | Do not buy a faster GPU from this one symptom alone |