Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2449564308
Sorry to hear you're having this issue - it's odd this issue cropped up since the game hasn't been updated in a while - but I'll try to see if I can reproduce it once I get a chance.
One more question: do you know roughly when the last time was when you played where you didn't have the issue?
If it's at all possible, could you record your screen as you launch the game and experience this issue? It might help me identify what is going wrong.
I'm not experienced recording game video but I was able to capture launching it from Steam VR using OBS.
here's a link to the short video capture:
https://youtu.be/mRicVvL5iLU
Also as far as when this started occurring... I can say I first started playing Jan 28 2021 and it was working fine. I think this issue started 2 or 3 weeks later... so mid February? That's my best guess, but I don't recall a specific update.. :-(
That's pretty odd about when it occurred though, since the last update to the Steam version of the game was on December 14th of last year.
Thank you for sharing that video, that actually helps a lot! The menu getting stuck on the floor like that is likely on account of some sort of breaking error happening during start-up. Is there any chance you could share the most recent logfiles with me? These are likely located here:
I might be able to see if some error is occurring in there. Easiest way to share this might be pastebin.
Thanks again for the help in tracking this bug down!
Anyway, all just speculation for now - hopefully the logs reveal more :)
Here, I grabbed the output_log.txt file from my appdata path that you specified--here's a pastebin paste (I set to expire 2wks from now):
https://pastebin.com/ysKdQB7F
I have Windows 10--and keyboard settings for that are set to 'English (United States)', which is what I would expect. I don't think that has changed at all on my machine.
*edit* My Steam application language setting is also 'English'. I haven't changed that at all afaik.
One thing you could try is to remove them from you disk to see if that fixes things (steam cloud saves should restore your progress).
Could you try the following when you have a moment?
1. Go to
If you have a 1_steam_full.save or 2_steam_full.save move these as well.
2. Launch the game again
Let me know if this resolves the issue. Normally, steam cloud saves should hopefully restore your progress.
If this doesn't work, could you please send me your save file via pastebin as well? Then I can see if I can reproduce the issue on my computer with it.
The good news is, if your save file was indeed corrupted this update will let you know once the game starts, and start on a new save file instead of blocking the game.
The bad news is that I won't be able to recuperate your save since it was corrupted :/
'0_steam_playerVariables.save'
When I removed this file ^ ^ ^ and re-open the game, I get the "press both triggers to start" prompt and I can play normally!!!
Anyway I'm playing Cubism again, woo-hoo!
And clever thinking in removing the player variables file - that must have been the one that somehow got corrupted. Currently, the only thing that files stores is whether you played the puzzle song (the play button next to the levels) or not - so luckily this wasn't storing anything important. I'll take note to make sure the game handle's the possibility of that file being corrupted more gracefully in the next patch!
Thanks again for all your help in finding the cause of this issue!