5.5 Showing meshes when they're not supposed to be there.

[Tim4DConstruct]

So, we haven't encountered this since we switched to 5.5. But when I setup a imodel in 5.5, the imodel displayed meshes that shouldn't be displayed at that moment in time. This is using ItwinTemplate running in 5.3 and 5.5 with no special settings. Just running in 5.3 and 5.5. They're purely that ITwinTemplate project under 5.3 and 5.5 with identical app ids, model ids, and changeset ids.

I can add people to the imodel if needed.

[GhisBntly]

It is expected to have several differences between the schedule display in the last 5.3 version of the plugin, and the latest 5.5 version.
Until recently, the schedule was not displayed correctly when the schedule time was precisely the start or end time of a task (which was the cause for the "flickering barge" in bridge project).
Also I think elements assigned to "Neutral"-type appearance profiles in 5.3 where hidden, although normally it depends on the presence of Install/Remove tasks for the same elements: since the plugin does not yet support dependencies between tasks, I have made these elements visible (during the Neutral task). Maybe this is the case here?
What does Synchro Pro display at the exact same time? Exactly like your 5.3 capture? Or a bit of both?

[Tim4DConstruct]

Synchro pro displays what it looks like in 5.3.

[GhisBntly]

Ouch 😟 Can you please add me to the project?

[Tim4DConstruct]

Yes will do.

[Tim4DConstruct]

Apparently you already have been added to the project ill email you the link and the name.

[GhisBntly]

It seems there is a problem with the dates displayed: Feb. 1st, '26 is not in "week 474" of the project, so I'm not sure which dates were used in your captures. Week 474 looks closer to your 5.3 capture, and lands early in September 2033 in Synchro Pro.
I get this for Sept. '33 on my end (capture from iTwin Engage EAP, but same display in the 5.5 plugin), which matches what I see in Synchro Pro:

[Tim4DConstruct]

Two new screenshots here first one from 5.3 and second one 5.5. Same date and week.

Synchro pro looks like 5.3

[GhisBntly]

That's right, this is a case of dependencies between tasks: Elements have a Maintain task first, only followed later by an Install task.
In this case, the Element should not be visible before the Maintain task, because it has not been "installed" yet.
But our current implementation treats all tasks independently, and all resources are visible before and after Maintain tasks.
I am currently working on supporting all these task dependencies properly.

[Tim4DConstruct]

Okay good to know thank you.