TBC 2026.10 & Worksmanager

1

Hi all,

I have an odd issue that I believe is related to the “new” Works Manager (since the TCC “end-of-life”), and I can’t figure it out. I’ll also admit upfront that I really don’t enjoy using the Trimble community forums, so I’m hoping to get some insight here instead.

Here’s the issue: Since updating to TBC 2026.10 and exporting designs through the “Construction Data” tab in TBC, I’ve noticed a couple of problems:

1. The VCL files I’m sending to the machines are massive compared to the old TBC “Works Manager VCL exporter.”

  • Works Manager export: 17.4 MB

  • TBC VCL export: 384 KB

2. I’m seeing a lot of lag on machines running the new TBC/Works Manager VCL exports. They take forever to sync, and the operator display lags as well.

We’re running the most up-to-date software on the machines, and all firmware is current too.

My initial suspicion is that the VCL exported through the new Works Manager workflow is creating a massively inflated file structure. I know 17.4 MB isn’t huge in absolute terms, but that’s roughly 45 times larger than the traditional VCL export from TBC, and it seems to be causing real performance issues in the field.

Has anyone else run into this, or found a way to reduce the export size?

Note: Under “Guidance surfaces” in Earthworks 2.24, there is the OG file and that’s what I don’t want/need to be upload. I believe that’s what’s causing the inflated file sizes but not sure how to not send the OG through TBC and works manager.

Thank you,

   Andy
1 Like
2

Good morning Andy,

Project Explorer/Project/Cleanup VCL file/Yes

This will get rid of the OG file and a ton of the noise in the VCL.

VCL Clean up
VCL Clean up1019×743 63.5 KB

3 Likes
3

I don’t know if cleanup helps with this or not, but if you are exporting a surface tie or anything connected to your OG surface, it will probably grab the OG surface as well…

1 Like
4

Andy - you can use the legacy files types (svd,svl) in works manger to machines. its what i do…:wink:

1 Like
5

Hi all,

Thank you for the feedback.

I have reached out to Trimble/Sitech with no response, Shocker. I will be trying the VCL cleaner today and confirm if that did the trick @Jason_Smyth .

@nate_doyle SVD/SVL is my typical workflow but having the VCL head to my machines and rovers would be nice. :smiley: Appreciate ya

6

I personally love the .VCL workflow through WorksManager. There have been issues along the way, but generally it’s way simpler and the rovers/machines handle everything I send 99% of the time.

1 Like
7

Agreed @nelsonhays ,

Notice any odd issues with the workflow in TBC 2026.10?

8

No, latest version has been working fine for me.

1 Like
9

You can also use Smart Model and use the right click on a surface to create a Duplicate TIN surface - the duplicate TIN is a dumb TIN model that has zero dependencies. Those can be sent to the field as a VCL file with no baggafe or overhead.

Alan

2 Likes