Hi, I'm having a problem with 1 out of 5 almost identical corridor models. They were all created at the same time and in the same way, but for some reason, one of them is behaving very oddly.
Whenever I usa a command (ANY command...) it starts processing stations, counting from 0-100% in the process-bar and when it reaches 100%, it starts all over from 0%.. This processing seems to be infinite and I don't understand why this is happening.
I tried solving the problem by starting all over, modelling the corridor from scratch in a new file, but I'm having the same problem again. I have never seen this in any of my other files and I have no idea what the problem could be..
I have a couple of Key Stations and Point Controls, but less than in my other files and only 1 template drop.
I'm working in PowerCivil V8i (SS4)
Hi Rikke,
Sounds like a processing loop - are there any point controls that may be causing it, eg. corridor 1 has a batter point controlled to corridor 2 batter, and corridor 2 batter is point controlled to corridor 1 batter. When corridor 1 processes, batter updates and moves corridor 2 batter. When corridor 2 batter moves, it initiates a process of corridor 1 batter and the process loops forever.
This can also sometimes be caused by point control or parametric constraint start/end station snap rules that somehow create a loop.
We've found loops to be the most time consuming and frustrating problem we get in OpenRoads.
Regards,
Mark
OpenRoads Designer 2023 | Microstation 2023.1 | ProjectWise 2023
Hi Mark,
I've already concidered the loop situation, but I only have 1 corridor and 1 template drop in my file, and when re-doing the whole model I was very cautious, not to create such conflicting loops with my point controls.
The point control or parametric constraint thing, you're suggesting, doesn't sound like something I've tested yet. Would you mind elaborating how I can test this or what I should out look for? (and maybe where?).
I've tried to delete some of my point controls, hoping to deleting the one causing the problem, but this just sets the loop in motion, so I might have to be able to identify the problem without starting any corridor-calculating commands, in order to only delete that one..
Maybe open in Microstation to delete an element that causes processing loops?