I'm trying my best to find the most balanced solution for playing W:A windowed, so I'll have to settle for playing it in VMware until some better option shows itself.

I've recently updated my VMware installation to the latest version (v7.1.4-385536) and I'm having problems with it. I don't know if it has something to do with the latest W:A update (settings), but it's not working fine.

First of all, no matter what settings I have set for Input, the cursor always leaves the vmware window in-game. Only in-game, while on the desktop it behaves according to the settings in effect. The issue with this is that it makes the cursor fly around (leaving the window while in-game) and it's also uncontrollable (very speedy) in-game.

http://img855.imageshack.us/img855/381/snagstridery11m05d05h22.png

I've tried all combinations just to make sure, it just doesn't want to work as it used to.

I've stopped all vmware services within the virtual computer: nothing!

http://img813.imageshack.us/img813/381/snagstridery11m05d05h22.th.png (http://img813.imageshack.us/img813/381/snagstridery11m05d05h22.png)

-----------------------------------------

And the other issue I've got is that the game stops responding (freezes the virtual machine) if I try to minimize or quit the game while playing (doesn't happen when I'm at the menu screens). The same happens after I finish playing a round (when the players should return to the lobby).

I've got these issues with the recommended settings for VMware as well as with various other settings.

http://img835.imageshack.us/img835/2927/snagstridery11m05d05h23.th.png (http://img835.imageshack.us/img835/2927/snagstridery11m05d05h23.png)

-----------------------------------------

So, is anyone playing the latest W:A on the latest version of VMware (XP guest)?

I have run WA 3.6.31.0 in a vmware workstation 7.1.2 vm. Windows 7 was installed on the guest. Workstation was running on a Windows Vista host. I didn't have the problems you describe. I had vmware tools installed and running on the guest. I set the vm display mode to "Autofit Window" and "Stretch Guest" (in the "Edit->Preferences->Display" menu) so nothing conflicts with most games' rigid video modes.

Maybe there's something wrong with using XP on the guest. I don't know. I hope sharing my experience helps you.

Here's my "Input" setting:
http://lex.clansfx.co.uk/dump/00000057.png

Thank you, Lex! If that setup is currently working for you, then I'll make the corresponding changes so they match yours and keep testing that way.

I've tried earlier patch versions, the issues are still present so most definitely there's no problem with the latest patch (if anything, it's only improvements for running better on virtual machines).

I've successfully played previously on XPSP2/SP3 and W7x86/x64 guests (with W7 x64 as the host), so It probably has something to do with the latest vmware update.

I'll keep testing with the current vmware version and the settings scheme you provided and I'll change the guest OS (tried XP SP2 and SP3 until now).

Something else I should mention: when the freeze occurs, I can still hear the background music, so it's like the game's running, but you can't do anything on the virtual computer (only reset or stop the machine).

Do you regularly play W:A on a virtual computer, or just for testing purposes. And if you do play mostly on the virtualcomputer, what resolution are you using for its display and did you make any special changes or did you keep the defaults suggested when first started the game?

I tried default and your settings on 7.1.0 and 7.1.4 under win7x64 with XP guest... All input works fine. May be you need fully reinstall VMWare and guest XP.. I recommend you to disable Autofit Guest, with it game will destroyed if VMWare window accidentaly resized.
But other issue i got too :(. It makes a lot of hate when i debug rubberworm :mad:.. .29 had no this problem...

May be you need fully reinstall VMWare and guest XP..

Reinstalled Windows several times, that's not it. The cursor behaves accordingly (e.g. doesn't leave the window) when I'm not in-game, so a faulty installation is excluded.

I recommend you to disable Autofit Guest, with it game will destroyed if VMWare window accidentaly resized.

That's useful information for those that just started using virtual computers to play games. Applies to both VMware and VirtualBox.

But other issue i got too :(. It makes a lot of hate when i debug rubberworm :mad:.. .29 had no this problem...

Speaking of VirtualBox (the latest version up to date), I don't have these issues. Game minimizes just fine, I can quit without problems, no freezing and no cursor (speed, fly out) problems. Same Windows XP installation, latest W:A version, so it clearly is the latest version of VMware causing all the trouble.

Either way, VirtualBox's performance is poor compared to VMware's, so playing on VirtualBox isn't a much welcomed option.

Use ctrl+alt to release the cursor from the vm. That's the only way to do it without vmware tools running.

Yep, it even tells you when running VMWare for the first time that ctrl-alt is how you unlock the mouse.

Use ctrl+alt to release the cursor from the vm. That's the only way to do it without vmware tools running.Yep, it even tells you when running VMWare for the first time that ctrl-alt is how you unlock the mouse.
Yes, I know but I'm a bit confused as to how is that related to my post. The problem I'm having in VMware is that the cursor leaves the window regardless of any settings I have made (even if VMare tools is not installed).

Anyway, even if this gets fixed, the other, more severe, issue still remains and it seems that it's strongly linked to the latest version of VMware. KMZ is experiencing it too.

I'm sorry for misreading your problem and giving you an irrelevant solution to an irrelevant problem.

You've said you tried all combinations of options on that "Input" menu. I don't think I can help any further. I wish you luck in solving this puzzle.

Yes, tried different settings on the Input tab as well as other settings and in-game options (registry tweaks).

I think the solution would be to downgrade VMware to the latest version that seems to work, which would be the one you're using- 7.1.2.

Thank you!