Mark Shamoun's Activities

Corridors do not reflect changes in item types

Robert Garrett — Thu, 31 Aug 2023 20:00:25 GMT

Consider the following:

Item types are configured to compute quantities according to specifications.
A corridor is created.
Specifications are updated which causes changes in pay items. Changes include:
- New pay items
- Abandoned pay items
- Changes in spelling
The feature definitions and item types are updated to reflect the changes.
The corridor DGN file is updated to read the new feature definitions and item types.
All the features in the corridor file which are not part of the corridor reflect the changes.
Features which are part of the corridor DO NOT reflect the changes.

If I make a new corridor in the same file, the new corridor is correct. But the old corridor never gets the changed items.

I have tried reprocess the corridor, swap out a template and then swap back. The only way to fix things is to either:

delete the corridor and start over
touch every component in the corridor and correct the pay item.

How To Fix Bowties in OpenRoads Designer Connect Edition

Aaron McLean — Thu, 02 Sep 2021 19:22:00 GMT

Hi,

Does anyone know a quick solution to fix the Bowtie Error that happens around tight corners of a corridor? (image below)

- I know you can delete all the vertices, but it just goes back and re-draws if any edits are done to the corridor.

-I know you use a clipping reference to clip out the bowtie, and then generate new lines manually but that is very tedious.

Looks like Civil 3D solved this in 2018 so surely ORD 2021 must have a solution no?? Civil 3D 2018 New Feature: Clear Corridor Bowties - YouTube

Thanks in advance!

Aaron.

Annotating cross slope of subgrade on cross-sections

Adam Wieczorek — Thu, 09 Feb 2023 09:06:58 GMT

I am using ORD 2022 R1. I cannot get cross slopes of subgrade to be annotated on cross-sections. Neither with all segments nor for created list of segments. It works as long as segments are on "top surface". If segments to be annotated are not on top, but on the bottom or at some intermediate level, no cross-slope is annotated.

And now, delivery, 800 cross-sections, urgent need to annotate cross-slope on bottom layer, and stuck. If the cross-slope is constant over along corridor, I would create a dummy annotation cell with fixed slope label, but slope of subgrade changes a lot.

Would appreciate any idea how to get cross-slope of bottom layers annotated on cross sections.

Adam

3D model appearing in Cross section DWG exports

Chris Fysh — Wed, 07 Jul 2021 06:05:09 GMT

Hi Everyone,

I am currently trying to export my cross sections from open roads designer to DWG auto cad format.

However no matter what setting I try on my export the DWG files seem to contain the 3D model (as shown) I have tried disabling 3D settings within the References Tab within the export utility with no luck.

Any ideas?

Thanks in advance!

Convert LandXML to a Mesh Surface to allow for AutoTURN to Read?

Michael Veerman — Wed, 08 Feb 2023 03:29:43 GMT

Hello, I have a drawing with an imported LandXML which projects a surface. In order for AutoTURN read the surface, the LandXML/Geopack surface needs to appear as a triangulated Mesh so that AutoTURN Pro can use to generate a 3D simulation.

Just to illustrate, I want to turn this:

Into something like this (Surface Readable by AutoTURN):

Any help would be greatly appreciated.

Thank you!

Superelevation Annotation with Parabolic Transition

Ryan McCormack — Mon, 01 May 2023 02:22:33 GMT

Hi All,

Does anyone know how to "correctly" show superelevation annotations when Parabolic Transitions are being used? When I am annotating superelvation on long sections where parabolic transitions are used, the "actual" cross fall is being annotated instead of the "point" crossfall. See images below of Superelevation Editor and what is actually annotated on the long section. I would like to show the station and crossfall information from the Superelevation Editor on the long section.

Line at interface between terrain models

Greg Eden — Wed, 19 Apr 2023 09:49:20 GMT

Hoping this is an easy answer, but I was wondering if there's an easy way to generate a feature line at the interface between two intersecting terrain models. The best I can think of is to create a delta terrain, display it as contours then copy the zero-height contours, but this is less than ideal.

