-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
SteamApi_Init() fails on latest version #1200
Comments
you launch steam game on mobox? or is it some other solution? Is taht a windows version of steam or linux version? And what game what is? |
i'm running guilty gear strive on wine ge 8.13, it's pirated version of the game, i assume it uses goldberg steam emu. it was always working without steam, like any such game should work, but just in case i tried to start it while steam was running - same issue |
Ok. It would be nice to do a bisect to find the offending commit, but I know it's difficult to do in mobox. |
i can do that in termux-box, it have same issue, but uses proot/chroot so i can compile it myself |
That would be very helpfull! |
i made the bisection. it seems that 5e9e1fa made the issue |
Oh, the memory tracking change? that's strange. Well, ok, I'll have a deeper look at that tomorrow. Thanks for the bisect. |
issue is still there on latest version (with merged pr) |
same here |
fixed now |
i had a box64 version from +- December 12, just updated to latest one and it seems that steamapi in unreal engine games is no more working (it was working fine just before the update)![Screenshot_2024-01-12-20-54-22-823_com termux x11](https://private-user-images.githubusercontent.com/71220271/296322519-f3392acf-145f-4124-b314-696cc7831d97.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA2Nzg2ODcsIm5iZiI6MTcyMDY3ODM4NywicGF0aCI6Ii83MTIyMDI3MS8yOTYzMjI1MTktZjMzOTJhY2YtMTQ1Zi00MTI0LWIzMTQtNjk2Y2M3ODMxZDk3LmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzExVDA2MTMwN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQwMjRmYWRlYzE1YTJkYmI2MjY4ZTQzNTkwNWY3NDBkOTM4ZGJjNjMyZTFjN2UwMjRkNmJiZDgwYWRhZDljZWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.bp8JH2Ylfa1tzjA6Zinn7J-j9NhyDZuC8sLrxQKonVo)
the log after dxvk initialization is only those 2 lines:
The text was updated successfully, but these errors were encountered: