PowerCivil geometry - can someone test if this leads to crash?

I am sending video with instructions how crash powercivil for 100% in a few seconds and create element that is undeletable, unselectable... anything associated with this element leading to crash.

Parents
  • ok. you are not using the tools as intended. the first tool, place alignment by pi, you can tell it the radius of the curve while placing it and therefore eliminating the need to edit a complex alignment (not recommended). If you want, you can create two lines that intersect and fit the radius that way.
    please review our wikis on horizontal geometry
    communities.bentley.com/.../16019.horizontal-geometry-openroads

    For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki

     



  • This is a big problem use the tools as someone intend. I think the program gives the user tools and is on him how he use them. If something does not work it's a bug in the program. Surely you do not have to every problem that the user needs to resolve separate instruction or video. In this case, I could just insert the arc in the creation of geometry, but there are cases where I can not.

    It therefore reason to report this problems, or Bentley knows them, but is no reason to solve them? But how to recognize abnormal usage from bugs?

    PowerCivil for Czech Republic V8i (SS4) 08.11.09.790

  • I think the issue Nico is pointing out is that in the video you are using the Complex by PI tool which already has built in the option of setting the radius of the curves. If you used it properly, you wouldn't be cutting out some of the linework and you wouldn't be assembling a complex alignment from the bits that remain.

    It seems that the anticipated workflow is to use Line Between Points (or any number of other tools), and then create fillets between these simple elements, and then create one complex element from all those.

    That said, I can definitely see that someone might do Complex by PI as a shortcut. There are technical and also design issues with taking that route: among them is that if you do go that route you can only move the PIs down the road, whereas the usual case of having separate line segments allows you to establish bearings more flexibly.

    In the end, here's what I found: If you do all the same steps as the original post, it will work if you insert a step just before creating the fillet to drop complex on the element you created with Complex by PI.

    Personally, I'd agree with you that this looks and feels like a bug. It's probably a manifestation of the design analog to object types in programming. 

  • Is there safe and fast way how add new peak into complex element? And is possible insert peak, which is displayed correctly as convex and concave?

    Something I'm doing wrong because the geometry under the corridor quite often stops working, stops responding to changes, only change through text parameters works correctly. I sent the file to the support and the response was that the file is corrupt and is no way how fix it. But this happens in almost every project.

    PowerCivil for Czech Republic V8i (SS4) 08.11.09.790

Reply
  • Is there safe and fast way how add new peak into complex element? And is possible insert peak, which is displayed correctly as convex and concave?

    Something I'm doing wrong because the geometry under the corridor quite often stops working, stops responding to changes, only change through text parameters works correctly. I sent the file to the support and the response was that the file is corrupt and is no way how fix it. But this happens in almost every project.

    PowerCivil for Czech Republic V8i (SS4) 08.11.09.790

Children
No Data