[Bug 29582] Star Wars Battlefront (I and II) "Loading" screen very slow.

[wine-bugs at winehq.org]

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

--- Comment #42 from Maxim Stewart <gamer1119 at gmail.com> ---
(In reply to Daniel Santos from comment #41)
> Well, graphics and sound alone won't do it for me -- it's like coca-cola
> where you get a lot of pop, zip, fiz, but no substance or bang.  It's just
> so sad they'll put all that work and talent into inventing new ways of
> making amazing graphics and then attach a crap game to it.  It's like
> painting a masterpiece only to cut it out of the frame, rub a glue stick on
> the back and sticking it to the trunk of a beat-up 1978 monte carlo with
> fading paint and a busted muffler.  I mean, it's their masterpiece and they
> can do whatever they want with it, but damn!
> 
> Anyway, I tested it it's working great with SWBF2.  The computer I tested on
> is old (quad-core Phenom) and with the patch disabled it takes 87.5 seconds
> to load vs 12.3 seconds with.  I only tested an old retail DVD version and
> not the recently patched one from steam, but I doubt much has changed
> structurally in the program its self.
> 
> I don't think this patch will be in PoL or Wine anytime soon because it's a
> *massive* change with around 8k new lines of code (not counting 2k lines of
> debugging and verification code) and altering a lot of how the wineserver
> works (which is at the core of Wine).  My best hope is to have it in
> wine-staging within a month or two, but it still needs a lot of cleanup. 
> However, I presume that something like the little hack patch could end up in
> PoL -- I haven't used it much and I'm not sure how their "connectors" work.
> 
> As far as integrating it with PoL, I don't know how you can do that.  To my
> knowledge, you would just have to build it.  There is a guide here:
> https://wiki.winehq.org/Building_Wine, but it's not very easy for the
> uninitiated. :o  Then again, after you do it the first time it will get
> easier the next time you need to build it for some reason.  The only thing
> you would do differently is get the sources from my github account and
> checkout the "hybrid-sync" branch.
> 
> As an afterthought, I have not yet tested building only 32-bit (with a
> 32-bit server), but that will be fine as long as I didn't break something. :D

You had me hee-hawing at a master piece being cut out and glued to the car. I
just imagined The Scream by Munch being cut out by a kid who's 5 and grinning
stupidly with glue stick glue in his mouth. XD

Now, I don't think that the Steam version changed much either even after the
updates. Still, it's worth my asking you since you coded the patch and know
more about what's going on with it. Anyway, I compiled the wine version in
32bit given that when I ran the ./configure command it complained about not
having some 32bit dev-libs needed. I hadn't thought to pass an argument to the
command to prep it for 64bit instead. My machine is 64bit but I assumed that
you had made the version 32bit for some reason. Shame on me for being
presumptuous and on top of that building the version in a VirtualBox. <sigh>
Anyway, I looked through the info for PlayOnLinux and I did find where they're
storing their Wine versions. Their layout is quite different from the compile
directory but I assume it follows standard layouts that a normal Wine install
would have. I bet you I could just run the Steam game from cli and use the
command you gave instead of going through PoL itself.


Here is what I did for compile in VirtualBox running 32bit Ubuntu 16.04 LTS
1.  Make sure to add or uncomment the sources URIs in /etc/apt/sources.list
2.  sudo apt-get update
3.  sudo apt-get build-dep wine
4.  git clone https://github.com/daniel-santos/wine
5.  git checkout hybrid-sync
6.  cd /the/location/of/wineBuildDir/
7.  ./configure     // Add a switch to build in 64 bit else just leave as is.
8.  make
9.  make install    // Optional since we can run from the build dir.

TO-DO
10.  STAGING_SHARED_MEMORY=1 STAGING_SHM_SYNC=1 WINEPREFIX=<your_prefix> wine
GameData/BattlefrontII.exe

First, did I do it wrong? Second, if no, then I need to test the compiled
version and get back to you. But, from the looks of it, nothing went wrong
during the compiling of your Wine version in 32bit. Now, I gotta do it for the
64bit version. Quick confirmation, the WINEPREFIX is the location path for my
virtual drive containing my Steam and game, yes? So, it'd be the master folder
of the drive folder called drive_c or is it drive_c itself?

-- 
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.