-
Notifications
You must be signed in to change notification settings - Fork 55
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
Lumines Electronic Symphony [PCSE00009] #693
Comments
Goes further after latest update, but appears to spam errors a lot. |
Can you please fix it? I was playing this game recently and I have the same error |
Upon updating to version 0.2.0 3563-b5aa1ec5, the game suddenly went past the title screen and made it to the main menu. However, it crashed again after trying to start Voyage mode. I tried booting it up again a few times, but it just went back to crashing at the title screen. |
As of Vita3K/Vita3K@dbe6951, the game once again goes in-game on the first launch after updating. This time, I was actually able to reach gameplay.
Here are my specs:
Test Environment Summary:
Unfortunately, I do not have a log because I forgot to save it before trying to relaunch the game. |
Unsure of how you guys are getting this far into it. Latest build gives me the endless loading circle as seen in |
For crying out loud, why this game wasn't fixed yet?! |
Same case for the PAL 1.02 release FYI. |
From my experience, I could only "launch Lumines Electronic Symphony and start the voyage mode" on a fresh installation of Vita3K & first-time boot of Lumines Electronic Symphony. After that, all following boots crashed. I'm not sure why. Maybe people can try and share theories. |
Was randomly able to once again get in-game on the first boot on today's update, Vita3K/Vita3K@1c315b1. If the log didn't capture it, it appeared that the game showed a single memory error at where the game normally crashes and then just continued to the menu as if nothing happened. Same settings and environment as with my last post. EDIT: Got it working again on Vita3K/Vita3K@206f152 |
Got in-game once again on Vita3K/Vita3K@9143a14 Some Observations: Wasn't able to save the log this time, sorry. EDIT: Why were the labels changed? Getting Ingame is wildly inconsistent and I still have no idea what causes it to work. Plus, even when it does go ingame, the game crashes on the 4th stage (of 33). |
App summary
Vita3K summary
Test environment summary
Issue:
Screenshots:
Log
vita3k.log
Recommended labels
The text was updated successfully, but these errors were encountered: