Neverwinter Nights in VirtualBox: My Settings

Now that I’ve managed to get my copy of Neverwinter Nights to run in a VirtualBox VM (as detailed here), I wanted to make sure I got the most bang for my bucks, and played around a bit with a few tunables.

My VirtualBox settings depend a lot on my hardware, of course. In my case it’s a MacBook Pro with 4 GB of RAM. I initially started granting 2 GB to the VM and trying to measure how much is needed with vmstat while running the game. However, either there is a memory leak in nwmain or the way of measuring vmstat into a file leaks memory somehow (to HDD cache or some such). The measurement had only 400 MB of the 2 GB left after playing and quitting the game only freed up memory to a total of about 900 MB. However, setting the total available memory to 1 GB seems to work nicely. My settings are like these:

The first thing I do after starting the VM is turn off host integration for the mouse. While that generally works quite satisfactorily, with NWN, I can’t stand it. Because the SDL game tries to mess around with the mouse pointer at a lower level, moving the mouse out of the VM leaves the mouse pointer invisible. When you click on something rendered by the host (say an icon on the backdrop or a window), the mouse pointer becomes visible. If you, then, move back into the VM, you suddenly have two mouse pointers painted one over the other … rather distracting.

As far as settings in Neverwinter Nights itself are concerned, a resolution of 1400 x 1050 was what I was going for. One word of caution: “environment mapping on creatures” seriously messes up your display. I started with these settings:

Initial Video Options

Initial Video Options

Initial Advanced Video Options

Initial Advanced Video Options

Those settings worked well for a while. The only thing I noticed were some white polygons here and there, a couple of trees, some carpets, my Paladin mount, nothing terrible. But it turned out that I was quite lagged in situations where a large number of other characters were around. I was looking into my network connection, memory and storage load, but it, quite simply, turned out to be anti-aliasing. Turning that off removed any lag for me (that I couldn’t explain by a major download or some such.) It also doesn’t impact the look and feel so much IMHO. My current settings, thus, are:

Current Video Options

Current Video Options

Current Advanced Video Options

Current Advanced Video Options

I don’t use any of the SDL environment variables that I used to, anymore. The only thing that I changed in nwn is to remove the game provided SDL libraries from the library path to make it use the newer ones from jaunty. Not sure that makes much of a difference, though.

Anyway, I’m set. The game hasn’t crashed ever once in VirtualBox.

Advertisements
Tagged , , , ,

6 thoughts on “Neverwinter Nights in VirtualBox: My Settings

  1. Grrr, blast that wordpress gallery … the NWN screenshots weren’t supposed to go up to the VBox images, but oh well.

    What’s more interesting, though: Seems I might not have used the right keywords when researching my NWN crashes. It appears such crashes occur on multi-CPU/multi-core machines and the simple solution is to disable all but one core while playing. That’s worth another attempt, then. But first I need to DL the Xcode tools again, because I didn’t install CHUD.

  2. David Barnes says:

    Thank you! Very informative and helpful. Have you tried running the toolset using VBox? I have been working with it for a few days, but I’m encountering some graphics issues.

  3. Haven’t tried that. I have a version of the toolset that I used to run on Linux with wine somewhere, but that doesn’t just run on wine ootb. Installed dx9c through winetricks, but that doesn’t help much (dxdiag crashes, too). I’m trying with vc2005sp1 which is said to help for wow, but I don’t remember doing any of that when I was using it (not extensively) two years (or so) ago. From my startup script it seems I did compile wine from scratch at the time (and certainly not without a reason.)

    I suppose you’re running windows?

  4. Btw., downloading vc2005sp1 I get a message saying it’s going to take 2d 48h !
    What’s that? Is this a nice way of saying it’s going to take 4 days?
    Oh well 😉

  5. Guess I’ll stop that download … the toolset starts up on my native jaunty machine with wine on a fresh wineprefix. So whatever issues the jaunty in VBox has with it, is prolly not related to the installation. Since the VBox installation complains about opengl32.dll failing to register, I am inclined to believe that it’s something to do with the 3D support in VBox.
    Because honestly, the toolset with wine is no fun, at all (graphics flash a lot, rotation doesn’t seem to work), I guess, the only remotely sensible config would be WinXP inside VBox … but that’s a whole new world of compatibility issues with the VBox 3D support that I have no idea about.

  6. Yeechang Lee says:

    I also have NWN, VirtualBox, and a Macbook Pro. My findings with all graphics settings set to maximum but antialiasing turned off:

    * Windows 2000 as the VM’s OS: Acceptable performance (generally 15-30 fps) until I save the game. Strange, isn’t it?
    * Windows 7: Acceptable performance until the player leaves the Hall of Justice in chapter 1; I think the many fires in the braziers at night are too much.
    * Wine: Acceptable performance outside the Hall of Justice. I began with vanilla Wine from MacPorts and the stock Apple X11.app, but have now moved to Wineskin and its built-in Xquartz server variant. The game runs well either way; installing the game within Wineskin merely makes it look and act like a “real” OS X application.

    I like being able to flip between apps running in different Spaces virtual desktops using system keybindings. By setting Wineskin’s Screen Options to Rootless and Virtual Desktop at 1344×840 (smaller than the 1440×900 physical screen), the game plays in a window which Spaces can auto-assign to a particular virtual desktop. Set the video resolution within the game to 1440×878, and the result is a full-screen game (minus the menubar) which nonetheless responds to Alt-Tab and Spaces keybindings. I normally like seeing the Dock, but having it on top of the game is annoying; by using the trick at http://www.mactricksandtips.com/2009/07/hide-the-menubar-or-dock-in-specific-apps.html I got the Dock to hide only when the game is focused.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: