[Bug 50878] Neon Noir Benchmark (through symlink) crashes on Wine-Staging before showing the first scene.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50878

--- Comment #4 from Dmitry Skvortsov (Iglu47) <lvb.crd at protonmail.com> ---
(In reply to Erich E. Hoover from comment #3)
> Would you mind stepping me through exactly what you have here?  It sounds
> like you're saying that you have two wine prefixes, one for downloading
> utilities and another for testing where you have a symlink from the second
> one to the first one.  If that's the case (or something similar), could you
> tell me exactly what your symlink is?

Yes, approximately it is, only the directory with the application itself
remained from the first prefix.

original: some_foldder/Neon_Noir_Ray_Tracing_Benchmark_2527
link:     some_foldder/prefix/drive_c/Program Files (x86)/Crytek/CRYENGINE
Launcher/Crytek/Neon_Noir_Ray_Tracing_Benchmark_2527
commands for the creation: 
cd "some_folder"
mkdir -p "prefix/drive_c/Program Files (x86)/Crytek/CRYENGINE Launcher/Crytek"
ln -sr Neon_Noir_Ray_Tracing_Benchmark_2527 "prefix/drive_c/Program Files
(x86)/Crytek/CRYENGINE Launcher/Crytek"
where WINEPREFIX="some_foldder/prefix"

A soft symbolic link is actually usually only used in cases where need to do a
lot of testing of different versions of Wine with the fresh prefix each time
(just small QoL thing at work with 50-sh GB applications) and such the
situation can be easily avoided by creating, for example, the drive D by
standard means, instead of manually creating soft symbolic links by users. So
in fact it might be necessary to clarify here whether this is consistent with
how that is supposed to work and is there really a problem or the report can be
closed.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.