| View previous topic :: View next topic |
| Author |
Message |
foux
Tux's lil' helper
Joined: 04 Jul 2004
Posts: 75
Location: Rennes, France
|
 Posted: Tue Dec 11, 2012 3:47 pm Post subject: |
 |
|
| eccerr0r wrote: | This is probably something that could provide the critical clue...
though really... blah...
Unfortunately I don't want to re-download the whole game... |
I can understand that 
But in fact it appeared without even having to reinstall the game. My box was on accept_keyword amd64, and I switched to ~amd64. And from this day on, the game stopped to work (it worked perfectly before).
I try to uninstall it, but as you can see it didn't help.
I managed to solve the problem yesterday night by installing it with PlayOnLinux on a wine 1.5.10. But that doesn't explain why it isn't working on my other environment...
| eccerr0r wrote: | | I just had my dual boot box patch itself just fine. Still think it's something wrong with my "windows environment"... |
I'm dual boot to, but with OSX on the other partition |
|
| Back to top |
|
 |
eccerr0r
Advocate
Joined: 01 Jul 2004
Posts: 3000
Location: USA
|
| Posted: Tue Dec 11, 2012 9:56 pm Post subject: |
|
|
Currently I sort of maintain four installs of WoW on my machines -
1. A Core2 Quad with RadeonHD 5770 running 32-bit Linux only - this machine I normally play on. Does not patch correctly.
2. A Core-i7 using the HD3000 cloned from this install, and not unexpectedly it doesn't work either.
3. A Core2 duo with i965G CGC running 64-bit Linux only. This machine patches just fine.
4. A Core-i5 laptop using HD4000, mostly cloned from the above, running a dual boot 64-bit Linux. Other OS is Windows 7 Home. This machine also patches fine in Linux.
One could say it's a 32-bit Linux problem but I don't know... I tried partially wiping my Windows environment from my 32-bit installs but still did not seem to fix the problem (there are some settings I didn't want to wipe...).
_________________
Core-i7-2700K@4.1GHz/8GB RAM/180GB SSD/Intel HD3000 graphics
What the heck am I advocating? |
|
| Back to top |
|
|
foux
Tux's lil' helper
Joined: 04 Jul 2004
Posts: 75
Location: Rennes, France
|
| Posted: Fri Dec 14, 2012 7:33 am Post subject: |
|
|
| eccerr0r wrote: | | One could say it's a 32-bit Linux problem but I don't know... I tried partially wiping my Windows environment from my 32-bit installs but still did not seem to fix the problem (there are some settings I didn't want to wipe...). |
I'm not sure about that : the Wine in which WoW wasn't working was a 64 bit wine, while PlayOnLinux installed a 32 bit one, which is working perfectly fine. But who knows, wine works in mysterious ways |
|
| Back to top |
|
|
eccerr0r
Advocate
Joined: 01 Jul 2004
Posts: 3000
Location: USA
|
| Posted: Thu Jan 17, 2013 10:42 pm Post subject: |
|
|
Incidentally, the 64-bit Linux machines not only patch correctly, can run both 32- and 64-bit WoW.
I will have to someday switch my 32-bit install to 64-bit as I keep on running out of RAM in WoW. It looks like the behavior of Linux when running out of address space for Wine is very weird... I definitely have enough RAM (4GB) and I'm sure there's plenty of stuff in RAM that could have been swapped out with no issues, but it ran out of physical addresses for the WoW process - and the machine starts thrashing badly, X11 virtually freezes - I can't click buttons anymore, even on the Gnome desktop. I don't quite understand this behavior yet.
Fortunately I could (easily) ssh into the machine and kill just WoW. The ssh session wasn't even that slow. Weird.
I'll have to look at this again but I've seen WoW slow down a lot when the core size is around 2.5GB or more. The hard drive constantly thrashes around this utilization. With the 1G/3G split in Wine, that's about it, process size can't grow much larger... but I still have another 512MB to 1GB of RAM free...
I was a bit disheartened when my eeePC stopped working in WoW. I couldn't really play on it anyway (it's way too slow for just about everything except auction house) but it was kind of funny having a small machine at least load up WoW.
_________________
Core-i7-2700K@4.1GHz/8GB RAM/180GB SSD/Intel HD3000 graphics
What the heck am I advocating? |
|
| Back to top |
|
|
eccerr0r
Advocate
Joined: 01 Jul 2004
Posts: 3000
Location: USA
|
| Posted: Tue Mar 05, 2013 3:55 pm Post subject: |
|
|
Patch 5.2: The Thunder King came out today.
I have to say... it looks like Blizzard got their act together, or somehow I inadvertently fixed the patcher on my 32-bit Gentoo install. The patcher came up when I ran the Wow.exe binary and started to download Thunder King just fine. We'll see later on if this really worked though, maybe later on it will choke and die.
[EDIT]
Looks like it runs just fine, seems slightly slower though, but it patched and runs OK.
_________________
Core-i7-2700K@4.1GHz/8GB RAM/180GB SSD/Intel HD3000 graphics
What the heck am I advocating? |
|
| Back to top |
|
|
slowdive
n00b
Joined: 01 May 2005
Posts: 26
|
| Posted: Wed Mar 13, 2013 3:35 am Post subject: Update problems? Try a new wine bottle |
|
|
I have two machines running wow, both amd64, one of which was unable to update. I tended to scp the contents of the wow folder from the good machine to the bad whenever there was a big patch. For large patches, this made sense, since it was faster than redownloading the content from my relatively slow WAN link. For small patches, it was silly.
When I tried updating from the bad machine, I would get a variety of errors, including the dreaded | Quote: | | ERROR: Blizzard Updater is unable to write to this location because it is a system directory. |
I stumbled on http://aspensmonster.com/2012/10/10/upgrading-from-wow-4-3-to-mists-of-pandaria-5-0-5-on-gnulinux-debian-testing/, which has a bunch of nice steps, including talking about the updater Agent. Turns out there is a Battlenet directory under Application Data that controls some of the updating. I tried copying the good machine's battlenet folder to the bad machine, but that didn't help.
The final bit that helped was simply making a new wine setup (bottle / prefix), and mv'ing my existing wow into the new bottle. The bad machine's .wine infrastructure was very old, and had many things in different places (Application Data was in another spot, for instance). My hunch is that enough things were wrong that some aspect of the agent code was failing. Using a new bottle got around this problem.
FWIW, I eventually plan to have a separate bottle for every game I play. This will allow some independence among the installs and settings (SC2 needs different Direct3D registry keys than other games, for example). I already have bash scripts to start certain games, so having a separate prefix/bottle isn't a big deal. Note that you'll need to rerun any winetricks or other registry settings for every bottle, since each bottle is like its own [/u]mini-windows environment.
For more info on wine bottles, check out http://ziemecki.net/content/wine-using-bottles or http://wiki.winehq.org/FAQ#head-faf9617c53607e583f6e6ff70a4ac9522d490faf |
|
| Back to top |
|
|
eccerr0r
Advocate
Joined: 01 Jul 2004
Posts: 3000
Location: USA
|
| Posted: Sat Mar 16, 2013 3:25 pm Post subject: |
|
|
Next would be performance tips and tricks?
I am sad. Though I knew that Linux was slower than Windows in WoW this is somewhat problematic. In 5-man instances my Core2Quad and RadeonHD 5770 are acceptable. However on Galleon and the large trash packs in Heart of Fear, I sometimes drop down to 1 or more seconds PER FRAME. This is unplayable. I do have recount running, which I have yet to try to see if it's the culprit.
Now I only have one Windows machine that's capable of running WoW, and it's an Core-i5 laptop with built in graphics... I just tried running it in Heart of Fear (LFR) with Windows and D3D11 mode (since that's native.)
I stayed about 12FPS the whole time!!! This is somewhat an unfair comparison as Recount was not installed Since this is dual boot, next I'll see how this same binary works in Linux/OpenGL.
In any case, anyone running HoF trash packs (LFR) and Galleon with no problems? I am running OpenGL mode for Linux as overall it's faster than D3D9.
Addition - hmm ... The Win7 machine got down to 8FPS on some trash packs and down to 6FPS on Garalon. It looks like Recount may be the culprit after all. Recount should be CPU dependent, but surprising how bad it is...? Even on a Core2 Quad it's bad?
_________________
Core-i7-2700K@4.1GHz/8GB RAM/180GB SSD/Intel HD3000 graphics
What the heck am I advocating? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gamers & Players
