Skip to content

Best Neverness to Everness Settings for Performance (2026)

Neverness to Everness best settings for PC, Android and iOS. A tier-by-tier graphics table, the real frame cost of Lumen and ray tracing, upscaler and VRAM guidance, mobile presets, and a repeatable way to test your own build.

Gamermir Editor
Published Nov 14, 2026Updated Nov 20, 2026

Neverness to Everness runs on Unreal Engine 5 with Lumen lighting, and that pairing explains most of what people complain about: beautiful city blocks, sharp dips when traffic and reflections stack up, and frame times loose enough to make aiming feel vague. The PC build lists DirectX 11 as its floor and DirectX 12 as the recommendation, and version 1.5 added AMD FSR 4 next to DLSS. What follows is the order to change things in, split by hardware tier, with the measured cost of every expensive switch.

Quick Settings Cheat Sheet

Change these eight first. They carry most of the frame rate you can win without touching anything else.

SettingSet It ToWhy

Graphics Quality

Lowest preset

Drops the costly passes in one click; raise single items afterwards

Upscaler

DLSS or FSR 4 on Quality

Cheapest frames available, with the least softness at 1080p and up

Frame Generation

On for low and mid tier

Restores playable frame rates; costs latency, so high tier can skip it

Global Illumination

Off on low tier, On above

Lumen is worth roughly a third of your frame rate at 1440p

Reflections

SSR on low and mid, Lumen on high

The Lumen version measured 28 frames behind SSR

Texture Mapping

Medium on 6 to 8 GB, High on 10 GB plus

Very Low frees about 1.2 GB of VRAM but flattens surfaces

Frame Rate

60 on 60 Hz, 120 on high refresh

A cap steadies frame times; the engine stops at 120

Motion Blur

Off

Free readability, and it costs nothing in frames either way

Spend whatever headroom is left on Material and Foliage before View Distance. The detail sliders are cheaper than they look on this engine.

Understanding Neverness to Everness's Performance

Two bottlenecks dominate. In dense districts the CPU is feeding simulated traffic and pedestrians, which is why the city centre stutters more than the outskirts; the Traffic slider under Settings › Others is a direct lever on that load. On the GPU side, Lumen lighting and Lumen reflections are per-pixel work that scales with resolution, so a 1440p display can lose a third of its frame rate to two menu items. VRAM is the third constraint: at 1440p with high textures, usage sat near 9.9 GB on a 12 GB card, and dropping textures to Very Low pulled it back to about 8.6 GB.

  • Stutter is usually streaming or VRAM, not raw GPU speed. Install on an SSD and keep textures inside your card's budget.
  • Low frame rate in the open city is usually CPU. Cut Traffic, then Foliage, before you touch lighting.
  • Sudden drops after an hour of play point at the memory leak the developers have acknowledged for some configurations; restarting clears it.

Official requirements, for reference:

PlatformMinimumRecommended

PC

Core i7-10700, GTX 1660 or RX 5600, 16 GB RAM, Windows 10 64-bit, DirectX 11

Core i7-12700, RTX 3060 or RX 6700, 32 GB RAM, DirectX 12

Android

Snapdragon 855 or Dimensity 8000, Android 10 or newer, 20 GB free

Snapdragon 8 Gen 2 or 8 Gen 3, Dimensity 9200 or better

iOS

iPhone 12 Pro Max, iOS 15 or newer, 20 GB free

iPhone 14 Pro or newer, iOS 17 or newer

Storage needs a decision before download: the store page asks for 110 GB, while the launch FAQ asks for 60 GB free plus another 60 GB temporarily during extraction. Plan for 110 GB. No official AMD CPU pairing exists for the minimum spec, so a Ryzen 7 3700X class chip is the usual stand-in.

Working tiers look like this. They are reference builds for reading the tables below, not official requirements.

TierGPUVRAMCPUTarget

Low

GTX 1660 or RX 5600 class

6 GB

Core i7-10700 class

1080p, 60 FPS

Mid

RTX 3060 or RX 6700 class

8 to 12 GB

Core i7-12700 class

1080p, 120 FPS

High

RTX 4070 Ti and above

12 GB plus

12th gen i7 or better

1440p, 120 FPS

Best Graphics Settings

The strategy is simple: cut lighting and effects, protect textures and resolution until VRAM forces your hand. Preset names have moved between builds — the bottom option has shipped as Performance and the top as either Cinematic or Extreme — so match by position in the list, not by label.

SettingLow-EndMid and HighWhy

Graphics Quality

Lowest preset

Balanced to top preset

Sets a base for every slider; start low, then lift items

