How well are Huge Terrains Handled?

I’m creating a game that occupies an area of about 120,591,900 studs sqaure. A server with only the terrain in it takes up to an average 6 seconds to load on decent devices and an average of 10 seconds on lower end devices (joining a newly created server). I’m worried that once I transfer all the structures, scripts etc. into the game, a majority of devices won’t even get past the Roblox loading screen.

I’m aware of the new terrain handling update, but it recently got disabled due to a bug. Although this is not a major concern because the update will be renabled once again in a few days from now, how well will devices hold up when huge terrain is stored on its memory?

The terrain is about 600mb on the client and server yikes

4 Likes

I’ve created terrain far larger than this before (32k x 600x 16k) that has lots of scripts running. There was no issues for me and it ran at a solid 60FPS. I have since made the map smaller but here is the game:

It also has StreamEnabled off.
You should have no issues with this terrain size but if you want it to run on every device, StreamingEnabled and making it smaller may be an idea.

3 Likes

The load time with structures and scripts in the game shouldn’t change drastically unless you have a ton of custom individual meshes. ROBLOX parts are optimized for ROBLOX and if you use ROBLOX textures a lot and ROBLOX parts the game shouldn’t get effected that much. The things that really make a game take a long time to load are a lot of different custom meshes.

2 Likes