Minecraft Forums

Just wanted to find out why there is such a massive frame rate drop once pistons and glowstone are involved.

I have seen a few topics already about people making a light house using a mine cart method and their frame rate drops.

So I went a head and build this compact version of a lighthouse found here
on my xbox server. I tested without glowstone in place and it ran smooth and no frame rate drop that was noticeable. But as soon as I added glowstone frame rate dropped really bad. I went ahead and build a copy on my mac version of minecraft and it didn't affect the game at all, lighthouse rotated smoothly.

So is there any reason why the new slim xbox can't handle a few (48 in this case) pistons and some glowstone? I've been waiting for the pistons just like everyone else, but my excitement was quickly gone once I found out they are almost unusable. I hope there is something that could be done from the software point of view and 4J will rush with an update to fix the issue.

Please comment with your opinions.

Yeah, try slowing the cycle. See if you can't add delay to it so that the light can update slower. You eat a ton of processing having to update that many blocks, redstone, and light levels at once. You shouldn't need to slow it very much at all really, even the slightest change can make a world of difference.

The only trouble is, with those lighthouses that run off of a cart and detector rails, most of the timings are very specific. I suppose you could make the rail longer, or with less powered rails, to force the cart to move longer between triggers. If I remember the schematic right, you MIGHT have enough room to add a single block hill between each detector to slow it down some.

I think everyone needs to remember that pistons probably haven't been fully optimized for the Xbox 360 yet and that pistons can even make a good PC lag from time to time.

yep, plus everyone's piston crazy... 200-300 pistons firing off... My computer is sighing in relief I'm a console gamer.

Light plus cycled pistons. Ack. Glad I didn't prep a light house.

Growing pains and learning curve. Just gotta find the right balance.

Instead of running multiple pistons clocks throughout the map, I suggest using just one every 6 chunks or so.Run redstone lines to a couple of different contraptions. Like a mini generators. Figure out what the box and internet can handle. And make switches to turn them off when not in use

I'm a piston fiend so the next suggestion is hypocritical. Use less, and sparingly. We've been watching utube video what seems like forever. Remember, all these video are in create mode, run on a pc, don't have epic piston builds every five blocks apart, and be practical.
Sure, you can harvest sugercane with a ridiculous amount of pistons, or you can make 10 good piston doors/traps.

I want to see improvements just the same as anyone, but there has to be a limit somewhere. Just gotta find your happy medium.

Quote from Gishgeron

The only trouble is, with those lighthouses that run off of a cart and detector rails, most of the timings are very specific. I suppose you could make the rail longer, or with less powered rails, to force the cart to move longer between triggers. If I remember the schematic right, you MIGHT have enough room to add a single block hill between each detector to slow it down some.

You must of not read my post or something. I said I build a lighthouse that does not employ the rail cart system in it. Just 48 sticky pistons, redstone, torches and repeaters.

I know that build. It's not a lot of crazy motion, and no rail cart. Saddens me that it's an issue. Maybe someone needs to shrink it down. come up with an xbox equivalent. Maybe only one layer of pistons instead of two. Thin it out.

Quote from AtomicSphincter

You must of not read my post or something. I said I build a lighthouse that does not employ the rail cart system in it. Just 48 sticky pistons, redstone, torches and repeaters.

I apologize, I read it backwards. I honestly thought you said you used that build.