Jason Walsh's Activities

Master of Upload

Sun, 04 Dec 2022 04:42:55 GMT

Upload 15 files, photos or videos to share with the community.

[MX V8i SS3] Haul mass analysis limitation

aleksander_zamorski — Tue, 13 Jan 2015 13:43:59 GMT

Hello,

I've encounter a bug or unknown to me limitation (no such info neither in "User manual" nor in "Command Language Reference"). When the number of point in haul analysis exceeds 1000 (10km with 10m step), a window appears with buggy information:

"MX Error E0097: Invalid string name specification"

Part of working input (1000 points):

HAUL,A1 QUANT,A1
070,1=MC10, ,3=VM00,4=10,5=426500,8=436490
071, ,2=VOLU, ,5=426500,8=436500
071
072,1=MC10,2=VM00,3=VH00, ,5=426500,8=436490
075
999

Part of not working input (1001 points)

HAUL,A1 QUANT,A1
070,1=MC10, ,3=VM00,4=10,5=426500,8=436500
071, ,2=VOLU, ,5=426500,8=436500
071
072,1=MC10,2=VM00,3=VH00, ,5=426500,8=436500
075
999

Is it right or something is wrong? I haven't used is before - spreadsheet did it ;)

Best regards
Aleksander Zamorski

ROUNDABOUTS SUPERELEVATION

Ikasten — Tue, 04 Nov 2014 16:32:26 GMT

I'm trying to create the superelevation of a roundabout.

I can create the Superelevation Section and Lanes.

But I can´t edit, import or assign the superelevation section because it´s not visible.

Any suggestions?

Thanks.

Popular File

Sat, 08 Jul 2017 14:21:35 GMT

One of your files is downloaded 50 times.

Too many elements for civil rule creation - impacts

John Lobbestael MDOT — Fri, 12 Dec 2014 02:52:13 GMT

When importing an alignment with General Geometry Import, from a .gpk, one of my advanced users is getting a message stating "Horzontal contains too many elements for civil rule creation." What does this mean and what are the impacts?

PowerGEOPAK SS3 - .722

Method for exchanging MX Drainage data with Watercom Drains

Grant Stewart — Fri, 12 Dec 2014 07:50:51 GMT

Since we lost our 12D drainage designer ,I have tried resurrecting MX Drainage to integrate road and drainage design. Our drainage engineer uses Watercom Drains and MX Drainage has menu options for both importing and exporting data to/from Drains.

However, the MX Drainage option uses an .mdb file, the Acesss database format now long discarded by both Watercom and Microsoft.

So to my questions:

Will Bentley update MX Drainage so that data exchange with current versions of Drains is possible?

Has anyone found a way to exchange data between MX Drainage and current versions of Drains (I know pipes can be transferred as CAD data, but have been advised pit information is lost)?

OpenRoads Corridor Parametric Constraints - Tables would make parametric constraints much more powerful and versatile

Michael-Lane — Thu, 02 Oct 2014 13:14:29 GMT

I have been working on migrating our office's corridor modeling workflows and processes to OpenRoads (PowerInroads SS3) for several months now. I love most everything about the approach Bentley has taken to corridor modeling, they really are setting the standard for the industry. There are some aspects that confuse me though. Like why are the parametric constraint objects so limited in nature (start sta, stop sta, start value, stop value)? Wouldn't it be great if you could define the parametric constraints in a table editor with a graphical preview similar to the super elevation diagram? You could streamline so many aspects of the corridor modeling process, it makes total sense to be able to define a parameter linearly for the length of the corridor (the same way you define super-elevations linearly for the length of the corridor). This will add another level of continuity to the corridor model that spans the length of the corridor. Does anyone agree??

Graphical Filters for Terrain Models

Jacquelyn Pettus — Tue, 25 Feb 2014 05:13:42 GMT

The Graphical filters for terrain models can be saved as dgnlib and can be used to create terrain models for other projects as well. The configuration variable that defines the terrain model filters DGN library is

CIVIL_CIVILTMDGNLIBLIST

