[Full Launch] Publish Games with Custom Terrain Materials and Performance Improvements

Hi, just an update on this, I am working on a PR in the rbx-dom repo that should fix this issue for rojo and lune. The issue is that the new property we introduced was not supported in rbx-dom. Add support for AssetContentMap by ADJ-acent · Pull Request #672 · rojo-rbx/rbx-dom · GitHub

2 Likes

A couple topics here:

  1. Terrain is ejected separately as an asset, it is no longer part of the 100 mb placefile limit, it has its own limit of 200 MB (although the new format is around twice as large as before). So you should be able to publish larger terrain than before if you have elements other than terrain in your placefile.
  2. Team Create performance is something that we are looking at. Currently without Team Create, terrain performance should be better for most cases (there is an issue we are trying to address which bottlenecks CPU time).
  3. 64k terrain is still in the works, we will have more details in the future.
2 Likes

Hey there, we will look into this issue. Thanks for the report. As for the pathfinding issue, are you still seeing that? If so, could you send us a repro place?

May I get an update on my bug? Did the same bug also occur on the place file I provided?

Hi, we are still working on a fix for this issue. Will let you know when the fix has been deployed. This is caused by an issue with grass rendering when the grass is at chunk border and there is only air on top of the chunk.

2 Likes

So far not seeing any issues, I’ll let you know if any arise, thank you!

2 Likes

There appears to be a bug with regards to when you raycast down onto a new terrain material it always detects it as grass.

For example:
I create a new sand terrain called ‘SandTest’, and I set the base material to sand, and with no material variant. If I then paint this onto my terrain, and I raycast onto the material to detect the material it will detect it as grass instead of sand.
TEST Baseplate.rbxl (91.6 KB)


image

Hi there, this is an issue we are looking at, we will need to go through an API change for this fix, so it might take a while.

1 Like

Hi there, been working on a personal project called Atlas ever since I first opened Roblox Studio.

As a map builder ( not a scripter ), my goal has always been to create an experience featuring multiple planets, each with its own landscapes and biomes.

Due to the limitations of Roblox’s native Terrain system, I’ve relied on a custom client-side system, developed with the help of friends, to dynamically change terrain textures, colors, and other environmental properties at runtime.

With Expanded Terrain , I’ve finally been able to move much of this material management into the native system, hoping to reduce the frame-time spikes that can occur on this side, during transitions between planets.

However, I’ve already reached material slot 49 out of the 62 editable slots , with several environments still under development.

While this update is a welcome improvement, I believe 62 material slots remain far too restrictive for large-scale, multi-world experiences .

Increasing this limit significantly, perhaps up to 100 or 150 or why not 255 slots, would give creators much more freedom without forcing them to rely on runtime workarounds.

I understand that there may be technical constraints behind this limitation, but I wanted to share my experience while this feature is still relatively new.

2 Likes