[Bug 29168] Star Wars: The Old Republic game client hangs at intro splash

wine-bugs at winehq.org wine-bugs at winehq.org
Wed Jul 24 06:41:18 CDT 2013


http://bugs.winehq.org/show_bug.cgi?id=29168

--- Comment #263 from Marco Di Fresco <marco.difresco at gmail.com> 2013-07-24 06:41:18 CDT ---
I did some test:

1.5.18
- Unpatched and without swtor_fix.exe it cannot run the game as it stay stuck
to the loading screen (the cog on the bottom right corner is spinning).
- Both KUSER_SHARED_DATA and swtor_fix.exe (used alternatively to each other)
solve the problem.

1.5.19
- Unpatched and without swtor_fix.exe it cannot run the game as it stay stuck
to the loading screen (the cog on the bottom right corner is spinning).
- KUSER_SHARED_DATA cannot longer be applied;
- swtor_fix.exe solve the problem.

1.5.24
- Unpatched and without swtor_fix.exe it cannot run the game as it stay stuck
to the loading screen (the cog on the bottom right corner is spinning).
- KUSER_SHARED_DATA cannot longer be applied;
- swtor_fix.exe solve the problem.

1.5.25
- Unpatched and without swtor_fix.exe it cannot run the game as it stay stuck
to the loading screen (the cog on the bottom right corner is NOT spinning).
- KUSER_SHARED_DATA cannot longer be applied;
- swtor_fix.exe is loaded without errors, but no longer solve the issue.

1.6 (LATEST)
- Unpatched and without swtor_fix.exe it cannot run the game as it stay stuck
to the loading screen (the cog on the bottom right corner is NOT spinning).
- KUSER_SHARED_DATA cannot longer be applied;
- swtor_fix.exe is loaded without errors, but no longer solve the issue.

As the problems in 1.5.25 and 1.6 appear to be identical, I may guess that no
version in between offer any difference; unless of course some official Wine
developer come out pointing a specific version that was supposed to work
differently, so in that case we can do a regression test.

Until the bug is officially fixed, or at least until there is a positive change
toward it, to play the game and still keep the latest Wine version system-wide,
I suggest to:
- Download the source code for Wine <= 1.5.24 (or <= 1.5.18 if you want to use
KUSER_SHARED_DATA patch instead of swtor_fix.exe);
- Apply the KUSER_SHARED_DATA patch (only if you have chosen the version <=
1.5.18 and you don't want to use  swtor_fix.exe);
- Either leave the compiled version on its own source code (by NOT issuing
'make install') or go back to the ./configure and add '--prefix=/opt/[whatever
directory that doesn't conflict with system-wide wine]')
- Make a script (or modify if you already use one) that call the custom Wine
version by absolute path (and eventually execute swtor_fix.exe of you opted for
that fix).


P.S.: as I was posting this it came to my mind that a regression test can be
done between 1.5.25 and 1.5.24 to see what is breaking swtor_fix.exe; since it
would take a lot of time and since swtor_fix.exe is an unofficial fix anyway,
is it worth doing it?

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.



More information about the wine-bugs mailing list