Check the published minimum, then the actual workload.

Compare the complete Windows minimum

Compare OS, CPU, RAM, GPU/VRAM and free storage, rather than using RAM alone as a compatibility test. The cited listing supplies a minimum configuration; we do not turn it into a benchmark, recommended-settings preset or target FPS.

Why the menu and market can load the GPU differently

In the October discussion, players reported greater GPU/resource use after entering the Demo than while sitting in its menu. The developer acknowledged that the density of the foliage and forest outside the playable area could be demanding on some hardware, despite using a dynamic GPU-instanced system.

A smooth menu therefore does not establish a smooth market. Conversely, high GPU utilization by itself does not identify a stock-production bug or prove that the whole application has stopped responding.

The reply promises continued optimization; it does not establish a specific foliage-density slider, launch flag or exact setting that fixes every machine. None is invented here.

Make a useful performance check

1. Record the Demo build from the initial splash screen and compare the published requirements with your actual system.
2. Distinguish failure to launch, an unresponsive menu, uneven movement and merely high GPU use. They require different reports.
3. Note whether the issue starts in the menu or after entering the market, and whether it changes with the part of the scene being viewed.
4. Record the resolution and the settings you actually used. Change one available setting at a time if you compare results; keep the original values so you can restore them.

These are comparison and reporting steps. We have not measured a hardware benchmark or a universal graphics fix for this game.

If the symptom is input or platform compatibility

If the cursor runs into the top-left corner, use the documented Demo input-fix route. If the game renders under CrossOver but buttons do not respond, use the Mac/Wine distinction. For a Proton launch failure, use the Linux setup report and limits.

For unresolved Windows performance, include your build, OS, CPU, GPU/VRAM, RAM, resolution and the menu-versus-market comparison in the performance discussion. A future optimization statement is not proof that your installed Demo already received it.

What this check should settle

You can compare the full published minimum and describe where the workload changes. If performance remains poor, you have a specific hardware/build/scene report rather than an unverified “best settings” recipe.