Following are the steps :

1. Create a dgnlib that contains terrain graphical filters.

2. From the Microstation menu select "WorkSpace > Configuration".

3. Hit the "New" button.

4. In the variable field enter the above variable

CIVIL_CIVILTMDGNLIBLIST

5. In the value field give the location of the dgnlib file, say, the dgnlib is placed in the folder named 'DGNLIB'

C:\ProgramData\Bentley\MX V8i (SELECTseries 3)\WorkSpace\Projects\Examples\Bentley-Civil-Metric\dgnlib\*.dgnlib

Hit OK. Click 'Yes' to save the changes.

6. You will need to restart MX so that the changes are applied.

The dgnlib will then be listed in 'Project Explorer > Civil Standards tab >Filters'.

Do let us know.

Slope direction pattern from corridor

smileyours — Thu, 05 Feb 2015 15:48:35 GMT

Can i somehow generate a slope direction pattern on the slopes i create in my corridor?

I'm using PowerCivil V8i (SS3)

Export Civil Geometry to MX - Halgn,Valgn and Verat Linemode

Jason Walsh — Tue, 03 Feb 2015 15:22:57 GMT

Product(s):	MXRoad
	Version(s):	08.11.09.674,08.11.09.722,08.11.09.788
	Environment:	N/A
	Area:	Geometry
	Subarea:	Export to Native

The respective M & G Strings are automatically created in conjunction with the corresponding linemode for horizontal (Halgn) and vertical (Valgn / Verat).
The linemode files (Halgn,Valgn and Verat) are created in ..\mxdata folder. These input files can then be incorporated back into the existing input file process.

How to use Associate MX Strings function

Jason Walsh — Tue, 03 Feb 2015 15:13:23 GMT

	Products(s):	MXRoad
	Version(s):	08.11.09.674,08.11.09.722,08.11.09.788
	Environment:	N/a
	Area:	Geometry
	Subarea:	Export to Native
	Original Author:	Jason Walsh, Bentley Technical Support Group

Background

In MX v8i SS3 and SS4 the Feature definition toolbar has a function called Associate MX Strings as below.

Associate MX Strings allows the projection of points from a reference onto adjacent strings. This ensure that the all the base elements points are included and align as would normally occur when using MX Design options.

Steps to Accomplish

Export the required OpenRoads elements to an MX model using Export to Native function.
Select the Associate MX Strings and select the OpenRoads feature element/elements that are the MX feature strings, the prompt will say Select a MX String, Right click when you have selected the required OpenRoads feature elements to continue.
The prompt will now say Select a Master String, select the OpenRoads feature element that is the MX master string.
Export the OpenRoads elements again to the MX model to update the MX strings.
When you interogiate the updated MX Strings they will now have the projected points.

Input files and ProjectWise

gregeden — Fri, 23 Jan 2015 11:33:56 GMT

Is there a way by which recently used input files managed in ProjectWise can appear in the list of recently used files in MXROAD? It is rather tedious to have to click through to the folder on PW every time I want to run the file, and running the file through the PW Integration feature doesn't run an open file, only the last saved version, even though the file is checked out.

[MX V8i SS3] Interface - changing width of mid-element

aleksander_zamorski — Fri, 16 Jan 2015 12:31:16 GMT

Hello Community :)

I've created an interface input with changing width of one of a middle element from 5.0 to 1.0 [m].
MX says "Invalid combination of data fields". Where have I mistaken? Below part of input:

INTERFAC,MAP TRIA,A1 SLOPES
259,INTI
260,1=MC10,2=IW10,3=IX10,4=-12,5=416495,8=418000
261,1=IGN ,2=ES11,3=RP10,4=5,5=0.50,6=,7=-0.46
261,1=IGN ,2=RP10,3=RU10,4=5,5=0.50,6=,7=-0.14
261,1=IGN ,2=RU10,3=RP11,4=5,5=0.50,6=,7=+0.14
261,1=IGN ,2=RP11,3=IA10,4=5,5=0.50,6=,7=+0.46
261,1=IGN ,2=IA10,3=IA11,4=5,5=5.00,6=,7=+0.05
261,1=TX00,2=IA11,3= ,4=5,5= ,6=,7=+0.66667
262,1=TX00,2=ES11,3= ,4=5,5= ,6=,7=-0.66667

