# Texture Atlas Seam Problem

**URL:** <https://community.cesium.com/t/texture-atlas-seam-problem/45515>\
**Category:** Cesium ion\
**Created:** [March 13, 2026, 8:32pm UTC](https://community.cesium.com/t/texture-atlas-seam-problem/45515 "2026-03-13T20:32:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Smithereens](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/smithereens/32/33320_2.png) [@Smithereens](https://community.cesium.com/u/Smithereens)\
**Post date:** [March 13, 2026, 8:32pm UTC](https://community.cesium.com/t/texture-atlas-seam-problem/45515/1 "2026-03-13T20:32:44Z")

</div>

Hello there,

Currently running into an issue with a texture atlas that is generated in Cesium ion and is used in Cesium for Unity. The end goal is to get a .glb file into Unity and have it usable offline via local URL source for the tileset.

In My Assets on Cesium ion, the data and .glb file are added. In the “What kind of data is this?” drop-down, it’s set to “3D Capture/Reality/Model/Photogrammetry".” In the 3D Capture Options, tried a few different options with/without compression and different types, no luck.

The texture atlas seems to be made on Cesium ion, and has some funky artifacts and an irregular resolution size of 1065 x 1043. They are very noticeable on the texture object in engine, and fairly noticeable in Cesium ion when zoomed out in the preview. When zoomed in both in Cesium ion and Unity, the seams are barely noticeable, but there are some artifacts present.

I believe the issue is coming in from how the texture atlas is made in Cesium ion, since the seams are visible prior to importing it to Unity using the URL .json source for the tileset.

Several questions:  
1.) Is it possible to set the resolution of the ion-generated texture atlas to a power of 2 (like 1024x1024) to be more friendly with Unity?  
2.) Is there a way to adjust padding or atlas tile offset to prevent seams?  
3.) Slightly related to the other questions: If there are two separate tileset.json’s, what would be the best way to merge those .jsons into one?

 ![tileset_unity_2](https://global.discourse-cdn.com/cesium/original/3X/5/b/5beb66469151b54b61d306da659e227ad72f1f6a.jpeg)

Thank you!

---

<div class="post-metadata">

**Author:** ![Marco13](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/marco13/32/2757_2.png) [@Marco13](https://community.cesium.com/u/Marco13)\
**Post date:** [March 14, 2026, 8:22pm UTC](https://community.cesium.com/t/texture-atlas-seam-problem/45515/2 "2026-03-14T20:22:26Z")

</div>

> [@Smithereens](#):
>
> Slightly related to the other questions: If there are two separate tileset.json’s, what would be the best way to merge those .jsons into one?

There are functions in the ‘3d-tiles-tools’ that could help here:

- The [`merge`](https://github.com/CesiumGS/3d-tiles-tools?tab=readme-ov-file#merge) command can take your input tilesets, and create one tileset that refers to the inputs as _external_ tilesets
- The [`combine`](https://github.com/CesiumGS/3d-tiles-tools?tab=readme-ov-file#combine) command can take such a tileset, and convert it into one that consists only of one, large tileset JSON file

(For the other points, someone from the ion/tilers team will have to chime in)

---

<div class="post-metadata">

**Author:** ![mdc9001](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/mdc9001/32/15919_2.png) [@mdc9001](https://community.cesium.com/u/mdc9001)\
**Post date:** [March 16, 2026, 3:15pm UTC](https://community.cesium.com/t/texture-atlas-seam-problem/45515/3 "2026-03-16T15:15:11Z")

</div>

So if I understand your workflow is as follows, is that right?

1. Upload a GLB file to Cesium ion to tile as _3D Capture/Reality/Model/Photogrammetry_.
2. Toggling the _Make available for download_ option on the asset details panel.
3. Using the download zip file locally for streaming in Unity

Another option could be to use the [Clips feature](https://ion.cesium.com/clips) in Cesium ion to get a downloadable 3D Tileset. That would go through a different tiler that may produce different results.

I’ve also reached out to our colleages who have more experience with the _3D Capture/Reality/Model/Photogrammetry_ tiler to see if they can provide any additional information about the textures.

---

<div class="post-metadata">

**Author:** ![jaadelgren](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/jaadelgren/32/12981_2.png) [@jaadelgren](https://community.cesium.com/u/jaadelgren)\
**Post date:** [March 16, 2026, 7:14pm UTC](https://community.cesium.com/t/texture-atlas-seam-problem/45515/5 "2026-03-16T19:14:45Z")

</div>

Hi @Smithereens,

Are you able to share the asset ID for this dataset (this will be listed under the **ID** column in “My Assets” in Cesium ion)? If so, I can take a closer look and help troubleshoot.

As for your first two questions, it’s not currently possible to set texture resolution or to adjust padding, but I’ll bring these up internally in our next planning meeting.

Cheers,  
Jake Adelgren
