Printable View
You could, but it would be very difficult to manoeuver the capture box around the level if the level is huge. The you'd have to place it in the new level by trial and error, so it doesn't go over the level boundaries.
My level had this bug, so i had to cut it into 4 chunks, then captured them.
I was hit with it three times. It happened way faster than 160 hours too, I had dodgy 0.1's after just a day or so.Quote:
Originally Posted by Sehven
When I first started building it, I was unaware of the causes at that stage so I did rack up quite a few hours unpaused. This led to the usual lack of response at 0.1 then 0.2 right up until 0.5 and then the pistons finally going nuts (at I assume 160 hours) and either not working at all or juddering about all over the shop. This happened twice and it wasn't until I'd finally found that response from MM on the workshop about pausing, that I finally got the motivation to move the level again.
After the move I remained in Pause mode as much as I could, but that proved quite difficult considering the problems I had with pistons/bolts not copying over properly. As I said they'd either vanished completely or the settings that worked perfectly well in the old level had totally borked in the copy, so I had a fair bit of tweaking to do. Having said that, almost all of the tweaking was done in one afternoon and I honestly don't think I had it in Play mode for any longer than an hour. All further building was done paused and I was careful to rewind, but it still gradually set in again and it felt like it was even quicker than the first time, although that may have just been because I was constantly checking.
After the third move I built the rest of the level in workshops. Not noticed it happen any more, but then I've not really been in the level much.
As for MM.. I'm just really disappointed tbh. Their lack of communication on the subject is infuriating, they're just ignoring the problem. If there is literally nothing they can do, then they should at least explain the problem, so I don't have to read endless posts about poor creators losing all their hard work. I wish I'd known about it beforehand.
Anyways, I'm not one to maon, so.... :p
When I first discovered the bug about a year ago, I had found the posts on LBW and added my situation. I had gotten the suggestion to have Mm reset the clock and it seemed there had been a few lucky individuals that had that done by sending an email. I've sent quite a few emails and even completed a bug report in the Beta on the issue, but I have never had a reply.
Seems to me if they do have the ability to do this, then add it as a feature to reset the clock. Heck.. I would even pay for that little option if it came in something like a Creator Pack 2!
This actually made it all a whole lot harder to swallow tbh. Why should whatshisname on LBW get his level fixed and not me? I sent 3 emails and didn't hear anything back. I even begged lol. 8 months work down the pan, I was desperate! :pQuote:
Originally Posted by jwwphotos
Me too Jww! I just don't think they're that bothered though as it's only affecting a handful of creators. It's just a shame that that small minority happen to be the ones putting the most work in. Makes me sad. :(Quote:
Seems to me if they do have the ability to do this, then add it as a feature to reset the clock. Heck.. I would even pay for that little option if it came in something like a Creator Pack 2!
I also emailed them to no avail. I don't expect them to reply personally to each and every one, but surely they know a lot of creators have had a crappy time because of this thing. If it wasn't for the unofficial information i found through this forum I would have given up the game entirely at that point. My guess is either it's unpatchable, or it affects too small a percentage of the general LBP community for them to consider worth patching.
Interesting.Quote:
Originally Posted by Kiminski
As far as I'm aware, no-one's actually done any controlled experiments on exactly how much unpaused time is required to trigger the initial symptoms (i.e. 0.1s pistons failing). So far, the "160-hour bug" moniker is based solely on this quote from MM...
...and, as a consequence, it's believed that 160 hours is the magic number, which is about a week.Quote:
Originally Posted by Anton from Media Molecule
However, if you read the quote carefully, it's ambiguous as to whether this is the actual amount of time it takes for the bug to occur, or whether it's just the amount of time which happened to be on the simulation clock of the level that was sent to MM for analysis.
Therefore, it's possible that the bug will actually start occuring after just a few hours of cumulative unpaused time.
Perhaps you made a mistake during the rewinds? Not every action in create mode generates a rewindable event, which is why the "placing a block of DM before unpausing" technique seems pretty effective for all those who use it.Quote:
Originally Posted by Kiminski
The only reason I question, is due to this other quote from MM...
...and seeing this guy is one of the lead developers for the game, I have no good reason to doubt his assertion that leaving the simulation paused is an effective means of circumventing this issue.Quote:
Originally Posted by Anton from Media Molecule
Yeah.. I have no idea. Maybe their fix is a bit harder than reaching in with a utility and flipping a value. The number of requests made it too difficult to respond? Who knows..Quote:
Originally Posted by Kiminski
Sad really. Makes me wonder why there isn't a huge warning sign on the box or in one of the tutorials.
Quote:
Originally Posted by jwwphotos
Quote:
Originally Posted by Kiminski
A bit of research yields this thread on LBW which used to be stickied. However, the fact that it no longer is, might suggest that it's no longer valid. Furthermore, if you read that thread, it says...Quote:
Originally Posted by julesyjules
...so I guess the guy who got his 160-hour bug fixed was just lucky.Quote:
Originally Posted by Sam_Protagonist on LittleBigWorkshop
For those who attempted to contact MM to get their levels fixed, did you follow the instructions on that thread precisely?
Quote:
Originally Posted by julesyjules
If you read the original thread, it sounds as if resetting the clock is fairly trivial for them, although Anton suggested that doing so may cause other problems with the level. However, with maybe 100,000 customers and only 20 staff at MM... well... you do the math. ;)Quote:
Originally Posted by jwwphotos
As for a long-term fix, if such a fix would require changing all the data types which store simulation time variables, then not only would a patch have to make the appropriate changes to every level on your moon, it would also have to patch any exported level files in the save data area, and all 2 million+ published community levels.
There's probably an easier way to fix this, but, frankly, there are far more serious bugs with LBP than this one, some of which can seriously corrupt your profile and/or make you lose one or all of your levels for good (check out this for example). At least with this one, it's possible to fix the problem yourself, and has probably been categorized as a 'low-priority' issue in whatever bug-tracking system they use.
I really hope that's not the case. If it just meant capturing the whole level and plonking it into a new space I couldn't agree more, but we're talking about levels that have taken sometimes months and months to build and contain a lot of information. My level was far too big to move in one piece, I had to literally delete whole sections to try separate it all, the whole move took me days and days. I'd much rather have lost a few hours work because I'd forgotten to backup.Quote:
Originally Posted by Aya042
Profile bugs have been pretty much sorted with the introduction of backups anyway. While I feel very sorry for anyone who suffers a corrupt level/profile, any digital data is prone to corruption and it's our responsibility to take precautions.
Well, obviously not working for MM, I can't be sure (I only live about 10 minutes from their office - maybe I should pop in and ask them? ;)).Quote:
Originally Posted by Kiminski
I merely base it on my experiences in software engineering, and what Anton said about looking into fixing it. Now since he said that, what, a year ago, and nothing's yet been done, I can only assume that it's either been marked as low-priority, or it's just too much of a pain to fix, and has been marked as WONTFIX (or whatever the non-bugzilla equivalent they're using is).
Either way, I doubt we'll see a long-term fix for this at any time in the future, although I hope I'm wrong about this. If the alleged integration of the PS Move into LBP requires any substantial core changes to the game engine and level format, then they might take the opportunity to fix this at the same time, but this is just speculation.
Don't let my somewhat unemotional writing style fool you into thinking that I don't sympathize for you, because I do. It's just that sympathy, unfortunately, isn't really going to help you out very much with this.Quote:
Originally Posted by Kiminski
All I can say is that I have done the whole level-moving thing in the past for someone else, for an incredibly substantial level which they'd spent about a year working on. In this case, I successfully managed to capture the entire level as a single entity, and transfer it to a new crater. The only things that needed fixing afterwards were about six or seven pistons which were attached directly to the floor. The whole thing was fully operational again in about an hour.
If you still have a level with this problem, or get one in the future, I don't mind having a go at trying to fix it on your behalf, since, frankly, your levels are awesome enough to make it worth my while. :)
Indeed. But my point was that, for those ignorant enough not to realise this, it's possible to lose a huge amount of work, with no chance of recovery. At least those people who are unaware of the 160-hour bug have the option of transferring their level to a new crater, and, even though it's a complete pain, it's arguably better than having to start from scratch.Quote:
Originally Posted by Kiminski
Lol thanks very much, I'll bear that in mind. ;)Quote:
Originally Posted by Aya042
Unfortunately it just wasn't possible with my last one, I kept getting the red exclamation mark every time I attempted to place it whole, so that was a definite no go.
Gawd.. it's all coming back to me now lol.
Finally managed it in parts, but lost a lot of decorations that had been stuck to invisible materials and contraptions and despite having nothing attached to the floor at all, I still lost almost all of my connectors, or at least had the settings go nuts and break the objects they were attached to.
That said, maybe a fix for this problem doesn't need to deal with the actual bug at all, but merely offer us an easier way to copy our levels over to a new space...
The fully recovered level is now complete and published (Level Showcase link: Sack Scout Camp). Thanks for the help, everyone, in solving this problem.Quote:
Originally Posted by comphermc
-- Nanluin
Looks like I never knew what the 160 hour bug was... seems I,ve been working around it forever... currently the best I can manage on a piston is .05!!!! In the words of LOST's James Ford, "Son-of-a-B...."
Pretty simple to recover. If you need a spotter to help capture and move the whole thing over lemme know. I should be on this evening.
Wow, this bug is still a problem as of today! I know this is an old thread but I absolutely had to post my thanks to all of you. I had NO idea what's been going wrong with my level. I had .01 pistons not working and a very important set of emitters just wouldn't work all of a sudden. That level would be out by now if it weren't for this glitch :P Anyway thanks to all who commented here, this will help me figure out how to solve my problem, whereas I had no clue at all what to do before! :)
that's definitely the way to go. avoids other problems aswell. such as breaking other objects in your level.Quote:
Originally Posted by jwwphotos
that said, my level has the bug :P was inevitable as i've been constructing this star destroyer for well over a year. the level has been rebuilt several times.
fortunately it only effected two pistons (all other pistons are set on 'direction'). one piston had to be replaced with a Wobble bolt. the other (moving a bounce pad) still launches sack persons the correct distance., but studders a little in the process.
the level is a huge, & intricate monstrocity. moving it piece by piece to a fresh level would take me weeks. too many pieces are attached together. plus i can't remember where all the wires go :P
wish i joined LBPC earlier, so i could have learnt about such bugs before it was too late.
This bug freakin' sucks! Agghh!!! I think I have it again. It always happens in the end process of my level making. i kept the level in pause and rewinded after any events after something moved. This is the 3rd freakin time....but its wierd this time around. I have a .1 piston working from some emmiter logic that activates the piston to work but I try putting a new piston in at .1 and it wont work but the other does. And from my experiences, usually it'll gradually go up from .1 to .2 and so on but this time it went straight to .3. Any piston .3 or below wont move and this happened suddenly. Its really going to be frustrating to move this thing because it uses a heavy amount of decorations. This is because when you place an item with decorations on it some of them disappear for odd reasons. I might just work through it :(.
Just got this *&@$**## bug. I ONLY work in PAUSE mode, playing to test and then rewinding. What's more I have already thermo-hacked my level so it's going to be a REAL pain to fix this one.
WHY does it do this when I edit in pause mode????
Edit: Actually wasn't that bad - most of my level is simply dark matter boxes with emitters on so it worked straight away.
You know what what happened to me the other day, I was hit with the unglue bug, but it only hit one iddy bitty section of my level,now these bugs are starting to be picky about what how they want to ruin our prescious created levels!
Well I kept wondering why my waterfalls got worse and worse, then I finally lucked out on this post, because I thought it was somethign else. I only work in pause because all my levels have starting events that I can't let play otherwise it willdestroy the logic. I am at .5, my level is bigger than the level size (I have a gas cloud that goes wuite a distance out of the level. This makes it impossible to capture...or rather paste back in. I had to share tons of logic to finish this level, so rewiring will be next to impossible with devices taking all three layers sharing one mag switch because I ran out of thermo for switches wayyy back. The level works, but not as well as I would want it with some of the effects being stuck at .5. I only realized this was the issue when my other level had the pistons all stop from .4 and the mag switches and the other items unglue from the gas and repaste on the other material ??
Kills me every time I read these posts. :(
Anyway, thought I'd better mention that 0.5 seemed to be the last step before my level was broken beyond repair (Big fat juddery mess!), so I wouldn't hang about in create mode for too long if you can help it.
Yup.. me too.Quote:
Originally Posted by Kiminski
Lol, wonderful. I think I will make a few more copies and try my best to capture them. What happened after the .5 stopped working? I captured both levels, but with them taking up the entire space, and both having a little fog that gos off the level bounds completely I am not able to paste them in. I have to go and find all items that have nudged to the out of bounds and move the fog back in (one goes about 1/3 a level off the level), and I am sure that will take me time. I emailed MM, but not sure how much they will care about a LBP 1 level. I wonder if importing levels to LBP 2 will help?
Can you possibly make a copy of the level and then delete the fog? Then try to capture? It might be handier.. Also with someone spotting for you, it might be much easier.
The timeline of the level is simply that. Regardless if LBP1 or 2. It is the precision of math calculations based upon a very large number (the current time in the timeline of the level) causing the issue. Publishing in LBP2 will not reset the timeline. The only way to do that is capture your level, even if in sections, and paste them in a brand new untouched level.
Thanks for the warning, I almost published them LBP2. I am off to try for a twentieth time to capture the level. I pulled teh fog and all other items out of the out of bounds area, but it still is not capturing random parts.
In your other thread I posted a suggestion... hope it helps. :)Quote:
Originally Posted by celsus
It's hard to explain, but basically every moving part in my level either stopped working altogether or would only move in a blurred pulsing judder. - So when extending a piston from say 0 to 100 it would perhaps take 100 tiny bursts of movement to get there. Horrible!Quote:
Originally Posted by celsus
I really can't believe this is still an issue in LBP2, it's crazy! I get that the problem may be unavoidable, but would it have been that difficult to provide us with an easier way to reset the timer? It's totally devastating to see months and months of work get destroyed like this. :(
I have to agree, I sent an email to MM, but not reply yet. I have just tried deleting the fog and clipping all the edges in, but now when I paste it in the new level it causes the PS3 to freeze. Three times in a row now, with three differemt captures and once using a second controller and blank profile for the capture.
I had an issue with decorations disappearing that I'd had stuck to invisible Dark Matter, but got round it by emitting the level instead. Obviously a different problem to what you've been getting, but could be more stable option perhaps?Quote:
Originally Posted by celsus
With regards to LBP2, I'd definitely publish a copy to try it out. The higher zoom levels alone will make it easier to paste the level.
Lol, I just tried copying the level and pasting it LBP 2 and it froze the PS 3 there too, then on reboot the system sent a error report to Sony. I have to remake it for LBP2 anyways because it is emitting half of an object for some unknown reason, and that makes the level impossible to defeat. Plus the camera thermo and logic will allow me to make the entire ship. I just hope the emitter is not a sign of the 160 doing it's coup de grace.
I have a bug in LittleBigPlanet 2 where the physics at the right of a level is acting oddly, like objects going inside other objects, and floating in the air then going back to its place, is that the 160 hour bug? Or is it a new bug? New error of the 160 hour bug?
Sounds like a different bug - there's plenty to choose from in LBP2. ;)Quote:
Originally Posted by EleoMod