I'm posting to this list as a result of the instructions on the "AppDB Maintainers" page.

Anyway, Endless Legend (https://appdb.winehq.org/objectManager.php?sClass=application&iId=16492) was broken somewhere between 2.17-staging and 2.18-staging.  While the initial credits videos load alright, the game's own loading splashscreen (for the Tempest expansion) crashes without fail.  If I run Wine 2.18-staging in a terminal, the error messages look like this:

fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #11:
fixme:d3d_shader:print_glsl_info_log     Vertex info
fixme:d3d_shader:print_glsl_info_log     -----------
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[0].zw" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[1].zw" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[2]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[3]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[4]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[5]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[6]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[7]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[9]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[11]" might be used before being initialized
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
err:seh:setup_exception stack overflow 1600 bytes in thread 0096 eip 000000007bc62c85 esp 00000000053e0fd0 stack 0x53e0000-0x53e1000-0x54e0000
fixme:shell:CustomDestinationList_QueryInterface not implemented for {00000003-0000-0000-c000-000000000046} (unknown)
fixme:shell:CustomDestinationList_QueryInterface not implemented for {00000003-0000-0000-c000-000000000046} (unknown)
fixme:shell:CustomDestinationList_QueryInterface not implemented for {00000019-0000-0000-c000-000000000046} (unknown)
fixme:shell:CustomDestinationList_BeginList 0x5385410 (0x1284e52c {92ca9dcd-5622-4bba-a805-5e9f541bd8c9} 0x1284e538): stub
fixme:shell:CustomDestinationList_QueryInterface not implemented for {00000003-0000-0000-c000-000000000046} (unknown)
fixme:shell:CustomDestinationList_QueryInterface not implemented for {00000003-0000-0000-c000-000000000046} (unknown)
fixme:shell:CustomDestinationList_QueryInterface not implemented for {00000019-0000-0000-c000-000000000046} (unknown)
fixme:shell:CustomDestinationList_BeginList 0x5384490 (0x12a4e52c {92ca9dcd-5622-4bba-a805-5e9f541bd8c9} 0x12a4e538): stub

If I run Wine 2.17-staging in a terminal, then I get only the following:

fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #263:
fixme:d3d_shader:print_glsl_info_log     Vertex info
fixme:d3d_shader:print_glsl_info_log     -----------
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[2].zw" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[3].zw" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[5]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[6]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[7]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[8]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[9]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[10]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log     0(19) : warning C7050: "vs_out[11]" might be used before being initialized

So, it seems safe to assume that something in 2.18 causes all of those page faults.


Cheers,

Walt