This is what i'm getting:

fixme:lsa:LsaGetLogonSessionData 0x32ebf8 0x32ec08 stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32e780,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d7f4,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32cb48,0x00000000), stub!

and a black screen with:
"(null): Error: Error #3694"

This error is .. hum... not very explanatory..

If anybody finds how, share your solution ;)

When looking for this specific error in google, i found a pirate site where someone with windows7 had the same issue on evoland.

Would be great if they could fix, i can't report as i'm a linux user and they will say my report is bogus.

I have the exact same issue. Interesting would be to know what video card and driver the Windows users who encounter this issue have. While this is just a guess, I suppose it is an issue with the video card support (or opengl / directX support). Like I said it is just a very wild guess :(

This is related to this part of the code:

github.com/ncannasse/h3d/commit/8564d1093baa74d84dd59f41432eaab329d53fba

Somehow ctx.configureBackBuffer fails but i don't know if it's a wine bug, an AIR bug, a bug in the game etc.. ;/

Someone on steam: Someone else: And another: Many many people on win7/8.

I myself have an nvidia 635M..

Interesting I actually have an Intel video card (Sandy Bridge on my core i5) :/

I've been looking around and, according to this PlayOnLinux thread, it's definitely something acceleration-related because, if you run it in a copy of real Windows under VirtualBox, you get that error if you don't have the 3D guest drivers installed.

Another user figured out that it's possible to get it running under Wine/PlayOnLinux (albeit, a bit slowly) if you install Firefox and Flash in your WINEPREFIX and use Flash's preferences panel to to turn off 3D acceleration in Adobe products. (I can confirm this. It displays "Error #3219" but runs anyway.)

This StackOverflow question suggests that error #3694 might be caused by a fragile resize handler that doesn't know how to deal with being called after the old drawing context was disposed of but before the new one has been created. (Which would suggest that it could be either the fault of Wine and certain real Windows installs for "not matching Windows closely enough" or the game's fault for not being robust enough.)