This follows Chris Cote's pinned dedicated-GPU instructions , rechecked on October 8. The developer describes a Chromium/Steam Overlay issue. Player replies report improvements on some PCs, but no controlled benchmark or guaranteed frame rate is supplied.

Jump to the file change or how to restore it.

Check whether this is your problem

This is relevant when the game opens, your PC has both integrated and dedicated graphics, and reduced performance may be caused by the wrong GPU being selected. On Windows, observe the game's GPU activity in Task Manager or your GPU monitoring tool and identify which adapter is active. Low frame rate alone does not establish that cause.

  • If you have only one graphics adapter, this dual-GPU workaround does not match the developer's stated case.
  • If no game window opens, use the startup checklist first.
  • If you are playing on Steam Deck, start with Full Screen ON and Stretch Screen OFF; a handheld stutter report does not establish a PC dual-GPU problem.

Steam Overlay and achievements: decide before editing

The developer explicitly says this workaround disables the Steam Overlay. If you need the Overlay, keep your original configuration rather than treating the change as a free performance upgrade.

A September 28/29 reply in that thread, depending on Steam's displayed timezone, reports achievements failing while using the change. That is a player observation, not confirmation that every setup loses achievements. If achievements matter to you, weigh that uncertainty before proceeding. This guide cannot promise that restoring the file will award achievements missed earlier.

Apply the exact flag replacement

  1. Close Elderfield and preserve the original

    In Steam, open Welcome to Elderfield → Manage → Browse local files. Find package.json in the installation folder. Copy it to a separate backup folder and note the installed build. Keep the original filename and extension in that backup. For a separate save backup, see the save-folder guide.

  2. Replace the existing flag

    Open the installed package.json in a plain-text editor. Find --in-process-gpu and replace that exact text with --force_high_performance_gpu. Preserve the surrounding JSON quotes, commas and other options. The developer says to replace the flag, not leave both flags together.

    If the old flag is absent, stop: your file does not match these instructions. Do not invent a JSON field or paste this string into an unrelated setting.

  3. Save, relaunch and compare the same scene

    Save back to package.json, ensuring the editor did not add .txt. Launch through Steam. Compare the same area and action with your previous result, keeping other settings unchanged. Record GPU activity, performance and Overlay behavior; restore the original if there is no benefit or the tradeoff is unacceptable.

Restore the original configuration

Close the game. If the installed build has not changed, copy your untouched package.json backup back to its original installation location, replacing only the edited file. Relaunch through Steam and check the original behavior. This rollback does not require deleting saves or replacing the NW.js runtime.

If Steam has updated the game since you made the backup, do not overwrite the new build with an old configuration. Check the current file and developer instructions again. Keep a new untouched backup before any further edit.

If performance remains poor

Return to the original configuration and report the integrated and dedicated GPU models, installed build, active adapter, affected area and what changed during this test. For action-specific crashes rather than frame rate, use the dated symptom index. Neither this flag nor the older patch notes establish one fix for every crash or stutter.