I have been trying to follow Bentley's best practices for file management within the OpenRoads environment, but I am running into an issue. It seems that whenever OpenRoads needs to create a 3D model on it's own, it will fail. If I create a file to contain my alignments, for example, I will start it in a 2D design model. When I go to begin the vertical geometry of that alignment, PowerGEOPAK will apparently try to automatically create the 3D design model needed, but it will hang and hang and eventually quit. If I start the process within a 3D model from the start, I don't have any issues. Is it having trouble finding a seed 3D design model? If so, how do I specify which design model I want to use as its seed?
Any other ideas about why it would fail at this step?
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
I don't recall if I ever replied to your message, but we are still dealing with this issue. We begin each project using a seed file that has been supplied by our client, with each one getting a coordinate system attached. Other than that, the seeds appear to be the same. We have one project where we don't have this problem and we have been using this as the seed file for the past couple of years. As we will occasionally get new seed files to use where we see the problem again, but I can't tell what the difference is between the seed files, other than the coordinate system. Would I be able to upload the good file along with the bad file for testing?
Ken: I have seen similar issues across many clients since OpenRoads was released. An example is in a large midwestern state DOT where they were experiencing greater incidence of crashes than expected. They were literally crashing every 5 minutes. Built a new seed file and the crashes went away. Well, Openroads crashes sometimes, sorry to say, but not every 5 minutes.
For seed files which have been around for years (sometimes decades) they just seem to accumulate cruft which OpenRoads finds objectionable. These problems are not always obvious or easy to find.
I always recommend that when starting to use OpenRoads that new seed files be generated from scratch. Since seed files are pretty basic now, compared to the olden days, it just makes sense to start fresh. My standard practice when developing new workspaces is to record the DGN settings from the current seed file then throw it in the trash. Then I make a brand new seed file starting with one of the seeds delivered in the product.
Senior Project Engineer
Thanks for the input, Robert. If I take the latest Bentley delivered seed file, I plan on just going through the design file settings to ensure all looks good for our use. Do you see anything else that would need to be checked? Thanks again.
Here's my list of things I review in the seed: