Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphic glitches in Warcraft 3 1.26 #1366

Open
askorbinovaya-kislota opened this issue Mar 16, 2024 · 8 comments
Open

Graphic glitches in Warcraft 3 1.26 #1366

askorbinovaya-kislota opened this issue Mar 16, 2024 · 8 comments

Comments

@askorbinovaya-kislota
Copy link

bisected the issue to this commit: a5a7d93

glitches look like this:

Screenshot_2024-03-16-22-29-05-965_com termux x11
Screenshot_2024-03-16-22-29-12-182_com termux x11

and that's how the game menu should look like:

BOX64_DYNAREC=0

Screenshot_2024-03-16-22-30-39-539_com termux x11
Screenshot_2024-03-16-22-30-43-050_com termux x11

simply disabling bigblock (i thought that commit referenced something about it) partially fixes the glitches, but cripples the menu even further:

BOX64_DYNAREC_BIGBLOCK=0

Screenshot_2024-03-16-22-34-45-678_com termux x11
Screenshot_2024-03-16-22-33-33-530_com termux x11

and with the safest dynarec options, the menu is almost fine, with a different glitch affecting the water (x87double fixed the menu):

BOX64_DYNAREC_BIGBLOCK=0 BOX64_DYNAREC_SAFEFLAGS=2 BOX64_DYNAREC_STRONGMEM=2 BOX64_DYNAREC_FASTROUND=0 BOX64_DYNAREC_FASTNAN=0 BOX64_DYNAREC_X87DOUBLE=1

Screenshot_2024-03-16-22-38-54-458_com termux x11

none of those issues appeared on bc770d9 (a5a7d93 - 1). i've checked the issues, and it seems that no one reported exactly those glitches, but a comment at #1364 states that many games are broken on a version after march 11; the commit after which the issue happened was made on march 10, so i think they had exactly the same problem

i'm testing on android and my cpu is snapdragon 750G

@ptitSeb
Copy link
Owner

ptitSeb commented Mar 16, 2024

That commit? This is really stronge. I reproduce the inssue on my side, and confirm your result. I'll work on that to see what's wrong (but it maign take time as I'm not home and will have little time this week for box64 dev.)

ptitSeb added a commit that referenced this issue Mar 19, 2024
…ould be revisited soon, to many bytes writen there)
@ptitSeb
Copy link
Owner

ptitSeb commented Mar 19, 2024

I pushed something, it should be better now, if you can update and test.

@askorbinovaya-kislota
Copy link
Author

no glitches on latest commit, works fine now

@BloodANGELdb
Copy link

BloodANGELdb commented Mar 19, 2024

I pushed something, it should be better now, if you can update and test.

I confirm that there are no more graphical bugs. But there is one significant mistake left? on versions from the beginning of the month everything worked perfectly, the wine prefix loaded in a second, Now if you enable "WINEESYNC=1, WINEESYNC_TERMUX=1" the prefix will load in 30-60 seconds.

Another problem is that the GPU caps viewer refuses to show tests, it simply freezes.

@airidosas252
Copy link

3384640

This commit actually causes Wine to start up very slowly. It also causes two winedevice.exe instances to appear. After reverting this - everything goes back to normal.

It also caused Mass Effect Andromeda to hang while trying to launch it.

@askorbinovaya-kislota
Copy link
Author

i also encountered freezes (in warcraft 3) on new version, but i thought it was wine issue...

After reverting this - everything goes back to normal.

i'll try reverting to see if freezes go away

@askorbinovaya-kislota
Copy link
Author

i'll try reverting to see if freezes go away

can confirm, no freezes if i revert that commit

@ptitSeb
Copy link
Owner

ptitSeb commented Mar 20, 2024

This commit is important. I'll try to check later why it cause some regressions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants