#Destiny Rising on Bazzite/Waydroid
1 messages · Page 1 of 1 (latest)
Yup. Same thing happening to me. I downloaded Waydroid on my Deck specifically for Rising, so fingers crossed it gets sorted.
Glad I'm not the only one!
It's happening to me as well and I just installed waydroid on my deck.
Yeah, same here. Really hopeful it gets fixed.
yeah no luck with waydroid so far
I wouldnt be supprised they did this on purpose. Anyone tried running mumu via proton?
I don't think it's possible to even run Mumu that way
I did, no go.
Well it definitely didn’t work, so probably not
Thanks for the confirmation
Just to check are you using the testing builds or the stable?
Same issue here on a freshly installed waydroid 🙁
thought I was finally getting it to work on linux
We have to wait for the game to update in case they messed up something with the beta build, otherwise this is intentional for waydroid to be exluded, so that everyone would only use mumuplayer for destiny rising.
And since mumuplayer aint running on Steam Deck, we are Joever
It may, i have something yet to try
Please upvote these:
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
#📮│suggestion-voting message
Cross posting:
#1410298851050655784 message
#1410616943353794610 message
#1413107425925529651 message
done. I would love to play it on my steamdeck instead of my pc, as I feel like my pc is the main cause for the high pings randomly.
Strangely enough, I've tried to play Eve Echoes on Bazzite/Waydroid, which is made by same company Netease, and I've managed to make it work by switching the "use_subsurface true", until the server banned me for a bogus environment reason. Maybe this is related to the hardware properties.
I've tried the same with DR but the game is force closing and restarting at the screen asking for accepting the terms, because pressing the back button repeatedly it will briefly show a popup telling that you cannot play the game without accepting them.
I remember I've seen something similar on a different game on WSA and it was related to webview settings, at first the game was not working but eventually after an update it could be playable.
Considering that on Bluestacks DR can only run on Android Pie64 instance which is version 9 and Waydroid is running version 13, maybe this is one of the reasons that makes the game boot loop.
no the issue is across all android versions
They have disabled it running on anything not a phone or tablet that's official based. i have traced the issue and the moment it detects none official rom based on x86/Linux and not arm64x the app force closes. They also have whitelist of what android emulator are allowed to work with x86 but good luck getting anything third party whitelisted.
Yeah they havent even enabled it on googles play games for pc so im pretty sure 100% intentional to keep people using their stuff
Well it’s counter intuitive to disable with such a hard lock 🔐 because their method is not golden!!
Yup, i kind of understand not supporting linux directly but dunnot why all forcing of mumu which isnt perfect by anymeans
Is there a way to spoof hardware properties like BS is doing?
I've tried a script that spoofs Pixel 5 properties onto Waydroid, but no change in DR
only way to get it to work from what ive seen is to dualboot win11 on a deck
something I am not willing to try but i reallllly want to
It runs like ass btw, already tried it
me too. In general, windows 11 gives me much much worse performance compared to any modern linux distro for some arkane reason and I just cant figure out why other tyhan the fact that windows is ass.
True
Cant we like, idk, make a petition about porting the game to steam or at least for the devs to make an official linux emulator or sokmething? I would genuinely spend my money on that if the price is reasonable
does destiny work under waydroid? Have you tried?
No it doesnt
Just bootloops
I think i gotta stick to scrcpy then. There's a little delay but it is playble overall
scrspy?
nvm
What?
Delay? That’s not good…
It's not that bad come on
Sounds like input issue
The gamepad is connected directly to the phone
Then your gamepad is malfunctioning
No it doesn't have any delay on the phone screen
The delay is of the video stream
Do you have any buffering set up on your scrcpy launch parameters? Have you tried switching codecs?
Another Linux-related suggestion to upvote: #📮│suggestion-voting message
so i can confirm that the game works but you need to redownlooad the files or you get stuck in bootloop as workaround after app exit/crash
Same here. I'm running waydroid on weston, redownloading the game does make it pass the bootloop
edit: nevermind it still bootloop after first restart
same, no luck here. I managed to get past the loop boot on the first boot, but I couldn't log it, it said that it couldn't find the google account, even if google services were installed (game downloaded from google play). Then on subsequent boots it loop boots again
Logging debugging the app is required to find the fault and what’s not activated that’s causing the issue. It can be simple as some permissions not turned on causing the issue
It did complain about not being able to connect to server when I try to login via google (something like error code 10400?) though I'm having working connection on the emulator and file downloading before that worked fine
apart from that the error logs from the app seems similar to the ones emitted before (when even the first boot loops) so I'd say it's still the same issue, not sure tho
Did you have your waydroid set up with GAPPS?
If you mean -s GAPPS on waydroid init then yes
I installed waydroid and DRising today on Fedora 42 and i didn't get any bootloading but i got the message, that my device isn't supported and i should use mumuplayer
I'm also on Review but only get this site on subsequent logins (which is avoidable by selling app data and redownloading everything each time).
Still not good enough IMHO, at least till the mouse issue doesn't require replugging it...
i also noticed at first boot i could actually launch the game, but it started a new account. I already have an account on my phone. Is there a way to play on the same save? (same google account btw)
To bypass "unsupported device" prompt: https://github_com/waydroid/waydroid/issues/1607#issuecomment-3340817418 (replace underscore with the . symbol)
To log into the game with google account, you need to set waydroid up with GAPPS:
https://jambitlabs_com/waydroid-set-up-with-google-play-gapps/ (same replacement as above)
@gusty pivot Hope this helps.
I managed to get Rising working with the guides from here on my PC's Bazzite installation. However, I'm getting this weird cut-up video issue when I have the resolution set to match my monitor, 1440p. https://imgur_com/a/LsKfGSy
I'm running KDE Wayland, Bazzite desktop with a 9070XT. Waydroid multi-windows enabled or disabled doesn't change it. If I go to 1080p resolution it seems to work fine?
Further inspection, it seems to do so whenever I go outside of Destiny Risings like, "preset" resolutions? Like I can scale vertically down to a phone size, and up to just under my full resolution with no problem. But as soon as I scale it beyond these goldilock resolutions it just does the thing above.
Game works now. Thank you
Crass save wasn't working because i used my discord account on my phone and not my google account. Switched account and everything was back
Any solutions to mouse pointer lock? didnt know if i may have passed over it between the two discussion boards.
Currently just doing wayland+weston controller for now
No solution for the desktops affected AFAIK.
Does anyone know how to add shortcuts to GameMode? I can get the spoof going fine but would like to just boot directly from game mode]
What OS/VM ?
To clarify my previous message, KDE Plasma (wayland) appears to be the only currently known desktop environment where Waydroid locks the cursor properly.
that is correct 🙂