260,1=MC10,2=IW10,3=IX10,4=-12,5=418000,8=418100
261,1=IGN ,2=ES11,3=RP10,4=5,5=0.50,6=,7=-0.46
261,1=IGN ,2=RP10,3=RU10,4=5,5=0.50,6=,7=-0.14
261,1=IGN ,2=RU10,3=RP11,4=5,5=0.50,6=,7=+0.14
261,1=IGN ,2=RP11,3=IA10,4=5,5=0.50,6=,7=+0.46
261,1=IGN ,2=IA10,3=IA11,4=5,5=5.00,6=,7=+0.05 ,9=1.00,10=+0.05
261,1=TX00,2=IA11,3= ,4=5,5= ,6=,7=+0.66667
262,1=TX00,2=ES11,3= ,4=5,5= ,6=,7=-0.66667

260,1=MC10,2=IW10,3=IX10,4=-12,5=418100,8=442505
261,1=IGN ,2=ES11,3=RP10,4=5,5=0.50,6=,7=-0.46
261,1=IGN ,2=RP10,3=RU10,4=5,5=0.50,6=,7=-0.14
261,1=IGN ,2=RU10,3=RP11,4=5,5=0.50,6=,7=+0.14
261,1=IGN ,2=RP11,3=IA10,4=5,5=0.50,6=,7=+0.46
261,1=IGN ,2=IA10,3=IA11,4=5,5=1.00,6=,7=+0.05
261,1=TX00,2=IA11,3= ,4=5,5= ,6=,7=+0.66667
262,1=TX00,2=ES11,3= ,4=5,5= ,6=,7=-0.66667
263

Best regards
Aleksander Zamorski

[MX] Unpredictable behavior of EDIT,026

aleksander_zamorski — Wed, 21 Jan 2015 20:51:05 GMT

Hello,

I've encounter very strange, very annoying and unpredictable behavior of simple EDIT,026.
I've just wanted to insert a points on string from intersection of normal from another string.
On one part it works fine but on other part the points are in random positions (screenshot below).
In attachment models and input - any ideas what is wrong?

Best regards
Aleksander Zamorski

communities.bentley.com/.../MODELS.TXT communities.bentley.com/.../INPUT.INP

Cross-section macro

Dave Chester — Mon, 19 Jan 2015 21:48:56 GMT

Hey,

I am currently developing a macro to draw cross-sections to the company standard with MX SS3. I haver coded it separately to make sure it displayed how I wanted it to and this works well. Then I converted it into a macro.

However, i can't process the macro and it seems to be having trouble with Format - Option section (see below example)

FORMAT
F3.0,2A4,F4.0,F8.3,2F10.3,F8.3,2F10.3,F8.3
OPTION

I have uploaded the Genio file of the design and ground model, Macro and Cross-section input file to the secure file upload.

There could be other issues i am not aware of with my macro. As I am new to writing macros any help would be much appreciated.

Regards,

Dave

Jason Walsh's Activities

Master of Upload

[MX V8i SS3] Haul mass analysis limitation

ROUNDABOUTS SUPERELEVATION

Popular File

Too many elements for civil rule creation - impacts

Method for exchanging MX Drainage data with Watercom Drains

OpenRoads Corridor Parametric Constraints - Tables would make parametric constraints much more powerful and versatile

Graphical Filters for Terrain Models

Slope direction pattern from corridor

Export Civil Geometry to MX - Halgn,Valgn and Verat Linemode

See Also

How to use Associate MX Strings function

Steps to Accomplish

See Also

Input files and ProjectWise

[MX V8i SS3] Interface - changing width of mid-element

[MX] Unpredictable behavior of EDIT,026

Cross-section macro