Open kero990 opened 2 years ago
Can you try without dynarec (with BOX86_DYNAREC=0
env. var.) and see if you have the same behaviour?
The problem is still Moreover, after executing BOX86_DYNAREC=0, the running speed of the game drops seriously, and the menu is still invisible. Judging from the sound feedback, it takes 10+ seconds for the interactive behavior of menu clicks to complete, and the speed after entering the game cannot be played normally. But importantly, the menu is still invisible.
My box86 was integrated into lutris by others, not compiled by myself, so I don't know whether its running environment is normal or not. Is this a bug of box86 or a case of my program.
Yes, using BOX86_DYNAREC=0
makes box86 much slower, o it's not a proprer solution, but it's to understand if it's a problem specific to the Dynarec of box86 or a more generic one.
It seems it's a more genereic one: it will be more difficult to track down.
I need to reproduce the issue on my side first.
Is the problem still here or can this ticket be closed?
I have already explained the related issues in the issue of ra2, and they are officially submitted to the box86 issue here. https://github.com/ptitSeb/box86-compatibility-list/issues/44
Chinese users, the hardware configuration is ft2000 cpu (I seem to see its compile option in the latest cmake), when running ra2 and Diablo II with the cnc-ddraw patch, ra2 loses all menu gui elements, including custom campaigns , the faction selection page of the campaign, and opening the settings menu in the game, all will be lost and displayed, but you can operate blindly. The game content is normal, but everything is normal with the cnc loader, but this loader can't play the campaign.
Diablo II is to click on the page where the 4 attributes of the character are added, and the game will crash directly. There is no problem with other sub-pages, and the game itself has no problem.
The above operations have been tested directly with wine on the x86 platform, and also tested on arm64 with exagear+wine, and there are no similar problems, so I guess there are some incompatibilities between box86 and ddraw.
I don't know where the log of box86 is, I can provide the corresponding log under your guidance.