Resolution

1920x1080

Native, or 2560x1440

Fill rate scales almost linearly, so this is the first lever

DLSS Super Resolution

Performance

Quality or DLAA

Performance for 6 GB cards; Quality keeps detail at 1440p

FSR 4

Performance

Quality

Added in 1.5 for cards without DLSS

Anti-Aliasing

TAA

DLAA or TSR

DLSS overrides this item and greys it out

Rendering Accuracy

High

High

Internal render scale; lowering it softens the whole image

Frame Rate

60

120

Cap just under your sustained average, not above it

Texture Mapping

Low to Medium

High

VRAM only, with a visible payoff; see the deep dive

Material

Medium

High to Ultra

Below Medium, shadows and reflections read flat

Foliage

Very Low

High

Dense greenery and alpha effects eat fill rate

View Distance

High

High

Cheap here, and it decides whether landmarks pop in

Post-Processing

Low

Medium to High

Bloom and depth of field blur what you are aiming at

Global Illumination

Off

On

The single most expensive switch on the page

Reflections

SSR

Lumen

SSR looks flatter but is far cheaper

Ray Tracing

Off

Off, or Ray Tracing on 4080 and up

Full ray tracing cut frames to a quarter in testing

Ray Tracing Reflection Reconstruction

Off

On only with ray tracing

Cleans up RT reflections; pointless on its own

Frame Generation

On

Off

Buys frames for latency; high tier does not need it

V-Sync

Off

On only if you hold 120

Adds latency the moment you drop frames

Motion Blur

Off

Off

Readability only, no frame cost

Traffic

Very Low

High or Ultra

Cuts NPC and vehicle simulation in crowded areas

Pro Tip: Do not lower View Distance to fix city stutter. In a controlled run it moved frame rate by 4 to 5 frames between High and Low, while the pop-in made the skyline look broken. Cut Traffic instead — that is the slider actually driving the crowd simulation.

Key Setting Deep Dives

Global Illumination, Reflections and Ray Tracing

Global Illumination is the Lumen switch, and reflections decide whether Lumen or screen-space tracing handles them. Both are gorgeous and both are heavy: turning Lumen off moved a 1440p test from 80 to 105 FPS, roughly a 30 percent gain, and switching reflections from Lumen to SSR added 28 frames on the same scene. That is the whole reason the low tier turns both off rather than shaving Foliage by one notch.

Ray tracing is a separate tier again. Full ray tracing ran at 26 FPS where ray tracing alone ran at 43 and lighting fully off ran at 92, so treat the top option as reserved for RTX 4080 class cards at 1080p or with an aggressive upscaler. The reflection reconstruction toggle only exists to clean up ray-traced reflections; leave it off if ray tracing is off.

If you have a 30 or 40 series card and a mid-tier CPU, the honest order is Off for Global Illumination, SSR for reflections, and no ray tracing at all. The city already looks good without them, and the frames buy you a stable cap.

DLSS, FSR 4 and Frame Generation

Upscaling is the best value on the menu. On a 1440p test rig, DLAA ran at 26 FPS, Quality at 48, Balanced at 58 and Performance at 68 — Performance nearly tripled the native-AA result, which is why 6 GB cards should not be shy about it. At 1080p the softer modes cost more visible detail, so Quality is the better default there; at 1440p, Balanced is a defensible middle.

Version 1.5 added FSR 4 on PC plus RTX Spark support, so AMD cards are no longer stuck with TAA. Anti-Aliasing greys out once DLSS is active, which trips people up: you cannot stack DLAA with DLSS Performance. If the image looks mushy at 1080p, drop one upscaler step before you touch Rendering Accuracy.

Frame Generation is the opposite trade. It lifts the displayed frame rate while adding a small amount of input latency, so it belongs on low and mid tier machines that are short of playable frames, and it should be off on a high tier build that already holds 120. On 40 series cards, the official troubleshooting advice for crashes is to turn Frame Generation off first.

Texture Mapping and the VRAM Budget

Texture Mapping is a memory setting, not a look setting, which is why the right value depends on your card rather than your taste. Very Low held about 1.2 GB less than High in a 1440p test — 8.6 GB against 9.9 GB — so it is a real fix on 6 to 8 GB cards, and wasted image quality on 12 GB and up.

Material is the slider people sacrifice too early. Below Medium the shadows simplify and the image goes flat, and since it is far cheaper than lighting it is the last of the three detail sliders you should cut. On 10 GB and above, Material at High or Ultra is affordable next to Lumen.

