OpenRoads "civil display browser" and one element's profile model crash in one SS4 file

The task I'm on involves forming complex chains that follow existing ditch flow lines so that I can view the existing profile along them. Many of them have included both Microstation elements (without civil data, and I can manipulate these with Microstation's Modify Element tool) and civil elements. They've all behaved fine when I opened the profile model on them.

One particular chain is not okay (for no reason that I have any guesses at). It crashed Geopak with a .NET error which I should have copied down, but I didn't. 

I disabled Geopak and opened the file. As expected, the view I was using for the profile is not accessible, but otherwise the file opened, and I had access to the 3d model.

I enabled Geopak again and opened the file and everything seemed to be fine. I attempted to use the keyin civil display browser, which I thought was a no-brainer to reset the profile model. Geopak is crashed again.

The same thing happens on another computer in my office, and on the flip side, I can open other files just fine in Geopak.

I took a leap and discovered that I can render the profile in another view--view 6; I had been using view 7 in the past--and it works just fine, even on this element where the problem was triggered. The civil display browser continues to crash Geopak.

Any thoughts? I'm using Power Geopak .845

Parents Reply Children