1. #11

    Re: Editor Boundaries?

    Originally Posted by sipe
    X axis 128
    Y axis 32
    Z axis 16

    128 * 32 * 16 = 65536
    Efficient, I like.
    Share this post

  2. #12

    Re: Editor Boundaries?

    Originally Posted by Jorma
    There has to be some some limits because of various constraints and those just happen to be practical and nice round numbers
    I just thought this was funny cause it's a common number for 16 bit processing and it's also the number of cell rows you can have in an excel spreadsheet.
    Share this post

  3. #13

    Re: Editor Boundaries?

    Originally Posted by nannerdw
    There's no point in trying to delete all of the blocks. It will just slow down your track and increase the load time.

    Originally Posted by Jonofthejungle
    I have come to the end before. the blocks start to get half size, and then they just don't delete.
    The end blocks are half size?
    I'm not sure about the Y-axis blocks but I've hit the far right end of the blocks more than once and they're normal sized. I'm also wondering why he referred to them as half-sized, they seem pretty normal to me :/
    Share this post