ProjectWise Integration for Microsoft Office 365 CONNECT Edition 10.00.03.906

Ranveer Basra — Thu, 16 Dec 2021 20:52:50 GMT

Hi Noticed this release however what is fixed in his integration module for Office 365?

ProjectWise Integration for Microsoft Office 365 CONNECT Edition x64 (SES) (English) Download

Version:10.00.03.906Date:12/15/2021\

Thanks,

Ranveer

When will we get multiple user full access to one file in MicroStation?

stuartw — Wed, 10 Jan 2018 23:47:14 GMT

When will a version of MicroStation be released that will allow multiple users to read/edit one file? Is this in the pipeline for a future release?

Revit can do this and, from my point of view, works a treat. This allows whole team to work in one model.

OpenBridge Modeler (v. 10.11.00.310) - Long Section irregularities (vertical lines created at each stroking distance)

Rastislav Krakovsky — Tue, 31 Jan 2023 13:34:27 GMT

Dear OpenBridge Modeler community,

I'm exploring the software for its functionality and ease of use for the current workflow that we, in the company, want to apply/have and I'm having issues with Long Section/Profile view that is following the Bridge alignment path (or any Feature Line).
The Long Section/Profile view is perfect for creating a section that is at constant placement in regard of the bridge, which is perfect for curved Bridges.

The section cuts through attached geometry as intended but it is producing vertical lines at every Stroking Distance (as per the definition values) - these vertical lines are not something I want to show there as these do not exist in 3D model! They are also misleading, if left unattended, and may be/are mistaken for Construction Joints.

Is there a way how I can do a Long Section or Elevation that would follow the curvature of the Bridge?!
..we are in 21st century so I would expect that there is a solution to this (other than masking those vertical lines)...

Many thanx in advance for any reply.

[CONNECT] Level Global Display bug?

Mark Shamoun — Tue, 08 Jan 2019 12:35:42 GMT

Hi all,

I'm having an issue intermittently for the last few versions in Microstation CE (and Power Platform products like OpenRoads Designer) where Global Display of levels doesn't turn levels on/off and does some strange things (see attached video). It happens very randomly and doesn't fix itself up by restarting the session, etc. View Display and Global Freeze work perfectly so i'm not too sure whats happening.

Anyone seen this before? Any ideas how I can resolve it - its driving me crazy!

https://youtu.be/6NJDPg6EwyI

GUID

Andrei Chiriac — Thu, 14 May 2020 11:06:44 GMT

Hi,

