Endless Legend crashes on start

[clapbr]

Tried virtual desktop and same problem. It goes fullscreen then stays black. wined3d backend starts fine

[iiv3]

I assume that the game starts with wined3d. Try to make an apitrace using wined3d, then replay it using Nine. If it doesn't work with wined3d, then you may need to use real windows.

If the trace crashes then send it to us.

If it does not, then you will need a mesa compiled with debug support, running the game under Nine with NINE_DEBUG=all. Send us the log

To make apitrace, download the latest msvc build from the site, put the d3d9.dll wrapper in the game directory, in winecfg add Library override for d3d9.dll as native, built-in. When you run the game it should create a trace file in the game directory or in the wine Desktop.
Be sure to remove the wrapper and override when done, it could eat your hdd space.
If you want to send the trace, you can ask for our ftp server or upload it to google drive. We will keep the trace and may use it for regression testing. Don't forget to compress it.

[axeldavy]

Which version of Mesa ?
Unfortunately we have a regression which affects mesa 18.3.2 (18.3.1 is fine) and mesa git.

[clapbr]

Didn't have time to record the trace yet but I can soon.
@axeldavy Latest mesa-git, I have a script that builds it every night. Do you have a link to the report if there is one?

[axeldavy]

The patch is on this github
https://github.com/iXit/Mesa-3D/commit/2fbed0fa616360edd6cf12e1d77dc6f345cba43a.patch
Hopefully you have the same issue than the affected games fixed by this patch.

[clapbr]

Thanks but the patch didn't help this case. Attaching the crash logs
error.log
output_log.txt
crash.zip (crash.dmp)
Let me know if it gives any clue or you need traces.

[axeldavy]

Sad to hear that.
I don't manage to see anything stand out in these logs. Maybe you could produce the log with NINE_DEBUG=all csmt_force=0 ?
csmt_force=0 disables csmt (better for logs that make sense)
NINE_DEBUG=all prints a lot of debug info. Mesa needs to be built with --enable-debug if you use autoconf, or defined ndebug with this patch https://github.com/iXit/Mesa-3D/commit/09c62b50ae2c0088e581c2cc1c9a23dcdd9f3597.patch

[clapbr]

Check if this got what you need
steam-289130.log
if it doesn't, what should I change in mesa config for all debug with meson?

     -D b_ndebug=true \
      -D buildtype=release \
      --wrap-mode=nofallback \
      -D prefix=/usr \
      -D sysconfdir=/etc \
      -D platforms=x11,wayland,drm,surfaceless \
      -D dri-drivers= \
      -D gallium-drivers=radeonsi,svga,swrast,virgl \
      -D vulkan-drivers=amd \
      -D dri3=true \
      -D egl=true \
      -D gallium-extra-hud=true \
      -D gallium-nine=true \
      -D gallium-omx=bellagio \
      -D gallium-va=true \
      -D gallium-vdpau=true \
      -D gallium-xa=true \
      -D gallium-xvmc=false \
      -D gbm=true \
      -D gles1=true \
      -D gles2=true \
      -D glvnd=true \
      -D glx=dri \
      -D libunwind=true \
      -D llvm=true \
      -D lmsensors=true \
      -D osmesa=gallium \
      -D shared-glapi=true \
      -D gallium-opencl=disabled \
      -D valgrind=false \
      -D tools=[]

[axeldavy]

No, the log doesn't have useful information.

for NINE_DEBUG=all to work, you need the patch I linked to, and -D b_ndebug=false

[clapbr]

Ok, did all that, seems nine messages are there now
steam-289130.log
.

[axeldavy]

Indeed, the messages are here.
I don't know however what causes the crash, because the last function with message does a lot of things, including making calls to the wine part of nine. Could you also enable the debugging for it ? The debug channel is d3d9nine, so probably is should be WINEDEBUG=+d3d9nine, but I'm not sure about the syntax.

[clapbr]

I ended up playing it with wined3d and giving up on this but if someone want to try fix it Endless Space is free now and runs on same engine as this and has the same issue. Get it at https://steamcommunity.com/games/endless-space/announcements/detail/1703951743101167654