Make all unsupported renderer message features consistently warnings

Previously, some messages indicating a lack of support were errors
instead of warnings. Some messages were also not shown when running
a release export template.

- Use "renderer" terminology consistently instead of "rendering method".
This commit is contained in:
Hugo Locurcio 2025-10-19 00:19:40 +02:00
parent f5918a9d35
commit 2cf7af9149
No known key found for this signature in database
GPG key ID: 46ACE49F61685096
12 changed files with 47 additions and 31 deletions

View file

@ -547,7 +547,7 @@ void Main::print_help(const char *p_binary) {
print_help_option("--version", "Display the version string.\n");
print_help_option("-v, --verbose", "Use verbose stdout mode.\n");
print_help_option("--quiet", "Quiet mode, silences stdout messages. Errors are still displayed.\n");
print_help_option("--no-header", "Do not print engine version and rendering method header on startup.\n");
print_help_option("--no-header", "Do not print engine version and rendering driver/method header on startup.\n");
print_help_title("Run options");
print_help_option("--, ++", "Separator for user-provided arguments. Following arguments are not used by the engine, but can be read from `OS.get_cmdline_user_args()`.\n");