You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I cannot use one time Mobile and other time Desktop Vulkan backend by just changing command line options.
I need to set this in project settings manually.
Not sure, but --rendering-driver seems to be proper option, but it is unimplemented
The text was updated successfully, but these errors were encountered:
Not sure, but --rendering-driver seems to be proper option, but it is unimplemented
#53150 implements it, but Vulkan still only has one vulkan option there.
I presume we'll have to add a distinction between vulkan_clustered, vulkan_mobile and perhaps vulkan (use the project-defined setting, defaulting to vulkan_clustered on desktop and vulkan_mobile on mobile).
Alternatively, we should add a --set command line argument to set any project setting before the editor or project starts: --set some/project/setting "value"
Alternatively, we should add a --set command line argument to set any project setting before the editor or project starts: --set some/project/setting "value"
Sounds good but --set-setting might be more clear than --set.
Also, how to differentiate between project and editor settings?
A. Add them separately: --set-project-setting and --set-editor-setting.
or
B. First we check if it's a project setting with ProjectSettings::has_setting and then EditorSettings::has_setting if it's not a project setting.
Either or both options seem good to me,
This is fully fixed now in 4.2 and later (4.0-4.1 had some issues with --rendering-method not reliably working for toggling between Forward+ and Mobile):
Godot version
4.0
System information
Ubuntu 21.04 - Nvidia GTX 970, Gnome shell 3.38 X11
Issue description
Currently I cannot use one time Mobile and other time Desktop Vulkan backend by just changing command line options.
I need to set this in project settings manually.
Not sure, but --rendering-driver seems to be proper option, but it is unimplemented
The text was updated successfully, but these errors were encountered: