YARC 1.0.2 Linux: Adding -force-vulkan to Additional Launch Arguments causes YARG to fail to launch | YARG | Page 1

austere cloak Feb 7, 2025, 9:21 PM

#

Fedora 41, KDE Plasma 6.2.5, Ryzen 5 7640U, Radeon 760M

Steps to reproduce

Open YARC and install YARG from either stable or nightly
Select a YARG profile and click Profile Settings
Add -force-vulkan to Additional Launch Arguments
Click the Launch Stable or Launch Nightly button

Expected behavior

YARG launches in Vulkan mode.

Observed behavior

YARG starts to open, then immediately closes
The Launch Stable/Nightly button state changes to and gets stuck in Loading... for several seconds

Workaround

A build off the theli-ua/tauri-2 YARC branch (https://github.com/YARC-Official/YARC-Launcher/pull/59) does not appear to be affected by this issue.

#

YARC command-line output:

[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

#

player.log:

Mono path[0] = '/home/gguillotte/.local/share/YARC/YARG Installs/7d3f6a6b-1992-4ea6-a030-d0b9b5959615/installation/YARG_Data/Managed'
Mono config path = '/home/gguillotte/.local/share/YARC/YARG Installs/7d3f6a6b-1992-4ea6-a030-d0b9b5959615/installation/YARG_Data/MonoBleedingEdge/etc'
Preloaded 'STB2CSharp.so'
Preloaded 'discord_game_sdk.so'
Preloaded 'libRtMidi.so'
Preloaded 'libStandaloneFileBrowser.so'
Preloaded 'lib_burst_generated.so'
Preloaded 'libbass.so'
Preloaded 'libbass_fx.so'
Preloaded 'libbassmix.so'
Preloaded 'libbassopus.so'
Preloaded 'libsqlite3.so'
Display 0 'eDP-1 13"': 2256x1504 (primary device).
[Physics::Module] Initialized MultithreadedJobDispatcher with {0} workers.
Desktop is 2256 x 1504 @ 60 Hz
[Vulkan init] extensions: count=4
[Vulkan init] extensions: name=VK_EXT_debug_report, enabled=0
[Vulkan init] extensions: name=VK_EXT_debug_utils, enabled=0
[Vulkan init] extensions: name=VK_KHR_portability_enumeration, enabled=0
[Vulkan init] extensions: name=VK_LUNARG_direct_driver_loading, enabled=0
Vulkan detection: 0
Forced renderer 21 is not supported, exiting

Workaround

Launch the YARG binary directly from the CLI with -force-vulkan, i.e. cd ~/.local/share/YARC/YARG Installs/7d3f6a6b-1992-4ea6-a030-d0b9b5959615/installation; ./YARG -force-vulkan, which works without issue and launches YARG in Vulkan mode.

urban spade Feb 7, 2025, 9:23 PM

#

This also happens to me as well

austere cloak Feb 7, 2025, 9:45 PM

#

Merging https://github.com/YARC-Official/YARC-Launcher/pull/57 might make this issue obsolete.

GitHub

Add Graphics API selection (styled) by theli-ua · Pull Request #57 ...

This rebases Riley's commits from pr#51 on top of current master and changes from unstyled dropdown to styled toggle group

urban spade Feb 7, 2025, 9:52 PM

#

It would still be nice to understand.. maybe someone needs -force-wayland or something

austere cloak Feb 7, 2025, 9:52 PM

#

-force-wayland seems to work fine for me in YARC, for what it's worth. It's specifically -force-vulkan as a YARC Additional Launch Argument that crashes.

#

urban spade Feb 7, 2025, 9:57 PM

#

yeah, but does it do anything? either way seems weird

austere cloak Feb 7, 2025, 10:03 PM

#

YARC does seem to pass Additional Launch Arguments. -batchmode works, for instance.

#

So does -single-instance. So it's doing something. It's just not clear to me what's different about -force-vulkan via YARC arguments (which fails) vs. YARG -force-vulkan from the command line (which works).

urban spade Feb 7, 2025, 10:13 PM

#

You can always run strace to capture how arguments are exactly passed

austere cloak Feb 7, 2025, 10:32 PM

#

Maybe, though since it looks like Tauri handles this, I wonder if the PR to upgrade to Tauri 2.0 affects this behavior also.

#

I built the Tauri 2.0 branch of YARC and confirmed that it appears to be UNaffected by this issue.

austere cloak Feb 7, 2025, 11:06 PM

#

whoops

#

Tauri 2.0 unaffected for sure

urban spade Feb 7, 2025, 11:06 PM

#

Well, the actual process starting is in the rust code

#

oh, interesting

urban spade Feb 8, 2025, 10:01 PM

#

@distant ibex this one would be fixed by tauri-2 as well apparently according to reporter

#YARC 1.0.2 Linux: Adding -force-vulkan to Additional Launch Arguments causes YARG to fail to launch

Steps to reproduce

Expected behavior

Observed behavior

Workaround

Workaround