You will need to set the point cloud related settings in the option command. Once you have a point cloud it can be used to make a surface. With the new objects when you display the point properties the points in the point cloud will not display their properties, but your control points will. It takes a long time to delete the original point objects (they are written to disk so you can undo them) so I would start with a new project as you have very little other data. This point cloud will now display instantly. yxz then you can drag and drop the file into your project and it will create a point cloud object rather than 350,000 points. You should import them as a surface or a point cloud. It may be that the difference you are seeing between versions is that newer version have options to display more of the points properties, hence more is drawn. This causes a lot of text to be parametrically displayed. The file also has all of the point display options enabled. The file as I received it takes 6.2 GB of memory to load. These types of points have 5k of information attached to them to position them with lat long and grid coordinates, names, feature codes, etc. So the problem is that the 350,000 points were imported as survey points. Should we be looking at intel i7 or i9 processors ? So. does anyone have any insights on this matter?ĭoes anyone here have a XEON processor with TBC v5.0 and everything is working fine ? The staff member said this is working fine. we imported the same txt file into TBC v3.7 old intel i7 processor.we imported txt file with a whole lot of GPS data into TBC v5.0 XEON CPU machine.does TBC v5.0 not like xeon processors? :-) When I was reading articles where people have no problem with v5.0 they all have intel i7 processorsĪll articles where i read where TBC has slow performance I see that people are using xeon processor. We have opened same document in version 3.7 and 3.6 and it is much faster. But TBC is acting like it is trying very hard to make simple tasks. so the computer is not even trying or having a hard time when working on TBC. Im no TBC specialist, i'm a computer specialist :-) OS: Windows 10 Professional 64 Signature ed.CPU: Intel Xeon E3-1505M 2,8-3,7GHz quad core.We have read a lot of articles about this on the Trimble forums and have tried all kinds of solutions without any results.
He has been complaining that TBC is very slow.
0 kommentar(er)
