ptitSeb

I don't think it's the issue. Those functions are wrapped already. They are not found, but that's probably normal and handled by the program. The issue is ``` 16271|SIGBUS @0xe...

Does those message ``` nvdc: start nvdcEventThread nvdc: nvdcEventThread select failed: Bad file descriptor nvdc: start nvdcEventThread nvdc: nvdcEventThread select failed: Bad file descriptor nvdc: start nvdcEventThread nvdc: nvdcEventThread select...

not sure what is happening. Try to update both box86 and box64 first, as a lot of wine/proton work as been done lately. It might just fix the issue.

This seems to be related to wineprefix issue, when mixing 32bits and 64bits version. have you tried to remove your `.wine64` prefix?

you don't need to use WINEARCH, at least, I don't use it on my side, and it works fine. Try to run with `BOX86_LOG=1` to have more detail with box86.

Are you sure your 64bits version of wine is complete? the last error `wine: could not load ntdll.so: Cannot dlopen("/home/pi/wine/bin/../lib64/wine/x86_64-unix/ntdll.so"/0x6ae32210, 2)` seems to indicate box64 cannot find the file. Does...

You can't. It's automatic. Can you do `file /home/pi/wine/lib/wine/i386-unix/libwine.so.1` and `file /home/pi/wine/lib64/wine/x86_64-unix/ntdll.so`

Mmm I think the 32bits llibwine loding message is just from box86, not the box64 there. So the question is why box64 doesn't load that lib. Try to run with...

I don't see anything wrong in those logs. And logs from box86 and box64 are mixed, making it difficult to follow. Did you try to run without the `WINEARCH=win64` (I...

ok, because I don't see what's is happening, you need to use `BOX86_LOG=1 BOX86_TRACE_FILE=$(pwd)/trace-%pid.txt BOX64_LOG=1 BOX64_TRACE_FILE=$(pwd)/trace-%pid.txt` to launch your program. It will generate 1 trace file per process, so things...