|
| @JulianK, thank you very much for your reply.
> "My recommendation is to only select the tracks you actually need when planning the work."
Yes, that's the workaround we're currently using, and it does improve performance significantly.
The challenge is that when a Work Plan is opened for the first time, the display automatically creates and selects a track set containing all tracks from the plan. In our case, this initial step is what causes the delay.
Ideally, for our workflow, the display would not automatically create this track set by default and would instead allow the operator to select only the tracks needed for that operation.
Perhaps a useful enhancement would be to make the automatic creation of track sets optional, allowing each operation to decide whether track sets should be generated automatically or managed manually by the operator.
@RecreationalTillage
We use Civil 3D together with a plugin developed by one of our partners to create planting, cultivation, and harvesting guidance projects. The plugin exports adaptive curves directly to Operations Center or a USB drive.
The solution works very well and meets our operational requirements.
Following the developer's recommendation, each track is limited to approximately 250,000 vertices. Because of that, larger fields often need to be divided into multiple tracks. Field topography can also increase project complexity in some situations.
For example, in one of our largest fields, covering about 2,700 hectares (6,700 acres), the project contains 44 tracks.
Thank you all for the insights and discussion. | |
|
How to Prevent Gen5 from Automatically Selecting All Tracks in a Work Plan?
