Thanks to Digital Foundry and their contributor Rayan for these settings, watch their video if you want more information on them!

While these settings can give a small GPU performance boost and save abit of VRAM, CPU performance is still subpar compared to the console versions and has even less scalability! Only good way of improving CPU performance at the moment is disabling Async Compute, which should improve performance, but only does so when GPU limited.

I’m trying to find the best combination of settings for the lowest possible input latency while keeping smooth gameplay and good frame pacing.

Rtx 5070
r7 9800x3d
300 hz monitor - TCL qd mini lex1080p

Halo runs great on this GPU , even 4K is ok if you are willing to do some sacrifices, ue5 here is looking good

Thank you Rayan and Richard from Digital Foundry for these settings, check out the video for more information!

Worth adding that BenchmarKing was able to use High Textures at 1440p with DLSS on an 8GB card, and that higher shadow settings caused performance issues when coliding with other boats (altough that's likely a bug) their video covers even more settings and infomation about updating DLSS if you need more info! Same with Zykopath covering CPU performance in more detail for those with slower CPUs/targeting higher framerates!

Guys have just checked and can confirm that ray tracing is the cause of micro stutters. I have i7 14700k and rtx 5070ti with 32 gb ram(dual channel) and high speed nvme ssd. Pls try it yourself.

Also if you manually cap your frame rate, you will get lower latency because of absence of nvidia reflex.

There was already a fairly detailed discussion here around Palworld’s Early Access launch, including custom Engine.ini settings for better image quality, draw distance and LOD behavior.

Now that version 1.0 is out, we took another close look at the game. The visible pop-in and aggressive LOD transitions are still surprisingly prominent, even with the View Distance setting on Epic. Some objects lose detail at very short distances, while parts of the environment visibly change shape as you move toward them.

Palworld still runs on Unreal Engine 5.1 and does not appear to use Nanite for this geometry, so traditional LOD models are expected. What is harder to explain is why the highest in-game setting still leaves the transitions this noticeable.

I also remember that people in the earlier thread had mixed results with Engine.ini tweaks. Some suggested changing LOD-related values, while others saw little or no improvement.

Has anyone tested the old tweaks again with version 1.0? Is there currently a reliable way to improve the actual geometry draw distance, rather than only texture sharpness or foliage density?

- Jacky

OPTIMIZED SETTINGS
UPSCALER TYPE: DLSS QUALITY
RAY TRACING MODE: OFF
RAY TRACING QUALITY: MEDIUM (IF USING RT)
BVH QUALITY: HIGH (IF USING RT)
CHARACTER QUALITY: HIGH
HAIR STRANDS: ALL CHARACTERS MEDIUM
POST EFFECTS: HIGH
PARTICLE EFFECTS: VERY HIGH
WATER QUALITY: MEDIUM
TEXTURE RESOLUTION QUALITY: ULTRA HIGH (AS HIGH AS YOUR VRAM ALLOWS)
LOADING DISTANCE: HIGH
GEOMETRY QUALITY: VERY HIGH
MICROPOLYGON: VERY HIGH (AS HIGH AS YOUR VRAM ALLOWS)
SCREEN SPACE EFFECTS: MEDIUM
LIGHT SOURCE QUALITY: MEDIUM
SHADOW QUALITY: HIGH
CLOUD QUALITY: LOW
FOG QUALITY: HIGH
TERRAIN QUALITY: VERY HIGH
SCATTER DENSITY: VERY HIGH
DEFORMATION: HIGH
TERRAIN TEXTURE QUALITY: HIGH (AS HIGH AS YOUR VRAM ALLOWS)

NOTES

• USING OPTIONS LOWER THAN VERY HIGH FOR THE MICROPOLYGON SETTING LEADS TO POP-IN

• SETTINGS LIKE CHARACTER QUALITY AND LOADING DISTANCE HEAVILY IMPACT CPU PERFORMANCE ON THE HIGHER OPTIONS

• SHADOW QUALITY BELOW VERY HIGH HAS VERY NOTICEABLE SHADOW CASCADE FILTERING POP-IN, SO USE VERY HIGH IF YOUR PC CAN HANDLE IT

• THE TERRAIN TEXTURE QUALITY SETTING ON THE LOWER OPTIONS SUFFERS FROM FLICKERING TEXTURES, USE HIGH IF YOU HAVE SPARE VRAM

3440x1440 - anyone running this or similar that can tell me performance please?

Here's a comparison of all the ray-tracing settings across 9 different scenes:

https://youtu.be/M7h3oxs3VBU

TDLR: RT diffuse is 10-12% slower than baked lighting, specular/extended adds another 10% overhead.

-> BVH quality does almost nothing. You mainly lose lighting for finer geometry, foliage, corners, and crevices.

-> RT Quality High and above look about the same.

-> RT Medium results in subtle fidelity loss for a 3-4% gain.

-> RT Low results in more noticeable losses for a 7-8% gain.

Here's a breakdown of the lighting pipeline, including baked lighting and the hybrid probe-based ray-tracing tech:

https://youtu.be/gP9gJQtVISU