DirectX Error?

[freebullets]

Whenever I keyclone tries to start multiboxing, the first wow starts up, then when the others try to start, they give a directx error. How can I fix this?

Also, it's hard to keep all my characters going in a straight line. Is there a way to synchronize the mouse too? Or maybe a way to line them up?

[mikekim]

1. try reinstalling directx, sounds like one of the files is corrupted

2. your characters should be on /follow with your main, you cannot run them together (buy controlling them all at one with the movement keys).. this is the way it has always been. put wasd on the do not pass list in keyclone

[keyclone]

also, run dxdiag and check the directX version (i'm running directX 10)

then go to the Display tab. check the DirectX features. are they all enabled?

[freebullets]

Reinstalled latest Dx, everything is enabled, still nothing. The main window never changes shape or size either.

Also is maxfpsbk is the max fps of the inactive windows?

EDIT: Installed video driver, still nothing. BTW i'm running vista.

[keyclone]

hmmm... another thing, make sure when you run keyclone that you do it with admin rights (right-click/run-as-admin)

also, run one wow... go to wow/options/sound and make sure 'sound in background' is UNCHECKed

wow/options/video ... 'vertical sync' UNCHECKed

let me know if that helps

(and yes, maxfpsbk == maximum frames per second while in the background.. ie: not the active window)

[emesis]

What is the exact error? Something about not being able to start 3D acceleration?

I see this occasionally, not so much when starting my 5 instances with Keyclone (though it has happened this way), but sometimes I have one of the warcraft instances error out and I need to restart it manually, and I see this error. Once it starts happening I generally need to wait a while or close and restart my instances.

Do you get this consistently on startup, with your second window? Once you get this message, can you start an instance of warcraft manually or do you get the same error message if you do that?

Can you reproduce the error by starting multiple instances of Warcraft manually, not using Keyclone, quickly one after another?

If yes to the last question, you might want to try working around this. Keyclone doesn't have a setting in the command editor for placing a delay between starting up the instances, but it would be pretty easy to write a .vbs (Visual Basic script) or .bat (command batch) file to do this. For instance,



Set oShell=CreateObject("Wscript.Shell")
oShell.run "C:\wo\wow.exe"
Wscript.Sleep 8000


The above code, saved to a .vbs text file, will start the wow.exe executable located in C:\wo and then wait 8 seconds before exiting. I can't check this with keyclone at the moment since I'm in a huge queue to get in the server, but I'd be surprised if Keyclone didn't accept running a vbs file instead of the WoW executable directly.

[freebullets]

Thanks, it's working now. Whatever I did fixed it.

Also, the sound is kind of torn. Probably because my comp isn't that fast. Any way to fix this?

[keyclone]

what are you system specs? how many wows, just two?

[freebullets]

3 WoWs on a Single core athlon 2.0? GHz processor and GeForce 7300 GT

I have a dual core 3.0 GHz and a GeForce 9600 GT on the way

EDIT: Oh and 4 GB of ram

[keyclone]

your memory is fine, but your processor is getting slammed

one thing you can do to help is to set up commands to run your wows and then set then maxfpsbk to 8 and the maxfps to 30 (or less)

then start your wows using keyclone by typing the commands in the command area which is to the right of the 'connect' button on the main screen.

depending on the command names you choose, the command should be:

wow1;wow2;wow3

of course, log into a single wow... and set all your video settings as low as possible (this goes without saying :D)... then exit to force those settings to save to disk