Maximum region info for Terrain ReadVoxels and WriteVoxels

Bug Reports Documentation Issues
#1

https://www.robloxdev.com/api-reference/function/Terrain/ReadVoxels
https://www.robloxdev.com/api-reference/function/Terrain/WriteVoxels

Neither mentions anything about this or what it’s max volume/extents is
image

5 Likes
#2

Out of curiosity, what size did you use that caused this error?

#3

I think it is around the same as parts (2048, 2048, 2048).

1 Like
Region is too large
#4

Nope, it’s volume based, so you can increase one axis if you decrease another

#5

Oh yeah, forgot about that. I had to reduce the volume for Free Build to achieve a 16k×240studs×9k terrain size. Also, I wouldn’t recommend making a terrain that big without a great excuse as the load times are… You can guess…

#6

It’s ok we’ve got custom streaming and some amazing optimization :wink:

#7

Guess you should be fine then, I had StreamingEnabled off lol. Load time were 5 - 10mins on a good day (Assuming no-one was already in a server otherwise it was like 20 seconds).

#8

Hello anyone at roblox care to look into this or do I have to make my own wiki with data I approximate by brute forcing numbers

Edit: After brute forcing for a little bit the limit looks to be around 268,000,000 studs by volume
Here’s my data for volume of different sized regions

Summary 
Didn't work:
268646400
268569600
270418176
269058048
_________
Did work:
267632640
267571200
265431040
263782400
2 Likes
#9

Thanks for the report.

This is an issue we are aware of and will be looking into.