AnsweredAssumed Answered

TRW 11.1 Enhancement suggestion and apparent bug

Question asked by Ronan Kelly on Aug 27, 2019
Latest reply on Sep 8, 2019 by Ronan Kelly

1. Additional Constraints for Regular Cone: I regularly use cloud based modeler to model Power and Light Poles. The vertical portion of many poles are cone (rather than cylinder shaped). The Auto-fitting for regular cone shaped objects seems quiet poor compared to Cylinders and boxes, 99 times out of 100 does not work without additional constraints. As a work around I have to create a cylinder at the base of the pole then use the pass through axis constraint to orientate the pole. This is not ideal where there is a bend or bow in the pole and the resulting cone does not line up with the cloud at the top of the pole. As an enhancement suggestion it would be ideal to have some additional constraint options for the regular cone geometry. Eg:

  • start and/or end cone diameter constraints (both match the diameter of an existing geometry or manual input options)
  • Fix start or end location and diameter to and existing geometry : select and existing cone or cylinder so that the resulting cone must start or end passing through the same centre point (but not locking orientation of axis).
  • Additional Modify Geometry options: when rotating the geometry (i.e. when the top of pole is offset from the cloud), rotation is always around the centre of the geometry. In most instances it would preferable to rotate about the top or bottom of the geometry (select rotate, select which end is the rotate centre, zoom in on opposite end and rotate manually until aligns with cloud)

 

2.   Additional Geometries: a regular pyramid shape would be useful

3.   Additional Geometry modifiers:

  • Modify/delete corners of a geometry. Create a perfect box based off the available cloud and then have the functionality to delete corners of the box to create a different shape (i.e. wedge) or modify/push/pull corners of the box to create a more accurate Asbuilt shape (concrete edges are rarely perfectly square).
  • Modify - add fillets and chamfers to edges: Create a perfect box based off the available cloud and then have the functionality to fillet or chamfer edges (manual input start and end chamfer sizes or select and input radius for rounded edge) but selecting edges to apply chamfers to.

 

4. Remove midpoint node on created polylines: Any polyline exported from TRW to dwg creates a midpoint node/point` between all actual nodes/point (actual nodes being where we have actually snapped to or clicked onto cloud data to create a polyline). This is an issue for post processing a line as when you are editing the end of a line it pivots around the midpoint between the end you are moving and the next actually measured point  rather than pivoting around the next actually measured point. Also it makes it hard to decipher in 3rd party software which points/nodes from extracted data are the actual extracted points. Is there currently a way to remove midpoint nodes from dwg output by default? if not can it be addressed in the next update?

 

5. Apparent 11.1.1.442  bug: UCS modifies coordinate system - when outputting a dwg (polylines and solids) from a project where ucs's have been created the resulting dwg is always on a local coordinate system whereby 0,0,0 is as per the most recently created UCS (note: this is despite selecting Home as the Export frame when writing the dwg (see image below). This was not the case in version 10. Also in Version 10 the XYZ measure tool was reporting to your actual coordinate system not the local UCS, this is not the case in Version 11 (see images below)

Pre UCS Creation: XYZ measure as per correct coordinate system

Post UCS Creation: XYZ measure to a local system where UCS=0,0,0

 

 

Steven Witte Jason Hayes

Outcomes