Unlike other display options, this one was missing a description.
This clarifies the option's purpose and the fact that it displays
the host's CPU usage, not the emulated system's CPU usage.
These options (especially xBR) have a very high cost. In my experience,
xBR has a greater impact on the framerate than enabling 4× SSAA or PGXP
in CPU mode (whose quality increase is much more obvious).
These options are also essentially unusable on mobile, regardless of
how powerful your device is. As a result, this adds warnings both
in the option names and the description.
Bilinear filtering is not affected by this performance cost, as GPUs
can perform this in hardware without having to emulate filtering
through a shader.
Previously, when you selected MSAA in the advanced options, you
got MSAA but the enhancements display showed "SSAA".
The opposite happened when you selected SSAA.
- Use CMake's `-B` option to automatically create the build folder
and avoid the `cd` requirement.
- Use CMake's build tool-agnostic `--build` option to use the same
build command regardless of whether GNU Make or Ninja is used.
`--parallel` also ensures that all CPU threads are used by default.
- Mention optional dependency on Ninja for macOS (it's confirmed to work
there, installed from Homebrew).
- Update Qt macOS path to use the default installation path on a modern
Homebrew installation. The old path is still mentioned just in case.
- Mention that the generated macOS application bundle may have to be
manually resigned before it can be run.
The macOS build steps were successfully followed on a 2020 Mac mini
(Apple M1).
Hugo Locurcio