GOG.com - The Black Mirror II

I think the issue is that for some reason there is a BlackMirror2 folder in my Home directory, instead of being in it's Virtual Drive. Thus, I guess, the game crashes as it doesn't have a permision to write anything in that folder. How can this be fixed?

The programs you run in Wine have your rights, so that shouldn't be the issue

The save game folder being in your home directory is normal. Quite a few games put save game files and similar there as your linux user home folder is symlinked as the windows user folder. As for the crash, I didn't experieince it on my computer. However, if you can share a debug output, maybe there will be some ideas?

Thank you for the attention guys. Well, I don't think that there is anything very interesting in the Debug code, but I can share it:

Running wine-1.6.2 BlackMirror2.exe (Working directory : /home/vilius/.PlayOnLinux/wineprefix/TheBlackMirrorII/drive_c/GOG Games/Black Mirror 2)
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16B16A16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f5c8,0x00000000), stub!
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16B16A16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32e5a8,0x00000000), stub!
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16B16A16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32e3a8,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:dbghelp:elf_search_auxv can't find symbol in module
fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithDataSegs
I think only one or two last lines appear when the game crashes.

last two lines are a consequence of the crash, so it's not useful

I've compared your debug output with mine, and just two entries stand out:
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
It's there twice in your debug, but not mine. Otherwise looks the same. So, I'm not certain they're the cause, but they may be a clue. As they relate to graphics/direct rendering, you could check that direct rendering is working on your linux installation? I'd also try using a virtual desktop. Also, using your system version of wine to see if it behaves differently.

I've checked with glxinfo that direct rendering works. My default wine version is 1.6.2, the same as required for the game. I can in fact install the game just via wine, but have exactly the same problem as if installed via playonlinux. It could be that my graphics card is just too old (Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller) (but then it's strange that the game starts at all). I can try to run it via virtual desktop, but I'm not sure if that's going to help. Thanks for the help anyway :).

Virtual desktops can help with various problems, but admittedly it's just a general idea that has often helped me in the past when graphics do odd stuff. It's an easy test, but you do need to get the resolution right in many cases to avoid an instant crash. The system version of WINE may be 1.6.2, but to be clear, that doesn't mean all the WINE bottles you have using 1.6.2 are the system version. It's still distinct and may be set up with some specific features that are absent in the others, so to be sure you're using it you need to select it specifically in the WINE version list. Games can crash at all kinds of points, simply because it's the first time they've attempted to do the thing that does not work. Changing resolution and playing audio are common crash points I've found in other games. However, I have played this game to the end in WINE, so it can potentially work, I just don't know at the moment what is different between your computer and mine

Excellent. Thanks. Approved.

Looks good. I would change WORKING_WINE_VERSION to simply WINEVERSION, though. That is a little more concise and more standard.

Looks good to me, or I'll have to change 250+ scripts ;)

Thanks Ronin. That makes sense, I'll change it over.