ptitSeb
ptitSeb
Bah, don't bother with the change, I have just made it default now. So you just need to update to latest box64 and try again (no source code changes needed).
Ah yes good. I'll check that next week.
> Can confirm that DF itself now works entirely as expected; DFHack (a very commonly used modding utility) does not—but that looks to be tied to using ARM64 versions of...
> @ptitSeb I suppose this `!` is related to something that's not yet supported by box64? The `!` means it's a pointer to a structure that might need special care,...
Yeah, but that's an unsuported opcode for now, even on the interpreter. It's some "dead code" for now (branch of code never executed because the cpu flag doesn't have a...
memory protection is tricky on box64. It's tracked and used as part of the dynarec. That being, said, `mprotect` have no more reason to fail under box64 then on native....
> So it was just a check on dfhack's part that seems to be somewhat wrong, it checks that memory is allocated contiguously for no obvious reason, and it's not...
I don't think Crossover use Box64 for 32bits binary, even if wowbox64 exist. Portal 2 from Linux Steam works with box64+box32. It migtht crash at exit tho, but you can...
> They mentioned in their blog post on [Arm64 support for CrossOver Preview](https://www.codeweavers.com/blog/mjohnson/2025/11/6/twist-our-arm64-heres-the-latest-crossover-preview), so I was testing that — but I want to see how it runs on Box64 as...
We should get an error message instead of a panic