Archive: 10 posts

---

Hi, I'm near finishing creating my level, and things have gone wrong. For some reason now, I can't make any more pistons function at 0.1 speed. Even when they are activated by a switch or on there own, they just stay still. And the first 0.1 speed piston I put in my level has stopped to. And really need it to work. Please can someone help me. Thanks.

2010-10-16 11:38:00 Author: Screeno Posts: 153

---

160 hour bug... You'll need to capture the entire level and place it into another crater.

2010-10-16 11:47:00 Author: gdn001 Posts: 5891

---

Nooooooooooooooooooooooo! But... But.. Why? I read up about the aforementioned glitch, and wonder, is it worth emailing Mm my level so they can reset the level's clock?

2010-10-16 12:04:00 Author: Screeno Posts: 153

---

I'm not sure if that's possible. Also, triple posting like that is considered against the rules; next time, just put all the information in one post, and if you want to add anything, use the edit button. But sadly, the only method of fixing it is to capture the whole level (as an object) and move it to another spot on the moon.

2010-10-16 12:40:00 Author: Stoicrow Posts: 276

---

Mine did this recently, I captured it in chunks and moved them to a blank level. Did the trick.

2010-10-16 12:46:00 Author: Radishlord Posts: 706

---

The thing is it's really hard to do in chunks. Lol so many probs!

2010-10-16 13:16:00 Author: Screeno Posts: 153

---

I know, what you can do is copy the level (from the pod) so you can take it apart and not save changes. Hope you understand that

2010-10-16 14:44:00 Author: Radishlord Posts: 706

---

Copied whole level at once and recovered all of it. Problem sorted! Thanks for those who offered their help!

2010-10-17 08:08:00 Author: Screeno Posts: 153

---

Is the 160 hour bug happening after you've been in create mode for 160 hours? Beacause my level does the same thing, and I've been creating in it for about 48 hours? Someone needs to really get a better name because mine didn't stick with the program and happend after 160 hours

2010-10-18 15:46:00 Author: damaz10 Posts: 771

---

Is the 160 hour bug happening after you've been in create mode for 160 hours? Yes and no. The moniker comes from an email sent by a MM employee to a user who was suffering from the bug, and refers to the amount of time on the simulation clock in that specific case. As far as I know, no-one's had the patience to work out what the minimum required simulation time is to trigger the bug, so it could be as little as 1 hour.

2010-10-18 23:54:00 Author: Aya042 Posts: 2870

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.