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
So sorry you're having trouble. Another person had a similar problem yesterday, but for them it got stuck consistently at 65% instead of 94%.
It's almost certainly due to file corruption. We saw this problem once a few months ago and it turned out that there was a file that got partially downloaded and the game would just get stuck whenever it hit that file.
We're looking to implement some kind of solution to fix this automatically, but it's not so easy! Sometimes we can't even tell that a file is corrupt until the game crashes.
Can you paste the launcherLog.txt file from your Prismata install directory?
The best thing to do is delete the entire game, including the whole “Prismata” install directory, and reinstall (either via Steam or via the Windows/Mac versions). You can also try the web version at http://play.prismata.net to see if it works. Adobe AIR uses the default cache for downloaded files, which is the *internet explorer* cache on Windows, so you could try clearing that (but this should never be necessary).
Launcher logging started
Launcher - Steam
Game run - start
Game run - complete
Launcher - hideUpdater
We just deployed an update that adds more information to this log. Can you try again?
It seems did not worked me.I am still strucked at the 95%.And i redownloaed 3 times today.
And the log is still the same.
EDIT:It worked after restart the launcher about 5 times.I am not sure the stability.If someone still strucked try again and maybe worked
Anyway it works.Thanks.
Hmm, OK, thanks for the update!
Game works fine in Chrome.
What's your Prismata username? We'll take a look. We're actually planning a couple more small tweaks to help it retry in certain failure cases.
Took a look at our error logs. It appears that your client is trying to download some small data files and failing. It will retry up to 20 times in a row and then give up. The files are:
https://s3.amazonaws.com/lunarch_assets/user/asset_info.jso?nocache=1522783483551
https://s3.amazonaws.com/lunarch_assets/soundtest/soundtest.jso?nocache=1522784159162
These files are really tiny and are stored on the amazon content delivery network, so they should be easily accessible from anywhere in the world. Is there any chance that a firewall or some other anti-malware software on your computer is preventing Prismata from accessing these files? I assume you can download them just fine in a web browser, right?
The reason they're loaded every time is that they allow us to make on-the-fly changes to sound and to custom player avatars without forcing all of our users to update, but I think you're the first case where somebody just couldn't download the files. Maybe we should have a backup in that case? Though if you can't download files, you might have a hard time with a lot of the game's online functionality.
Not sure what else to suggest. Are you doing anything unusual with your internet (running a proxy, etc.?)
No clue, honestly. Thanks for your effort, I'll see if I can fiddle with some settings.
It worked fine now, perhaps it'll go away. Though like I said, I did manage to log in normally a few times before. Strange.
We looked a bit further. Seems that Amazon s3 threw a 503 error, which is this: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-503-service-unavailable.html
So maybe Amazon actually had some temporary downtime? S3 is supposed to be super reliable though, and there's no way we're hitting request rate limits.
Given that we've never seen this particular bug before, and it only ever happened to you on one occasion, I'm included to think it was a one-time rare thing that we probably shouldn't worry about. But please let us know if it happens again.
Edit: Nevermind, seems you're also having trouble in the browser too? That's so weird. WTF...