Icewind Dale: Heart of Winter Forum

Hello everyone,

I have an iMac running OS X 10.5.8. I purchased the DRM-free, download-only version of Icewind Dale (with Heart of Winter expansion) from www.gog.com. I installed the game into a Windows XP bottle. It installed without any problems.

For a while, the program appeared to run almost perfectly. (The only problem was that the sound in the intro movie stuttered a bit.) I created a party of characters and wandered around the town where the game starts. I went into a few buildings. However, when I try to go into the northernmost building, the game immediately crashes. A dialogue box pops up which says something like, "IWD.exe needs to close. We are sorry for the inconvenience. Check www.codeweavers.com/compatibility to see if there is any advice about this problem."

I don't know if CrossOver generated an error log anywhere. I did open the "Console" application in the "Utilities" folder, and some lines in there pertain to Icewind Dale, but I cannot tell if any of them have to do with the crash I experienced.

I need to be able to access this building in order to start the game's plot, so the game is not playable (beyond an early point) for me.

Does anyone here know what the problem might be?

Do you know if there is a way for me to obtain log information from one of these crashes, so I can provide it to help with debugging?

Thank you very much!

Hi,

Grab a debuglog of the crash, by following the instructions on the following page;

http://www.codeweavers.com/support/wiki/SubmitTechSupportLog

Attach the debug to the 'IWD.exe' file, tick the +seh checkbox and put +ntdll in
the 'Other' stringbox. Once you have created the debug log, gzip it and upload it
to here using the password TgdL47vUgd to login and upload the file.

Btw, which version of Crossover are you using, and what model Mac do you have?
Which video card/chipset is it fitted with?

Cheers!

Thank you for the instructions. I did as you said and created a crash log with the +seh and +ntdll options enabled. I uploaded the crash log to the location you indicated. It is called "IcewindDaleHeartOfWinter_CrashLog.cxlog.zip". (Note that the game application is actually called "IDMain.exe," not "IWD.exe." I misremembered the application name when writing my original post.)

Here are more details about my setup:

   I am using CrossOver Games for Mac version 9.2.0.

My iMac is an aluminum body iMac introduced in mid-2007. It has:

   Processor: 2.4 GHz Intel Core 2 Duo
   RAM: 3 GB of 667 MHz DDR2 SDRAM
   OS: 10.5.8
   Video Chipset: ATI Radeon HD 2600
   VRAM: 256 MB
   Video card EFI Driver version: 01.00.219
   Built-in screen: 1900x1200, 32-bit color depth
   (I have an external monitor connected: 1280x1024, 32-bit color depth)

Note that this game has a separate config program which you run to choose game settings before starting Icewind Dale. In that utility, I have set:

   All graphics and audio settings to "high end"
   OpenGL 3D Acceleration enabled, 32-bit textures enabled
   Resolution: 1024x768 (This resolution is in the "unsupported" category. Only 640x480 and 800x600 are "supported" by Black Isle Studios. The "unsupported" category has four resolutions in it, but all of them are grayed out for me except for 1024x768.)

Please let me know if there is anything else I can do to help out with this problem. I wouldn't mind running additional tests or providing additional information.

Hi,

Is crashing in the Mac's opengl lib, but, that looks like it's due
to being handed an invalid pointer in memory - possibly relates to;

http://bugs.winehq.org/show_bug.cgi?id=14662

I'm unsure of the situation wrt OSX-10.5.8 and the HD2600 (there were
some opengl/driver bugs in 10.5.x but I'll have to ask someone in the
know whether they might be at play here or not)...

Thanks for the debug log -- just curious, have you tried enabling 'emulate
a virtual desktop' in winecfg?

Cheers!

Hi Don,

I just gave it a try with "Emulate Virtual Desktop," simulating a 1024x768 desktop. The crash is not affected at all. (Interestingly, the issue with the stuttering sound in the intro movie is resolved when emulating a desktop.)

I think the bug you linked to in the Wine bug tracker is the same bug I am experiencing here. It definitely has to do with the OpenGL acceleration.

When I disable OpenGL acceleration using the Icewind Dale "Config" utility, the crash does not occur. However, disabling OpenGL introduces a new problem (when in full screen mode). The game is rendered about 2 centimeters too low, resulting in a black bar across the top and cutting off the bottom of the game. This is problematic when I need to scroll the screen because the game tries to detect when the mouse is at the edges of the game area in order to scroll the view. I can't scroll down because I can't move the mouse past the edge of the screen to reach the edge of the game area.

If I emulate a virtual desktop, the game area is positioned correctly in that window, but it is still very hard to scroll the screen. (I must carefully position the mouse within 1 or 2 pixels of the edge of the virtual desktop in order to scroll in that direction.) But it is impossible to play in Full Screen mode because either the game area is positioned too low (no OpenGL) or it crashes as described above (with OpenGL).

