Todd Hummel's Activities

[V8i] Fatal Error. Could not create a .ma file ... crash issue multiple times per day (Print Organizer Crash, View Attributes Crash)

Todd Hummel — Mon, 06 Jun 2016 15:21:51 GMT

MicroStation v8i (SELECT Series 2) - Version 08.11.07.443

Bentley GEOPAK V8i (SELECT Series 2) 07.11.07.619

Windows 7 Professional x86

Services Pack 1

Intel Xeon CPU E5-1620 0 @ 3.60 GHz

32.0 GB RAM

Approximately, 4-5 times per day the program will crash producing the error message attached. The problem more consistently occurs when opening print organizer or view attributes. Other occasions occur, but during random use of application. Error message reads:

"Fatal Error. Could not create a .ma file for an AddIn: ustation.dll

System.IO.DirectoryNotFoundException: Could not find a part of the path '_________'

at System.IO.IIError.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Bolean overwrite)

at Bentley.Internal.MicroStation.DotNetShim.AppManager.CreateMdlApplicationFile(String maNameToCreate, StringtaskIdP)

at AddInManager_createMdlApplicatioFile(SByte*addInMaFileName, Int 32 addInMaFileNameByteLength, SByte* maNameToCreateP, SBytex taskIdp)

[OR] Corridor objects/Template drop - enhancement

Krzysztof Burdziel — Wed, 18 Feb 2015 09:12:44 GMT

Hi,

Can we have "Synchronize with library" button under Corridor objects/Template drop please? Ideally working with multi select. At the moment, the only way to update multiple template drops is to select them all in 2D model and click "Synchronize with library" from context menu. It's time consuming.

Or I am missing something and there is a more efficient way to synchronize multiple template drops at once?

Thanks,
Krzysztof

Managing different versions of Microstation and Geopak with different clients

Todd Hummel — Thu, 22 Mar 2018 19:34:25 GMT

I'm currently working with a client that requires Microstation SS4 8.11.09.832 & Geopak SS4 8.11.09.878. I have these versions installed on my machine.

However, I also need to do with work another client that requires Microstation SS3 08.11.09.714 and Geopak SS4 08.11.09.845. It's my understanding that I cannot have two version of Microstation/Geopak installed concurrently on my machine without creating separate partitions to my hard drive.

Would there be issues using Microstation SS4 8.11.09.832 & Geopak SS4 8.11.09.878 with the client using the older software versions? Other individuals within our company that are specific to that client will be working on the same files, but using the older software versions Microstation SS3 08.11.09.714 and Geopak SS4 08.11.09.845 that the client requires.

I'm concerned that if I were to work on these same drawings with a newer version I could potentially corrupt the drawings/corridors within the drawings.

Thank you in advanced.

OpenRoads Corridor Corrupt

JTatum — Mon, 26 Sep 2016 20:07:57 GMT

Hi All,

I am working in OpenRoads and my corridor seems to be corrupt. It can handle certain functions, but anytime I attempt to relate it to another surface in the model it crashes and kicks me out of the program. One common crash happens when trying to create a point control that will tie my corridor to the existing corridor using a corridor feature as the point control. Another crash is when I attempt to use the Define Target Aliasing tool; as soon as I select my corridor, the program crashes and immediately closes Microstation. Any idea why this isn't working?

Thanks,

Jesse

Ask A Question I

Mon, 28 Aug 2017 02:31:05 GMT

Ask a question in a forum.

Corridor Feature Point Control Randomly Deleting

Todd Hummel — Mon, 28 Aug 2017 19:54:56 GMT

I have experienced, on several occasions, that point controls targeting a corridor feature from a corridor referenced into the drawing will randomly be deleted. Initially, I assumed that I accidentally detached the reference and disregarded the warning about the implications of doing that. However, I've experienced this enough to know that the issue is not from detaching the reference.

Are there any do's or do-not's that I should be aware of when using point controlling to a corridor feature that is referenced? Any other things I could troubleshoot to eliminate this rework?

Thanks

Inroads Roadway Designer Plan View Graphics

Todd Hummel — Tue, 06 Oct 2015 12:35:22 GMT

Recently, when creating new corridors, the graphics in the plan view of roadway designer are shrinking. The graphic showing the active cross section in plan view varies in size as shown in the photos below. It's becoming an issue when cleaning up end conditions. Anyway to adjust this?

Importing Pattern Lines to be Key Stations in Roadway Designer

Todd Hummel — Wed, 29 Jul 2015 21:51:44 GMT

I have hundreds of cross sections that were cut using pattern lines that are at uneven, varying stations. Is there any way to quickly input these pattern lines as key stations in Roadway Designer so the model is more accurate at these exact locations?

Roadway Designer DTM/Surface Size Limitations Causing Process to Freeze?

Todd Hummel — Fri, 25 Sep 2015 16:20:48 GMT

Running SS2 Version 08.11.07.443

Geopak V8i SS2 07.11.07.619

Memory Statistics

Element:   60.2M, 529 Blocks
Available:   28688M (Physical),   3240M (Virtual)
System:   32694M (Physical),   4096M (Virtual)
Free Limits:   50.0M (Physical),   150M (Virtual) [MS_MEMORY_FREELIMIT]
NOTE: Unable to use all of the memory in your system because current user does not have "Lock Pages in Memory" privilege. See Control Panel>Administrative Tools>Local Security Policy>User Rights Assignment.

We are running x64 OS, but the Microstation process is ustation.exe *32 and the system directory is the "systems32" folder.

When processing large surfaces/models in roadway designer, if the Private Working Set Memory ever reaches levels around 1,350,000 K to 1,450,000 K the process will cease and the surface will never build. By reducing the length of the corridor I can successfully process then entire model, but it would be preferable not to separate into multiple corridors.When reducing the length of the corridor the memory never reaches the 1,300,000 K level so I believe I am reaching some size limitations, but I cannot find anything on how to resolve the issue. I've read the article http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903.surface-size-limits-dtm-failed-allocating-memory-error but I never get an error stating "Failed Allocating Memory" and am unsure if the issues are related.

Thanks in advanced.