#1476

Abrupt satellite colour seams when far tiles switch from BNGS2 to USGS

OpenMihneaTeodorStoicaopened 2d ago

Reproduction

BeamNG.Earth 1.10.1 beta, Linux/Vulkan. Load the Mojave near 34.452337 N, 115.931238 W, with nearVisual=detail, S2 colour matching and full de-shadowing. Look down from about 10,140 m while the distant tiles refine. Rectangular grey/rose colour steps remain with clouds off and with the near TerrainBlock hidden in raw view.

Evidence

Co-registered cached imagery against the actual rendered DDSs. A level-3 Mercator tile at 128 px requests imagery z13 and uses BNGS2, while the same geometry at 512 px requests z15 and uses USGS. The transition is caused by BNGS2's maximum view zoom, not a brightness difference between terrain shaders. The adjacent m14_2914_6518 and m14_2914_6519 tiles had a 55.8/255 mean absolute RGB step across paired 100 m strips. Another nearby pair had a 62.0/255 step.

An offline A/B using the native imagery renderer and already-cached, geographically matched reference imagery reduced those steps to 0.4 and 2.5 levels while preserving high-frequency image detail. This establishes that a shared colour grade can remove the discontinuity without replacing the sharper imagery. Applying it only when a reference happens to be cached can create a new cold-cache seam; the grade needs reliable reference coverage (or pregraded CDN imagery) before it is enabled by default.

This is separate from cloud trails, rain altitude, and black far-tile flashes.

Activity

1
MihneaTeodorStoica2d ago

Native replay confirms the result. I imported the two original .cdae meshes, kept the stock 512/128 px DDS sizes and camera fixed, disabled clouds, and swapped only the texture grade. Mean RGB step across equal screen strips fell from 53.93 to 1.71 (USGS shared grade) or 5.69 (BNGS2 shared grade). The detail-resolution difference remains, but the color jump is gone.

A separate incomplete-reference control found an adjacent pair of USGS tiles where only one had its reference halo resident. The cache-only guard introduced a new 49.9-level step where stock was 1.1. This is why I did not ship that shortcut. Pregrading geographically feathered CDN packs, or asynchronous shared-grade references with consistent coverage, avoids moving the seam to the edge of the cache.