Trimble Business Center

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

As of my last post to this thread our department users have not updated to the 

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

I am having a nightmare with point cloud registration since updating to 2024.  A myriad of different errors come up.  Can't import a simple e.57 file that I just exported myself from TBC.  

As of my last post to this thread our department users have not updated to the 

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hi Derek,

We have had the same.  Lots and lots of issue.  Saving problems, registration, import, etc. all when point clouds are involved.  Bummer.  And not much at all from Trimble folks on this.

I am having a nightmare with point cloud registration since updating to 2024.  A myriad of different errors come up.  Can't import a simple e.57 file that I just exported myself from TBC.  

As of my last post to this thread our department users have not updated to the 

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hey Clayton and Derek,

New releases bring a lot of new functionality, sometimes unforeseen issues can pop up. If a particular update isn't working for you, it shouldn't be too hard to roll back to a previous version that was more stable for your setup. Also, for more specific help, I'd recommend reaching out to your local Trimble dealer-they can connect with the dev team and get a deeper look at what's going on.

Hi Derek,

We have had the same.  Lots and lots of issue.  Saving problems, registration, import, etc. all when point clouds are involved.  Bummer.  And not much at all from Trimble folks on this.

I am having a nightmare with point cloud registration since updating to 2024.  A myriad of different errors come up.  Can't import a simple e.57 file that I just exported myself from TBC.  