If you see hitching that only appears after a few minutes in a new district, drop Texture Mapping one step and re-test before blaming the GPU. That pattern is the classic over-budget-VRAM signature.

Visibility, Post-Processing and Camera

Frame rate is only half of readability. These settings decide whether you can pick a target out of a neon-lit street.

SettingRecommendedWhy

View Distance

High on every tier

Cheap, and low values produce visible pop-in

Post-Processing

Low on low tier, Medium or High above

Bloom in the rain plus depth of field hides small targets

Motion Blur

Off

Smears a moving camera; costs no frames either way

Sharpening

Low

Recovers softness from upscaling; heavy values create halos

Brightness

Match your room, not a number

The game's neon lighting punishes a bright panel

Frame Rate

60 or 120, never unlimited

Steadier frame pacing means steadier aim

The engine caps at 120 FPS with options at 30, 60 and 120, so a 240 Hz panel will not go past 120 here. Set the highest cap your average actually holds. A 60 cap removed repeated stutter on a 12 GB RTX 3060 in one documented run, which is a reminder that a stable 60 beats a swinging 90.

Latency and Frame Pacing

Cap and pacing do more for how the game feels than any single visual slider.

  • Cap below your average. A 120 cap on a machine averaging 105 produces repeated frame drops; a 60 cap on the same machine is smooth.
  • Skip V-Sync while you are below your refresh rate. It adds latency precisely when frames are scarce. Above 100 FPS on a 120 Hz panel it is a reasonable anti-tear choice.
  • Turn Frame Generation off for competitive play. The added latency is small but real, and it is the first thing to cut if inputs feel heavy.
  • Keep the install on an SSD. Streaming hitches read as input lag because the frame never arrives.

The V-Sync question splits by hardware, and both positions are defensible: off for the lowest input latency at 60 to 90 FPS, on for a tear-free image once you hold 120.

Android and iOS Settings

Mobile drops DLSS, ray tracing and Frame Generation entirely; you get the preset, anti-aliasing, rendering accuracy, texture, foliage, view distance and post-processing. The fight there is thermal, not raw GPU power, so aim for a cap the phone can hold for thirty minutes.

SettingLow-End PhoneHigh-End Phone

Graphics Quality

Custom

Custom

Anti-Aliasing

TAA

TAA

Rendering Accuracy

High

High

Frame Rate

30

60

Texture Mapping

Low

Ultra

Texture

Low

High, only with 8 GB RAM or more

Foliage

Medium

High

View Distance

Medium

Ultra

Post-Processing

Low

Low

Motion Blur

Off

Off

Two notes that matter more than the table. Textures at High are not worth it under 8 GB of RAM — the stutter that follows is memory pressure, not a slow chip. And the 30 FPS cap on older hardware is not a compromise you can argue your way out of; Snapdragon 8 Gen 2 class devices are the realistic floor for a locked 60, while a stable 90 has been demonstrated on Snapdragon 8 Elite Gen 5 hardware, which needs both the chip and a display that supports it.

System and Driver Tweaks

Four changes, all reversible, none of them touching game files.

  • Install on an SSD. This is the official fix for streaming stutter and the cheapest upgrade most people can make.
  • Set virtual memory to 1.5 to 2 times your physical RAM if you have 16 GB or less. Official guidance, and it prevents the hard stalls that look like a crash.
  • Turn Frame Generation off if the game crashes on a 40 series card. Also official advice, and it usually resolves the startup crash.
  • Leave the game files alone. The anti-cheat is kernel level, and there is no official list permitting config edits or mod loaders. Edited files are not worth the account risk, and no third-party optimizer is either.

Back up any configuration you change at the driver level before you change it, and note the version you were on. Version 1.5 changed rendering support, not the settings menu, so advice written before it may still name options that have moved.

How to Test Your Settings

  1. Pick one repeatable route through a crowded district and one indoor area. Do not test in the tutorial zone.
  2. Record average FPS and 1% low — the slowest 1 percent of frames, which is what you actually feel — for two minutes on that route.
  3. Drop every setting to its lowest value and record the ceiling. That number is your hardware's limit; if it is below 60, no menu setting will save you.
  4. Raise one group at a time: lighting first, then textures, then detail. Note the frame cost of each group.
  5. Keep a group only if it costs less than about 10 percent of your frames and changes what you can see.

Targets by display: a 60 Hz panel wants a locked 60, a 144 Hz panel wants 120 to 144 but will sit at the 120 engine cap here, and a 240 Hz panel gains nothing in frame rate — only in pacing consistency, which is still worth having. Test after every patch; 1.5 shifted rendering support, and driver updates move these numbers too.

More games to download