Archive: 13 posts

---

Downloaded & installed update BUT system freezes when trying to load LBP2 deleted updates from game data utility and re-installed 1.06 but it still freezes system Anybody got any suggestions or solutions?

2011-09-07 21:38:00 Author: Unknown User

---

Well, how long is the freeze. After I installed the patch, it took a long time to start up. It was at a black screen for a while, then it went to the video when you start the game. So I think it is just the first startup on 1.06.

2011-09-07 21:48:00 Author: StaticLinuxpro Posts: 482

---

I've now heard several people having a slew of different issues after the new update Be sure to go to getsatisfaction.com (http://getsatisfaction.com/littlebigplanet) and check if your issue has already been raised. If not, you can create a new "problem", and hopefully Mm will respond in not too long...

2011-09-08 09:26:00 Author: Slaeden-Bob Posts: 605

---

Some good points gentlemen...thanks for sharing them.

2011-09-08 12:12:00 Author: RickRock_777 Posts: 1567

---

Anybody got any suggestions or solutions? I posted a possible solution here (https://lbpcentral.lbp-hub.com/index.php?t=62893&p=923765&viewfull=1#post923765).

2011-09-09 04:38:00 Author: Aya042 Posts: 2870

---

I ran into the same problem. I fixed it pretty much like Aya said by deleting my save data and importing a backup. I wish I'd seen his post first 'cuz for some reason it didn't occur to me that I could roll back to 1.05 and create a new profile backup. Fortunately I hadn't done a whole lot of creating since my last backup and almost all of it was just experimenting for kicks and giggles so I didn't lose much. As a side note, all of the hazards that I've been missing are in my popit now-Yay! Aya mentions in his post the possibility that all of the patches may have been rolled into one. Thankfully that's not the case and you can update to 1.05 and then cancel before getting to 1.06 so you should have no problem creating a new profile backup if you don't have a recent one. Just make sure that you're deleting the game data and NOT the profile data if you're trying to get to 1.05 to make a backup. After you're 100% sure you have a backup you can use, then delete your profile data (in the game data section of the ps3, not the save data--the save data will contain your profile backups).

2011-09-09 09:32:00 Author: Sehven Posts: 2188

---

I fixed it pretty much like Aya said by deleting my save data and importing a backup. Well, it was just speculation, but good to know it works. I wish I'd seen his post first 'cuz for some reason it didn't occur to me that I could roll back to 1.05 and create a new profile backup. Also speculative - there's always the risk that upon booting 1.06 for the first time it actually modifies the profile in a non-back-compatible way during loading, in which case rolling back won't help, and you've lost your profile for good, which would be kinda annoying if MM push out a patch shortly. For those who don't want to wait for MM, but don't want to take the risk, it's possible to test on another account by rolling back to 1.05, creating a new profile on a new account, doing the 1.06 upgrade, then cutting the power to the PS3 as soon as you load 1.06 for the first time so it doesn't get a chance to save the profile. Once you roll back to 1.05 again, you can see if it successfully loads that profile or not. Frankly, there's still a minor risk, so I'd still recommend waiting for MM if you're not comfortable with it. Personally, whenever I see the "There's a new patch" message come up, I always cancel, load up the current version, and make a profile backup before quitting and upgrading, because I have little faith in MM releasing comprehensively-tested code. To be clear, that's nothing personal against MM - I work in software engineering, so I'm aware that the realities of business can sometimes preclude such things. As a side note, all of the hazards that I've been missing are in my popit now-Yay! Cool. I wonder if that was a side-effect of the profile import, or just a proper fix in 1.06. Did anyone else with this bug have it fixed upon loading 1.06? Aya mentions in his post the possibility that all of the patches may have been rolled into one. Thankfully that's not the case... Good to know. Cheers.

2011-09-09 17:47:00 Author: Aya042 Posts: 2870

---

Personally, whenever I see the "There's a new patch" message come up, I always cancel, load up the current version, and make a profile backup before quitting and upgrading, because I have little faith in MM releasing comprehensively-tested code. To be clear, that's nothing personal against MM - I work in software engineering, so I'm aware that the realities of business can sometimes preclude such things. Excellent advice. This is the first time I've had a problem like this but I'll make sure it's the last by doing a backup before every update from now on. Cool. I wonder if that was a side-effect of the profile import, or just a proper fix in 1.06. Did anyone else with this bug have it fixed upon loading 1.06? I'm betting it was a side effect of the import. I'm also betting that my profile was screwed up in some way when I imported my lbp1 profile and that's why I was missing the hazards in the first place and also why 1.06 refused to load for some of us (somebody else who had the 1.06 problem mentioned that they had been missing the hazards too). I have nothing to base that assumption on--just a hunch (the game gave me problems when I imported my lbp1 data originally so I guessed that that might have something to do with my missing hazards). Then again, I've imported backups in the past and it's never fixed the hazard problem so maybe it is something new in 1.06. Or it could be because I deleted my save data, went through the intro level, and then imported the backup. In any case, I'm glad that I don't have to use lethalizers or ask friends to light things on fire for me any more.

2011-09-10 21:46:00 Author: Sehven Posts: 2188

---

I'm betting it was a side effect of the import. Hmm. I was leaning more towards the other explanation. I guess we'll have to wait till we hear from others who suffered from the problem. ...somebody else who had the 1.06 problem mentioned that they had been missing the hazards too... Well, IIRC OmegaSlayer had the 'missing hazards' issue, but I don't recall him saying he had any problems with the patch. Or it could be because I deleted my save data, went through the intro level, and then imported the backup. Seems unlikely, but anything's possible with a bug. Shouldn't be too hard to test out. Certainly would be neat if fixing the missing hazards bug was as simple as: backup, reset, then import. Edit: Ah. Just found this post by OmegaSlayer... I must say this patch was sweet for me because I finally got the hazard tools that were all missing (except the gas) in my popit.

2011-09-10 22:14:00 Author: Aya042 Posts: 2870

---

I keep getting the "3 beeps" whenever I exit LBP2.

2011-09-11 12:33:00 Author: Ali_Star Posts: 4085

---

Try rebuilding the database. I do this after any game update, and I have not had any issues. http://www.ps3blog.net/2011/01/28/tips-and-tricks-ps3-rebuild-database-faq-recovery-menu/

2011-09-11 13:04:00 Author: StaticLinuxpro Posts: 482

---

I keep getting the "3 beeps" whenever I exit LBP2. At least I'm not the only one, it was the same with the Uncharted 3 BETA. Hopefully this won't cause people to lose data. *backs up profile*

2011-09-11 13:22:00 Author: keanine Posts: 114

---

Try rebuilding the database. I do this after any game update, and I have not had any issues. http://www.ps3blog.net/2011/01/28/tips-and-tricks-ps3-rebuild-database-faq-recovery-menu/ Is it completely safe? Because this 3 beeps thing is getting worrying.

2011-09-11 22:22:00 Author: Ali_Star Posts: 4085

Posts: 1077139    Threads: 69970    Members: 9661    Archive-Date: 2019-01-19

Aus dem Archiv wurden alle persönlichen Daten wie Name, Anschrift, Email etc. - aber auch sämtliche Inhalte wie z.B. persönliche Nachrichten - entfernt.
Die Nutzung dieser Webseite erfolgt ohne Speicherung personenbezogener Daten. Es werden keinerlei Cookies, Logs, 3rd-Party-Plugins etc. verwendet.