Is it possible to export a dgn file made in OpenRoads Designer as an IFC? Or is it possible, somehow, to get the GUID of a corridor component ( let's say asphalt layer) in a dgn file? The reason why I am asking is that the client wants the project delivered in BIM360 and want so be able to read the GUID of an element/componet etc.

Thank you

OpenRoads Designer render runs out of memory

Merlijn van Beurden — Thu, 05 Dec 2019 07:51:35 GMT

When I record an animation script in OpenRoads Designer, it seems that all recorded frames are stored in the RAM. This causes a crash in OpenRoads Designer when (almost) all RAM is used. Even when all frames are made without a crash, the RAM is not emptied until OpenRoads Designer is closed. This goes for both 2018 Release 2 and 2019 Release 2 on multiple machines.

I record the frames as JPEGs, so I can continue from the moment of crashing, but that means I have to keep checking whether the program has crashed. For large scripts (7000+ frames) I need 3 runs, while I would like to just let it render overnight. I also need to restart ORD for every recording, as the previous recording is still in my RAM until ORD is fully shut down. In my opinion, the frames should be released from the memory as soon as the JPEG is made. I have set the cache size in the render preferences to 25600 MB (+/- 80% of the available 32 GB), but this did not help. Is there a setting I am overlooking?

I have attached my recording settings, although I don't think the problem is in those.

Thanks in advance!

Kind regards,

Merlijn

Cross sections cutting slow from corridor model

Ryan Hoefs — Mon, 17 Dec 2018 17:35:31 GMT

I have a rather large model, it never used to be slow ( could cut around 550 sections in about 5 minutes) but now has slowed to a halt or crash. I have tried cutting them through a "section" file with the models attached there and from the base model file. Does anyone have any thoughts on getting this file to process sections quicker? When I try to do dynamic sections, microstation grinds a halt until it process the 3D model very slowly. Any ideas are helpful! Thanks in advance!

[CONNECT C#/C++/VBA] OpenRoads - Model Flags/Properties - Annotation Cell

Mark Stefanchuk — Sun, 23 Sep 2018 19:33:35 GMT

Versions: OpenRoads Designer and SDK Update 4: 10.04.00.48. And MicroStation Update 10 (10.10.00.32 and SDK 10.10.00.23).

I am trying to create a model (a cell) that can be placed as annotation cell. The model gets created as expected, but fails to set CanBePlacedAsAnnotationCell to true. I have set this as a discussion since I found a solution. But I do have a basic question - that is, why doesn't the C# or C++ versions work? Or, what did I miss? Suggestions welcome!

Here's my C# code...

    DgnFile df = Session.Instance.GetActiveDgnFile();
    // to-do: delete model if it already exists

    DgnModelStatus error;
    ModelInfo mi = df.CreateNewModel(out error, modeName, DgnModelType.Normal, false, null).GetModelInfo();
    mi.IsAnnotationCell = true;
    mi.IsUseAnnotationScaleOn = true;
    mi.PropagateAnnotationScale = true;

Based on what I've been able to determine from other posts, this should be enough to set the model to place an annotation cell. What am I missing?

I also tried to create the model in C/C++. Basically the same thing - and same result.

	DgnModelP tmpMdl = CreateTemp2DDesignModel(m_assemblyTypeData[0]);
	DgnFileP dgnFileP = ISessionMgr::GetActiveDgnFile();
		
	mdlModelRef_setModelFlag(tmpMdl, MODELFLAG_IS_ANNOTATION_CELL | MODELFLAG_USE_ANNOTATION_SCALE, TRUE);

	// I thought above should be enough, but it was not. 
	// Attempted the following based on ModelExampleHelper.cpp
	// looks pretty much like c# - still fails to set the CanPlaceAsAnnotationCell to true
	DgnModelPtr dgnModelPtr = dgnFileP->LoadModelById(tmpMdl->GetModelId());
	ModelInfoPtr modelInfoPtr = dgnModelPtr->GetModelInfo().MakeCopy();
	modelInfoPtr->SetIsAnnotationCell(TRUE);
	modelInfoPtr->SetPropagateAnnotationScale(TRUE);
	modelInfoPtr->SetIsUseAnnotationScaleOn(TRUE);

I didn't give up - MVBA does what I want.

Sub TestCreateModel()
    Dim mdl As ModelReference, template As ModelReference
    
    On Error GoTo ERRORHANDLER
    Set template = ActiveDesignFile.DefaultModelReference
    Set mdl = ActiveDesignFile.Models.Add(template, "testmodel", "na", msdModelTypeNormal, False)
    
    mdl.CanBePlacedAsAnnotationCell = True
    Exit Sub
ERRORHANDLER:
    Debug.Print "Exception: " + Err.Description
End Sub

So, since MVBA worked, I have implemented the COM solution in C#.

    BCOM.ModelReference template = App.Context.ActiveDesignFile.DefaultModelReference;
    BCOM.ModelReference mdl = App.Context.ActiveDesignFile.Models.Add(template, modelName, "na", BCOM.MsdModelType.Normal, false);
    mdl.CanBePlacedAsAnnotationCell = true;

And this produces what I want. My concern - based on several CONNECT programming posts, COM is discouraged and MstnPlatformNet, DgnPlatformNet are encouraged. But, it works so I'll stick with it for now.

Please discuss.