Is there any way to force CrossOver to confine the mouse arrow to the virtual desktop? This would help immensely with the scrolling. I tried checking the "Allow DirectX apps to stop the mouse leaving their window" in winecfg, but it doesn't work here.

Hi again,

Thanks for the feedback....guessing heavily (I don't own this title 8), I am supposing
when you disable opengl accel, the game probably falls back to directx7 rendering - this
might possibly account for the screen shift (although I can think of other reasons) --
you might try experimenting with other registry keys to see if there's some workaround
here...see the following page ;

http://wiki.winehq.org/UsefulRegistryKeys

The keys you likely want to play with, are DirectDrawRenderer , OffscreenRenderingMode,
and perhaps UseGLSL and/or RenderTargetLockMode. There's no rule of thumb here, the
results of changing these keys are app/videocard specific...but for example, with opengl
accel enabled, you might try DirectDrawRenderer=opengl -- you'll really have to 'suck it
and see' and explore what the various options do relative to the title's config settings.

As for the mousing issue, that would be winebug 6971 -- many apps are affected by this.
There is one registry key that might help this (although it doesn't work in all cases),
that being 'MouseWarpOverride' -- the valid values for this key are 'force' and 'force_edge'.

citing Ken Thomases;

"The other thing to try is the MouseWarpOverride setting in the registry. You can run regedit using CrossOver's Run Command dialog. Within the registry editor, navigate to HKEY_CURRENT_USER/Software/Wine/AppDefaults/<whatever>.exe /DirectInput. For each key that may be missing in that key path, you can create it using Edit > New > Key. Then, with the DirectInput selected, you do Edit > New > String value. Give the new string value the name "MouseWarpOverride" (without the quotes). For the value, try "force" or "force_edge" (without the quotes). You'll have to experiment to see which works best or remove the setting if it makes things worse."

Give these things a try and post back how you get on...

Cheers!

Hi Don,

Thank you for your help.

Unfortunately, it looks like the page you indicated on wiki.winehq.org which lists "Useful Registry Keys" either is outdated or does not apply to CrossOver games. I can use the "Run Command..." menu option to run "regedit" and bring up the registry editor. I can look through the trees of entries. However, there is no "Direct3D" category under "HKEY_CURRENT_USER/Software/Wine". I have looked around in regedit, and I did find Direct3D categories in application-specific folders under HKEY_CURRENT_USER (or HKEY_USERS)/Software/Wine/AppDefaults/<application folder>". These application folders correspond to programs I have never installed in this bottle, like "civilization4.exe", so they must be defaults included with CrossOver Games. There is no folder for Icewind Dale. (Nor do I see any way to create a new folder in regedit.) Therefore, I do not see any place where I could alter (or add) the DirectDrawRenderer, OffscreenRenderingMode, UseGLSL or RenderTargetLockMode keys.

I am afraid that I cannot access the "Bug 6971" to which you linked. When I click on the link, it takes me to a page with the warning message: "Access to Bug 6971 Denied! You are not allowed to access this bug. This is usually because the bug is restricted to certain user accounts." EDIT: Oh, now I see. The linking is done automatically by the CodeWeavers website and refers to a bug number which is non-existent in the CodeWeavers bug tracker. You were indicating the WineHQ bug http://bugs.winehq.org/show_bug.cgi?id=6971 . Yes, that seems to be the issue, assuming it is not intended for the mouse to be able to move past the edges of a Wine virtual desktop. (I can imagine this being intended behavior, as it would be helpful if you wished to work in both a Wine application and a native Mac/Linux application at once. Making this a user-customizable setting might make sense.)

I cannot follow the directions from Ken you quoted because they require the presence of a folder for Icewind Dale in HKEY_CURRENT_USER/Software/Wine/AppDefaults/

So I guess I didn't get very far this time around.

Jeff R wrote:

Unfortunately, it looks like the page you indicated on
wiki.winehq.org which lists "Useful Registry Keys" either is
outdated or does not apply to CrossOver games. I can use the "Run
Command..." menu option to run "regedit" and bring up the registry
editor. I can look through the trees of entries. However, there is
no "Direct3D" category under "HKEY_CURRENT_USER/Software/Wine". I
have looked around in regedit, and I did find Direct3D categories in
application-specific folders under HKEY_CURRENT_USER (or
HKEY_USERS)/Software/Wine/AppDefaults/<application folder>". These
application folders correspond to programs I have never installed in
this bottle, like "civilization4.exe", so they must be defaults
included with CrossOver Games. There is no folder for Icewind Dale.
(Nor do I see any way to create a new folder in regedit.)
Therefore, I do not see any place where I could alter (or add) the
DirectDrawRenderer, OffscreenRenderingMode, UseGLSL or
RenderTargetLockMode keys.

Apologies, I briefed over the instructions...you have to manually add the required keys
(and/or the application.exe) to the registry -- those key do not exist by default. The
applications you do see in the registry are defaults included in CX to account for certain
known program behavior -- the folks at Codeweavers include these as part of CXO/CXG's makeup.

Jeff R wrote:

I am afraid that I cannot access the "Bug 6971" to which you linked.
When I click on the link, it takes me to a page with the warning
message: "Access to Bug 6971 Denied! You are not allowed to access
this bug. This is usually because the bug is restricted to certain
user accounts." EDIT: Oh, now I see. The linking is
done automatically by the CodeWeavers website and refers to a bug
number which is non-existent in the CodeWeavers bug tracker. You
were indicating the WineHQ bug
http://bugs.winehq.org/show_bug.cgi?id=6971 . Yes, that seems to be
the issue, assuming it is not intended for the mouse to be able to
move past the edges of a Wine virtual desktop. (I can imagine this
being intended behavior, as it would be helpful if you wished to
work in both a Wine application and a native Mac/Linux application
at once. Making this a user-customizable setting might make sense.)

The C4 site logic sees 'bug' and automatically points to the CX bugtracker, not winehq's
(I keep missing that point ;)...but you figured it out. In emulated virtual desktop mode,
the win32 app (game) should capture the mouse, have the mousing working as expected, and
require the user to alt-tab to another application to release the focus grab. Not all apps
require this treatment, but as you see in 6971 a great many do....so far, no 'proper' fix
has been created/provided to fix 6971...the only way to effectively work around it at
present, is to run such games fullscreen where possible (where it's not possible, it a real
pain with no easy resolve)...

Jeff R wrote:

I cannot follow the directions from Ken you quoted because they
require the presence of a folder for Icewind Dale in
HKEY_CURRENT_USER/Software/Wine/AppDefaults/

So I guess I didn't get very far this time around.

See above -- you have to manually add the game exe into the Applications Settings of the winecfg
Applications tab (or in regedit), and then manually add the required keys under that. Sorry I
wasn't a bit more verbose with the instructions previously ;)

Cheers!

Afraid I still can't get it.

I added the game, IDMain.exe, in the Application Settings of the winecfg Applications tab. (I see no way to add the game in regedit itself. The only things I can create in regedit are string, binary, DWORD, and multi string values.)

Making this change added IDMain.exe to several places in regedit:

HKEY_CURRENT_USER\Software\GNU\ffdshow\blacklist
HKEY_LOCAL_MACHINE\Software\Black Isle\Icewind Date - Heart of Winter\FullPath
HKEY_LOCAL_MACHINE\Software\GNU\ffdshow\blacklist
HKEY_LOCAL_MACHINE\Software\GOG.com\GOGICEWINDDALE1\EXE
HKEY_LOCAL_MACHINE\Software\GOG.com\GOGICEWINDDALE1\EXEFILE
HKEY_LOCAL_MACHINE\Software\GOG.com\GOGICEWINDDALE1\LAUNCHCOMMAND
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths
HKEY_USERS\S-1-5-4\Software\GNU\ffdshow\blacklist

Unfortunately, none of these is the correct place to add the four Direct3D-related entries you mentioned, which according to the "Useful Registry Keys" page is HKEY_CURRENT_USER\Software\Wine\Direct3D

I've just about reached the limit of effort I'm willing to expend trying to get this game to work. It's a shame there isn't a better UI for making these sorts of registry changes.

Anyway, I hope that the crash log and the info in this thread may help the developers debug the problem someday...

Hi,

You want HKEY_CURRENT_USER/Software/Wine/AppDefaults/IDMain.exe

Then add to that the subkey entry as required (direct3d or whatever);

HKEY_CURRENT_USER/Software/Wine/AppDefaults/IDMain.exe/
\Direct3d

Then add to that subkey, the required string & data setting(s);

HKEY_CURRENT_USER/Software/Wine/AppDefaults/IDMain.exe
\Direct3D
\DirectDrawRenderer opengl

You would do the same as required for DirectInput...ie;

                                                    \DirectInput  
                                                                 \MoursWarpOverride   force_edge

Hope this helps...

Cheers!

I'm having this exact same problem with IWD in CXG on my Macbook Pro, in OSX 10.6.4. It's definitely an OpenGL issue; toggling OpenGL in the Config tool makes the problem vanish and reappear.

So far, I've been playing with OpenGl enabled, as it makes the game performance, especially the mouse cursor, significantly better. When I encounter an area-change crash, I disable OpenGL in the Config tool, move through the area transition, and then re-enable OpenGL on the other side. So far, this has been working well for me, though I'm not very far into the game yet.

And, of course, it'd be spiffy if the underlying OpenGL bug were resolved.

Same here. It's definitely an OpenGL issue that was introduced with Trials of the Luremaster. I really, really do hope this gets resolved soon, because the way I have to play the game now (with OpenGL enabled) is only half the fun. Pity, because it's such a great game.