As of my last post to this thread our department users have not updated to the 

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Bizarre! I am not seeing any of this behavior. Are you sure that you are using using the max possible ram (Options-->Point Clouds-->Rendering memory cache size? Also, you are ONLY using an SSD drive and not a spinning or network drive, correct? Just trying to come up with any ideas here? If running AMD CPU, did you adjust the affinity settings? Lastly, is your temp directory pointing to a SSD drive or spinning/network? I would never use any network drives or spinning drives (for any reason really) with TBC. The same goes for any application that uses any amount of resources really. 

Hey Clayton and Derek,

New releases bring a lot of new functionality, sometimes unforeseen issues can pop up. If a particular update isn't working for you, it shouldn't be too hard to roll back to a previous version that was more stable for your setup. Also, for more specific help, I'd recommend reaching out to your local Trimble dealer-they can connect with the dev team and get a deeper look at what's going on.

Hi Derek,

We have had the same.  Lots and lots of issue.  Saving problems, registration, import, etc. all when point clouds are involved.  Bummer.  And not much at all from Trimble folks on this.

I am having a nightmare with point cloud registration since updating to 2024.  A myriad of different errors come up.  Can't import a simple e.57 file that I just exported myself from TBC.  

As of my last post to this thread our department users have not updated to the 

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hi Derek and Zach,

Thank you for your feedback.  Regarding contacting my vendor support, we do often report these items to our vendor.  We also place them hear, as the discussion tends to be much more involved and often includes Trimble folks input, which matters.  Regarding rolling back software, it is time consuming and expensive.  We expect updates to work.

I really do appreciate your help Zach.  We do address the memory cache reliably as it resets with each install.  Everything we do is by SSD and it is networked.  Trimble can't expect in this day and age of servers and companies using mapped networked drives as standard operating procedure that operating on local machines is acceptable.  It would create a nightmare of issue with chain of custody file preservation and organization.  Almost every professionally consulting firm of more than a few survey staff that I have peers in uses some form of a mapped network drive with strict file and folder practice policies.  Every other software we use does not have issues with this, and it has been normal practice to use mapped network drives since the early 2000's.

I will look into the affinity settings.  I don't think anyone is running AMD CPU in my group.  We have a muscle computer which has an AMD processor and we use for aerial imagery processing, which we do outside of Trimble software, it does have an installation of TBC, except we don't use it very often. I will look there at these affinity settings and I discover what they are.  I think I have read some reporting on this, so I think your clue is enough for me to hunt it down.

Lastly, I will double check our location of our temp file.  All of our workstations are solid state memory.  But looking that the temp path may help anyhow.

Again, thank you for your input.  We typically enjoy TBC and realize great success in efficiencies that get lost in Civil 3d when working with point clouds, so we need to continue to use it and use it successfully.

Thank you.

Bizarre! I am not seeing any of this behavior. Are you sure that you are using using the max possible ram (Options-->Point Clouds-->Rendering memory cache size? Also, you are ONLY using an SSD drive and not a spinning or network drive, correct? Just trying to come up with any ideas here? If running AMD CPU, did you adjust the affinity settings? Lastly, is your temp directory pointing to a SSD drive or spinning/network? I would never use any network drives or spinning drives (for any reason really) with TBC. The same goes for any application that uses any amount of resources really. 

Hey Clayton and Derek,

New releases bring a lot of new functionality, sometimes unforeseen issues can pop up. If a particular update isn't working for you, it shouldn't be too hard to roll back to a previous version that was more stable for your setup. Also, for more specific help, I'd recommend reaching out to your local Trimble dealer-they can connect with the dev team and get a deeper look at what's going on.

Hi Derek,

We have had the same.  Lots and lots of issue.  Saving problems, registration, import, etc. all when point clouds are involved.  Bummer.  And not much at all from Trimble folks on this.

I am having a nightmare with point cloud registration since updating to 2024.  A myriad of different errors come up.  Can't import a simple e.57 file that I just exported myself from TBC.  

As of my last post to this thread our department users have not updated to the 

Hello,

Trimble any input?  This is critical.  We can't operate like this and a bug this severe can't be issued to paying customers.

We are using the latest release and I don't believe we had any issues until we, as a department, installed this release.  2024.01, released this August.

The failure point is different from my team's users.  Some cannot use the classify point cloud tool at all without complete and total failure and quit of the TBC program.  TBC just disappears as if it wasn't even started, but it does leave behind the lock file.  Other users can successfully get through each step of the registration tool, but at the point it is time to save, this causes a crash where TBC become unresponsive, but it doesn't disappear, just locks up.  and sometimes we are able to get through the total classification process including refinement.  Best luck is to do each step separate and limit the regions of interest to ground and then refine only ground.  What a bummer.

We have installed, reinstalled, cleaned, reinstalled, on line install, off line install, etc. Any help is appreciated.

  Yes, I have. 2024 and 2024.1 have severe point cloud processing bugs.

   Its not source dependent but some LAZ files are worse than others.

Classify ground usually works. Classify and refine ground almost never does and if it doesn't, you have to restart. If Classify/Refine finishes, sometimes it will put the point cloud in the wrong place or you'll actually drag it around on the screen when you pan/zoom.

2023 was almost flawless. But advanced point cloud filtering is so awesome, I've forgiven TBC for not fixing this for all of 2024.

I always use the TBC office utility to clean out previous installs before updating.

I went to a Wingtra lidar demo and the salesman had TBC point cloud classify crash on him. Never could get it to work.  That had to be embarrassing. 

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Looks like TBC 2024.1 is now available.

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

hello everyone. 

i have a more general question but in the realm of this discussion. we have been running a uav lidar setup. we have not moved to tbc 2024 yet. i forget what we are on 5.9 or something. i would like to use tbc as our main point cloud coordinate system transformation, classifier, surface builder, and linework extractor. 

we have a lot of different software carlson cad, civil 3d, cloudcompare, 3d survey, qgis… tbc is by far the best visualizer in 3d. and the newer classifier works well with terrestrial scans. 

here is our issue. we can barely even load a uav lidar dataset into tbc. it takes 15-20 minutes to get the las into tbc and often it stalls out at 100%. 

the recent sites have been a couple km corridors or couple hundred acres. recent 12km corridor and coming up couple thousand acres. i do not see how it is possible to use tbc for these datasets if we are already having trouble loading reduced size projects. for the last couple km corridor i think there was maybe 30 million points or something maybe there was some more zeroes there. i put it in cloud compare, classified it, then reduced the ground to 1million points so that i could bring it to tbc to work on. but this seems ridiculous to me. any thoughts or workflows people are using, better computer? i will say our ram is not super high. we will process on our "server" which only has 32g ram. it has decent graphics card(s) but when i look during loading it does not use them. a but fuzzy on checking these specs but i can look next time we try to do something. 

back to the initial post, it takes a really long time to classify in tbc and sometimes glitches out. i don t think that with larger sites this will get any better and i question why i can do this work in cloudcompare? maybe tbc needs to take a look at how they do it, maybe just the truncation of coordinates makes it all speed up????

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Ian - without going into various settings in TBC that could help, 32 GB of RAM is simply not enough in this day and age. Have you watched your task manager to see if your ram is maxing out when you load these clouds? Since the newer versions of TBC are more graphics intensive, I'd want at least a 30xx series card.  Beef that up with an i9 and 64 gb ram. Time is valuable, get a machine that will not interfere with your workflow. 

hello everyone. 

i have a more general question but in the realm of this discussion. we have been running a uav lidar setup. we have not moved to tbc 2024 yet. i forget what we are on 5.9 or something. i would like to use tbc as our main point cloud coordinate system transformation, classifier, surface builder, and linework extractor. 

we have a lot of different software carlson cad, civil 3d, cloudcompare, 3d survey, qgis… tbc is by far the best visualizer in 3d. and the newer classifier works well with terrestrial scans. 

here is our issue. we can barely even load a uav lidar dataset into tbc. it takes 15-20 minutes to get the las into tbc and often it stalls out at 100%. 

the recent sites have been a couple km corridors or couple hundred acres. recent 12km corridor and coming up couple thousand acres. i do not see how it is possible to use tbc for these datasets if we are already having trouble loading reduced size projects. for the last couple km corridor i think there was maybe 30 million points or something maybe there was some more zeroes there. i put it in cloud compare, classified it, then reduced the ground to 1million points so that i could bring it to tbc to work on. but this seems ridiculous to me. any thoughts or workflows people are using, better computer? i will say our ram is not super high. we will process on our "server" which only has 32g ram. it has decent graphics card(s) but when i look during loading it does not use them. a but fuzzy on checking these specs but i can look next time we try to do something. 

back to the initial post, it takes a really long time to classify in tbc and sometimes glitches out. i don t think that with larger sites this will get any better and i question why i can do this work in cloudcompare? maybe tbc needs to take a look at how they do it, maybe just the truncation of coordinates makes it all speed up????

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

hello everyone. 

i have a more general question but in the realm of this discussion. we have been running a uav lidar setup. we have not moved to tbc 2024 yet. i forget what we are on 5.9 or something. i would like to use tbc as our main point cloud coordinate system transformation, classifier, surface builder, and linework extractor. 

we have a lot of different software carlson cad, civil 3d, cloudcompare, 3d survey, qgis… tbc is by far the best visualizer in 3d. and the newer classifier works well with terrestrial scans. 

here is our issue. we can barely even load a uav lidar dataset into tbc. it takes 15-20 minutes to get the las into tbc and often it stalls out at 100%. 

the recent sites have been a couple km corridors or couple hundred acres. recent 12km corridor and coming up couple thousand acres. i do not see how it is possible to use tbc for these datasets if we are already having trouble loading reduced size projects. for the last couple km corridor i think there was maybe 30 million points or something maybe there was some more zeroes there. i put it in cloud compare, classified it, then reduced the ground to 1million points so that i could bring it to tbc to work on. but this seems ridiculous to me. any thoughts or workflows people are using, better computer? i will say our ram is not super high. we will process on our "server" which only has 32g ram. it has decent graphics card(s) but when i look during loading it does not use them. a but fuzzy on checking these specs but i can look next time we try to do something. 

back to the initial post, it takes a really long time to classify in tbc and sometimes glitches out. i don t think that with larger sites this will get any better and i question why i can do this work in cloudcompare? maybe tbc needs to take a look at how they do it, maybe just the truncation of coordinates makes it all speed up????

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?

Apart from your RAM being woefully inadequate, you seem to indicate you are processing or loading from a server. This is a big no. You should have the TBC project on your local machine as well as any files, especially point clouds, which you want to bring into the project. Read/Write to a server is asking for trouble. A fast M2 or SSD type drive on your machine is also a must.

I too had questions about the time TBC takes to load large point clouds etc and the explanation I got was that TBC is (the only?) true geodetic application and it has to load all that data into a proper database and do al sorts of clever things that GlobalMapper, CloudCompare etc dont. 

hello everyone. 

i have a more general question but in the realm of this discussion. we have been running a uav lidar setup. we have not moved to tbc 2024 yet. i forget what we are on 5.9 or something. i would like to use tbc as our main point cloud coordinate system transformation, classifier, surface builder, and linework extractor. 

we have a lot of different software carlson cad, civil 3d, cloudcompare, 3d survey, qgis… tbc is by far the best visualizer in 3d. and the newer classifier works well with terrestrial scans. 

here is our issue. we can barely even load a uav lidar dataset into tbc. it takes 15-20 minutes to get the las into tbc and often it stalls out at 100%. 

the recent sites have been a couple km corridors or couple hundred acres. recent 12km corridor and coming up couple thousand acres. i do not see how it is possible to use tbc for these datasets if we are already having trouble loading reduced size projects. for the last couple km corridor i think there was maybe 30 million points or something maybe there was some more zeroes there. i put it in cloud compare, classified it, then reduced the ground to 1million points so that i could bring it to tbc to work on. but this seems ridiculous to me. any thoughts or workflows people are using, better computer? i will say our ram is not super high. we will process on our "server" which only has 32g ram. it has decent graphics card(s) but when i look during loading it does not use them. a but fuzzy on checking these specs but i can look next time we try to do something. 

back to the initial post, it takes a really long time to classify in tbc and sometimes glitches out. i don t think that with larger sites this will get any better and i question why i can do this work in cloudcompare? maybe tbc needs to take a look at how they do it, maybe just the truncation of coordinates makes it all speed up????

Thank you for the recommendation.  We will give it a shot and report back.

Hello,

Have you looked at updating your Graphics Card Drivers?

Hello, 

As a department we have approximately 10 work stations all with the 2024.01 of TBC installed.  We have noticed workstation specific stability issues.  The most common of them is the classify point cloud process.  Some workstations are not able to classify point cloud regions at all.  Others do not have issues.  For example, importing a point cloud file created with Agisoft Metashape of a five acre commercial road and blank pad site, the import is successful on all workstations.  On some workstations when attempting to process this point cloud, TBC just closes with the classify process at 1% complete.  On others, the process of classification completes without issue.  We have had this on enough workstations that we are confident it is not the point cloud.  It is the program.

Has anyone else had this issue?