[Wine] Re: Duke Nukem Forever Demo (Steam) not launching

Quix0r wineforum-user at winehq.org
Fri Aug 5 12:28:56 CDT 2011


Okay, correction. :) I use WINEPREFIX with plain wine.

And yes, other 3D games work fine. So the most crashes are because the demo exe is in bad shape? Gearbox should fix that then. Here is an except from the console output:


> wine: Unhandled exception 0x80000003 at address 0x5ebc4a (thread 002f), starting debugger...
> fixme:dbghelp_dwarf:compute_location Only supporting one breg (edx/19 -> edx/19)
> 0x005ebc4a: int $3
> Modules:
> Module  Address         Debug info  Name (170 modules)
> PE    340000-  41d000   Export          dncommon
> PE    420000-  427000   Deferred        3drdebuglib
> PE    430000-  5dd000   Deferred        meqon
> PE    5e0000- 102f000   Export          engine
> PE   1030000- 1046000   Deferred        xinput1_3
> PE   3bc0000- 3be1000   Deferred        cserhelper
> PE   3d00000- 3d91000   Deferred        gameoverlayrenderer
> [...]
> More lines ...
> [...]
> Backtrace:
> =>0 0x005ebc4a in engine (+0xbc4a) (0x0031d250)
>   1 0x00355f4c in dncommon (+0x15f4b) (0x0033d264)
>   2 0x0088c90d in engine (+0x2ac90c) (0x0033d2c8)
>   3 0x007fe67a in engine (+0x21e679) (0x0033f3fc)
>   4 0x00818fb4 in engine (+0x238fb3) (0x0033f92c)
>   5 0x1090e49f in dukeforeverdemo (+0xe49e) (0x0033fe10)
>   6 0x1090fe7a in dukeforeverdemo (+0xfe79) (0x0033fea0)
>   7 0x7ed6c18c call_process_entry+0xb() in kernel32 (0x0033feb8)
>   8 0x7ed6d190 start_process+0x5f(peb=0x7ffdf000) [/home/quix0r/git/build/wine/dlls/kernel32/../../../../wine/dlls/kernel32/process.c:1087] in kernel32 (0x0033fef8)
>   9 0x7efa1c98 call_thread_func+0xb() in ntdll (0x0033fef8)
>   10 0x7efa64db call_thread_entry_point+0x6a(entry=0x7ed6d130, arg=0x7ffdf000) [/home/quix0r/git/build/wine/dlls/ntdll/../../../../wine/dlls/ntdll/signal_i386.c:2499] in ntdll (0x00000000)


I still have the +d3d logfile, shall I upload it to the bug tracker (which ticket)?







More information about the wine-users mailing list