3D generator progress bar follows any modelId, not the current model #1043

New Issue

2026-08-13T05:22:22Z

spikerj commented

2026-08-13 05:22:22 +00:00

Receive3DModelProgress always writes progressNotificationSignal, then only copies mesh stats onto currentModel when currentModel.id === notification.modelId.

currentProgress / currentStage read the notification unconditionally (percentage || 0, stage || Queue). So a progress event for a different model (previous job, second tab, another in-flight generate) drives the progress bar and stage chip while leaving currentModel on the selected id at 0%.

Pinned by threed-generator.hub.spec.ts ("progress for a different modelId still drives the progress bar").

this.progressNotificationSignal.set(notification);
const currentModel = this.currentModelSignal();
if (currentModel && currentModel.id === notification.modelId) {
  // updates currentModel only
}

`Receive3DModelProgress` always writes `progressNotificationSignal`, then only copies mesh stats onto `currentModel` when `currentModel.id === notification.modelId`. `currentProgress` / `currentStage` read the notification unconditionally (`percentage || 0`, `stage || Queue`). So a progress event for a *different* model (previous job, second tab, another in-flight generate) drives the progress bar and stage chip while leaving `currentModel` on the selected id at 0%. Pinned by `threed-generator.hub.spec.ts` ("progress for a different modelId still drives the progress bar"). ```ts this.progressNotificationSignal.set(notification); const currentModel = this.currentModelSignal(); if (currentModel && currentModel.id === notification.modelId) { // updates currentModel only } ```

spikerj commented

2026-08-14 03:28:39 +00:00

Already on master. Receive3DModelProgress already ignores a foreign modelId, so the progress bar follows only the current model. Closing.

Already on `master`. Receive3DModelProgress already ignores a foreign modelId, so the progress bar follows only the current model. Closing.

spikerj closed this issue

2026-08-14 03:28:39 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#1043