Thanks for reporting this.
I've enhanced the react workaround I've published on the forum but It's not functional at 100%.

I've another case where render mode is a problem. Changing layer color parameters like h,s,l , brightness, contrast

**edit ** the last case works after a call to viewer.scene.requestRender() :)

Any news on this? This is annoying.

I'm playing with entities and the UI I wrote toggles visibility.
Hide an entity is immediately take n into account but the opposite, showing an entity, needs to move the camera to see effect.

Hi @chdenat No new yet. If you are interesting in contributing, please let us know and we'd be happy to discuss implementation or review a PR. Thanks!

@ggetz , thank you for the news ! Unfortunately, although I know the cesium API well, I do not have sufficient knowledge to help at the core level. Sometimes I look at the source code, but it's more to understand how a class or a feature works.

Unfortunately this is a blocker for my organization updating, I looked through merge requests which affected the render loop of datasources and found the cause to be #12429, specifically:

Line 333 explicitly will prevent the update callback to run scene.requestRender() after anything other than the first frame, which is a clear regression from the behavior before this MR.

A fix requires either adding an additional flag, removing the condition !this._ready from line 327, or undoing the change. I am not sure the exact meaning of the ready flag, but it was clearly used as a "dirty" flag before this MR. I would like to get a fix in before 1.130

@ggetz I've opened a PR solving the issue, it's ready for review:

#12630

For now, the following monkey patch solves the issue until that gets merged:

const originalUpdate = DataSourceDisplay.prototype.update;
let prevResult = false;

DataSourceDisplay.prototype.update = function(time) {
  const result = originalUpdate.call(this, time);
  if (!prevResult && result) {
    this._scene.requestRender();
  }
  prevResult = result;
}