So, as we all know, it was confirmed that the world size will be quite small to keep a smooth 60 fps on 4 player split screen.
But I was thinking, why not add a split screen option when creating a map? So people who want to play ssp/smp get a much larger map, and for those who want to play split screen, they get the smaller map.
So, as we all know, it was confirmed that the world size will be quite small to keep a smooth 60 fps on 4 player split screen.
But I was thinking, why not add a split screen option when creating a map? So people who want to play ssp/smp get a much larger map, and for those who want to play split screen, they get the smaller map.
So, as we all know, it was confirmed that the world size will be quite small to keep a smooth 60 fps on 4 player split screen.
But I was thinking, why not add a split screen option when creating a map? So people who want to play ssp/smp get a much larger map, and for those who want to play split screen, they get the smaller map.
Thoughts?
I think that will be good, you know its a larger map. How about a bit of a small island?
So, as we all know, it was confirmed that the world size will be quite small to keep a smooth 60 fps on 4 player split screen.
But I was thinking, why not add a split screen option when creating a map? So people who want to play ssp/smp get a much larger map, and for those who want to play split screen, they get the smaller map.
they coudl "simply" build in some sort of map traveling via loading screen. you should always remember, that you are able to create multiple worlds, so i asume it should be possible to travel from one to another (something like, all players on the server have to be near one edge of the map to travel to the next one). the only thing they had to do for this would be to save inventory somewhat gamewide, not mapwide. they are smart enough i guess, so they will figure something out. i won't bother small loading times after 5mins of walk. this would eliminate the performance issues because you don't really make the map bigger =D
Like a real time loading system, I'll explain the basic idea of it. (sort of)
It would save the data depending on the players location, at the position the player is, it finds the nearest 4x4x4 chunks.
(not sure the size of a chunk, but it would be medium, big-ish?)
This would be the "world" the player sees, this would be the main chunk.
Around the main chunk, it would get other chunks(smaller than the main chunk to avoid lag when loading them) and save them.
(= 9 sidechunks... sidechunks = chunks around the main chunk)
if the player leaves the main chunk, the side chunk load, if the player stayed a while from the main chunk, the main chunk would update to the players location. Meaning it doesn't have to keep loading old chunks when the player is in that area.
blocks would only load in the main chunk if the player is in it.
These main chunks and side chunks would be like a chunk with smaller chunks.
the basic load chunk and unload chunk would still be used, this idea might get rid of the performance issues with large worlds.
So think as the main and side chunks as the world.
Either way the world size would increase, but the idea would be to save performance to allow bigger worlds.
Well that sounded complicated ._.
I have no idea if this would work, but I felt like brain storming for solutions! ^-^
they could also have something to help performance like optifine!
But I was thinking, why not add a split screen option when creating a map? So people who want to play ssp/smp get a much larger map, and for those who want to play split screen, they get the smaller map.
Thoughts?
I agree.
I think that will be good, you know its a larger map. How about a bit of a small island?
I swear I didn't see your post, I went through a handful of them but I promise you I didn't see yours.
Edit: also, if you didn't make a thread on it, could you please link me to where you said it?
Try to send it(twitter?)to them
Like a real time loading system, I'll explain the basic idea of it. (sort of)
It would save the data depending on the players location, at the position the player is, it finds the nearest 4x4x4 chunks.
(not sure the size of a chunk, but it would be medium, big-ish?)
This would be the "world" the player sees, this would be the main chunk.
Around the main chunk, it would get other chunks(smaller than the main chunk to avoid lag when loading them) and save them.
(= 9 sidechunks... sidechunks = chunks around the main chunk)
if the player leaves the main chunk, the side chunk load, if the player stayed a while from the main chunk, the main chunk would update to the players location. Meaning it doesn't have to keep loading old chunks when the player is in that area.
blocks would only load in the main chunk if the player is in it.
These main chunks and side chunks would be like a chunk with smaller chunks.
the basic load chunk and unload chunk would still be used, this idea might get rid of the performance issues with large worlds.
So think as the main and side chunks as the world.
Either way the world size would increase, but the idea would be to save performance to allow bigger worlds.
Well that sounded complicated ._.
I have no idea if this would work, but I felt like brain storming for solutions! ^-^
they could also have something to help performance like optifine!