The Find The Needle low FPS and performance issues are a CPU problem, not a graphics problem: lowering the resolution alone will not fix it, because the processor is what struggles as your factory grows.
Find The Needle low FPS and performance issues: the CPU is the limit
- A player on an 8-core / 16-thread 4.6 GHz machine reported 100% CPU usage during level loading, with the PC freezing.
- Another player on a 3600 with a 3080 FE got 25 fps at 1080 on medium settings, and judged the game to need a lot of optimisation.
- Lowering the graphics settings helped some players only partially, which is the expected result when the load is on the CPU.
- Very large factories are CPU heavy. The recommended spec says a faster CPU keeps the frame rate up late in the game.
The machine you need for the late-game factory is in the demo PC requirements.
What actually helps
- Close other demanding applications before you start a session.
- Check whether the slowdown only happens inside the large factory. If the frame rate is fine at the start of a map and drops as the belt network grows, that is the CPU load, not a graphics setting.
- Keep the factory smaller than you think you need. Every arm, belt and pole is work for the processor, so a compact layout with several parallel lanes beats a sprawling one. How far a single session can realistically push is in what the demo lets you finish.
- Demo V8 reworked how loose hay is rendered, turning it into hay tufts to improve FPS. V8 also raised the default jump height, so older videos look different from your current build.
What does not help
- Lowering the resolution alone. The load is on the processor, so a smaller framebuffer leaves the bottleneck exactly where it was.
- Lowering graphics settings and expecting the same gain everywhere. It helps somewhat in some scenes and barely at all in others.
- Waiting for a fix. The game does not promise an unattended farming layout, so watch the line rather than leaving it to run on a machine that is already struggling.
If the game will not start at all rather than running slowly, that is a different problem — the crash fixes cover it, and what the demo lets you finish covers how far you can push a session.