I used to have problems running WoW and ventrilo using the same software. For that reason, I used to run WoW under cedega, and ventrilo under wine. I actually generally prefer cedega for running WoW. It runs faster for me, though I've heard people say wine runs as fast, I haven't seen it do so for me.
In any event, running wine and cedega at the same time really kills my processor. As a result, my fps drops substantially. My computer isn't amazing to begin with, so I can't really afford the drop in some cases. So, I tried running ventrilo through cedega too, and it has been working (though I don't know recall why it didn't before). However, for some reason, it causes error 132 to occur in WoW after awhile.
I find this truly curious. My WoW has been historically very stable, and I have undeniably tested and proved that running ventrilo and WoW through cedega at once will cause a 132 error.
Is my only choice wine if I want to run both applications at once? Has anyone else had this problem?
I know this is an obscure post, and I don't really know if I can expect an answer, but we all know Blizzard won't help me as a Linux user, so I come here. I'll provide any other additional information upon request. Thanks!
I haven't played WoW in a while, but when I used to, I would run 2 instances of wine as 2 different users with no problems.
Start wine and WoW as the main user, and in another shell su to a second user (make sure they are in the audio group) and start wine #2 and ventrillo from there. Never any problems, even through hard-core raiding.
I don't know whether Cedega would work similarly.
Having a dual-core machine for this helps a lot, as does 2+GB ram.
Though I appreciate the reply, I'm really trying to run ventrilo and WoW under one instance. The issue that, in doing so, it seems to cause WoW to crash with the 132 error. I'm not really sure why. The error is not usually immediate, and seems to occur more regularly in some areas than others. I am sure it's a combination of a few things, however the error never comes up if ventrilo is running under a separate instance.
I am sure that the reason why running under two instances doesn't bother you is due to the power of your computer, though. My computer is about half yours, almost literally! I have only 1 gig or ram, and a single processor that's not all that powerful. If I run two separate instances of wine/cedega, my fps while raiding can drop to 2. That is not acceptable in cases in which I have to run some certain direction.
However, in general, the use of ventrilo under a separate instance from WoW will nearly half my fps. For a client as light as ventrilo, I can't think this is acceptable. I am wondering if other people suffer from this problem as well?
It could very well be that the only solution is a better computer... something I cannot afford right now. On the other hand, the real piss-off is that if ventrilo would release a Linux client, as they had promised in 2005, this wouldn't even be an issue, as I'm sure a native client would not take many resources at all. Oh well...
My solution to running ventrillo and Wine+WoW.exe simultaneously was to use another computer. Although that is not a solution for many folks who simply do not have computing resources at their finger tips.
I wonder if the in-game chat is better, or folks still using ventrillo
I used to play WoW and vent on the same user using wine for a long while with no issues, other than needing to un-check the 'use direct input for hotkeys' box.
I don't normally use vent so I wasn't aware that it was "under development" for so long. Oh well, I was only going to use it on rare occasions anyway. I don't like hearing the random conversations while I'm trying to play. I prefer to just listen to my music while playing anyway. I use it on occasion to talk to family and friends in other states, it's easier and cheaper than a phone call.
I'm not clear on one point - you can't run WoW and Ventrilo under the same instance of Wine? I see you have problems with running both with Cedega.
I have been running both under Wine. I only listen to the raid leader and just type in raid chat so the PTT issue not relevant for me. The Ventrilo listing at the Wine website has a script hack that does provide PTT.
I'm running WoW on an Athlon XP 3000+ with 1GB RAM and Wine 0.9.49 with ALSA.
I've been using WoW+Ventrilo on the same computer for a long time. Basically, if a lot of people talk at once your processor is fucked, even if you have one with insane specs (I'm running a dual core 2.4ghz now and I still get a little stuttering).
I suppose this may not be the answer you were looking for, but I use two different versions of wine for this; I run WoW with the latest git build and vent with the latest release build, so there are actually two completely separate instances of wine running with separate settings.
There is no substitute for experience.
Imperfection indicates a lack of effort.
Vent sucks compared to Teamspeak and TS is cheaper and less of a network hog to bad people dont understand this and hopped on the Vent band wagon.
I run vent on my company laptop while I raid. Now The new vent afks the client since I am not doing anything on it just listening. The writer of vent said he was not going to port a native client since he was worried about people stealing the code hahahha what a joke.
I got a new computer a couple days ago and tested it tonight with no errors. When I originally researched this, when Windows gets 132 errors, the reason was pretty vague, although usually associated with a hardware issue. I do know that I had more of a tendency to get the crashes when I raided. For awhile I thought that this was due to the fact that there is more going on in WoW than in a non-raid situation. However, reading Darckness, and thinking back on my own experiences, I'll have to agree that it is actually as he says. It seems 132 errors are more common if there are more voices in Ventrilo at the time. Right now, with a quadcore 2.4ghz I've had no issues running them at the same time, under the same instance or otherwise. Admittedly, though, I am using wine this time around. I think I would get 132 regardless on my old computer, but I cannot remember, as I long gave up on the issue and used an old mac laptop for Ventrilo. I may try to get cedega working just to test this, but the build I used to have isn't working, and I don't want to renew my subscription at the moment.
Overall, it's probably related to the processor or sound? It could also be a cedega issue. If I get cedega up and running, I'll test it, or if I can produce the 132 error on this computer, I'll post back. Otherwise, I can't really come up with anything concrete on the issue.
ConVicTioN wrote:The writer of vent said he was not going to port a native client since he was worried about people stealing the code hahahha what a joke.
How can you steal code from a binary? ... ok maybe I should append that. How can you steal code from a linux binary that wouldn't take equal effort from a windows binary?
ConVicTioN wrote:The writer of vent said he was not going to port a native client since he was worried about people stealing the code hahahha what a joke.
How can you steal code from a binary? ... ok maybe I should append that. How can you steal code from a linux binary that wouldn't take equal effort from a windows binary?