I would like to know if anyone else is having this issue, or if there is something that can be done about this issue.
I am having some trouble with using Profile Intersection Point.
In this example I have a line crossing two lines. I have created a line between points using the intersection snap between lines 1 and 2 and intersection snap between lines 1 and 3. Lines 2 and 3 have profiles attached.
I opened a profile model of the newly created line and used profile Intersection Point to show the location of lines 2 and 3 and created a profile from these two points. No problem, this works how I would expect.
I tried the same exact thing with another line I will call A, and created a line between points using the intersection of A and 2 and the intersection of A and 3.
I then opened the profile of this new line and went to use profile intersection point again to show lines 2 and 3 on the profile. One point will register but the other keeps saying "Elements Don't Intersect".
How is this possible? How can the same exact operation work and then not? On top of that, isn't it impossible for these lines to not be intersecting? I built the line off the intersection of the elements I am trying to show the Profile Intersection Point of.
I have tried this upwards of 15 times now, its not a matter of snapping to the wrong element, I have tried this in multiple files, have restarted the program, etc.
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
Not to be a pest, but is the answer no on being able to look at a running list of current defects that have not been fixed? Basically is Bentley saying I would have to log an issue, see if it has been logged, get a defect number reply, then wait to see if it gets fixed in the next release? I ask because I spent the last week and a half trying to redesign my civil cells again and again, but if the current defects were in a list somewhere I would have been able to look at a list of current defects, see that the issue I am having is something that needs to be in the next update and not spend my time trying to fix something I can't possibly fix and move onto the next task while I wait for the next release.
I am not sure if this is something that could be implemented but a running list of current defects in addition to resolved ones would be really useful. My unit is working on new workspaces for OpenRoads and MicroStation Connect, so there is definitely a lot of work to be done while I wait for any updates. I understand that no software release is going to be perfect, even after many updates, but as someone who works in a CAD admin role it is very time consuming to not be made aware of defects that are already logged, just to stumble into them like the people before me.