Instalar o Steam
Iniciar sessão
|
Idioma
简体中文 (Chinês Simplificado)
繁體中文 (Chinês Tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Checo)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol de Espanha)
Español-Latinoamérica (Espanhol da América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polaco)
Português (Brasil)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar problema de tradução
Regras e Orientações das Discussões
1 
Denunciar este post
Just wanted to test it, but I get the following error while trying to execute the game on my Steamdeck:
https://gtm.you1.cn/sharedfiles/filedetails/?id=2889736139
Whoa. It works on ThreeSon's Steam Deck, and I don't have my own at this time to test it out...
I just pushed an update which changes compiler target to basic 386/486 CPU and sets optimizations to minimum. It will probably crash again, but can you please post the new screenshot of that message when it does?
The patched version should say "v2.54" on the bottom, as opposed to 2.53. Well, if you ever get to the menu, that is...
unisntalled and installed again to try to ensure the new version is installed
same result, note: the number changes between errors every time I try it
https://gtm.you1.cn/sharedfiles/filedetails/?id=2890035824
https://gtm.you1.cn/sharedfiles/filedetails/?id=2890035832
That's strange. It should've shown a more detailed message than just a memory address.
Does your Steam Deck have any unusual customizations? Such as, maybe you installed some beta proton drivers?
I changed the video initialization method. Can you please try again? You can force the game to update by going to properties in Steam and doing "Verify integrity of game files".
Now I tested to unisntall the game, remove proton files and gamepad configuration. And installed and tried again. Same result :(
No idea what I could do to help you investigate.
Thank you, but did you do this after my second post? I literally pushed an update minutes ago.
just tested it again, same error
I don't really know if the game is updated or not in the Steamdeck, I can sse that the game Compilation ID is 9967011
Aaaand I just pushed the last renderer calculation update for the night. Thank you for your patience... the new ID is 9967378.
I created a beta branch for Monsterland called "steam deck test". Steam client may not show it until it is restarted. Can you please try running it from that branch?
NOTE: what you will run is an abandoned version of Monsterland engine, it's not the actual game. It is not Steam Deck ready, it doesn't have menues or a campaign, but all I would like to know if it actually loads and displays things. It is sufficiently different from Monsterland itself, so the fact that it loads, would give some idea on where the crash ISN'T happening.
I'll give a try into that branch a bit later and I'll reach you
Thank you. However, it is statistically improbable that it's only you. You're probably the 2nd person to run Monsterland on a Steam Deck and it doesn't work on yours, so there are probably many more like you, hence I would like to figure out what's going on here.
Monsterland is very basic when it comes to rendering things. It uses SDL 2.0, a widely used library. Maybe there's something about the sound library... Either way, you running the test branch should help me narrow it down a bit more.
Hi Dexter. Although, like your friend, I have not encountered this problem with Monsterland, I have encountered very similar problems in many other games on my Deck, even very popular Verified games like Horizon Zero Dawn, where the game will simply not launch or will give an error message the first time I try to play it on the Deck.
Based on that experience, I am also 95% confident I know a workaround that will permanently fix it for you.
All you need to do is to launch Monsterland once using GE-Proton instead of the default Proton. Once you've launched it with GE a single time, the error should go away permanently and you can resume using normal Proton to play the game in the future.
If you don't have GE-Proton on your Deck yet or you don't know how to install or use it, there's a pretty good 3-minute tutorial here: https://www.youtube.com/watch?v=IHAkFFQFAHw
If anything in that vid is not clear I'd be happy to answer any questions you have. I would suggest simply downloading the most current version of GE-Proton, which I believe is 7-41 as of today.
If for some reason this fix does not work, let me know.
As for why Monsterland (or other games) don't work with normal Proton until you've launched it once with GE-Proton, I honestly don't know. It's a longstanding bug that's been around on the Deck for several months at least.
I think it has to do with the Linux Steam client not correctly installing a game's prerequisites (e.g. DirectX, Visual C++, .NET, and so on). However, as near as I can tell, Monsterland does not have any prerequisites so that explanation wouldn't fit here. But I am still very confident this fix will work for you.
https://gtm.you1.cn/sharedfiles/filedetails/?id=2890583186
also tried to update Steamdeck to beta version and installed GE-Proton as Threeson suggested, all came with the same final result
thanks