I am really excited with the SS3 Civil product relese and has been waiting for it since beta testing. now I get an error when I start Inroads SS3:
Then I press Continue and software works OK I think. However I am afraid that this error would cause problems in latter works.
Anyone is struggling with the similar error?
I suspected you install InRoads SELECTseries 2 in the same machine.
Maybe you can try to edit this file …\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\system\load_inroads.cfg
You can remark (#) all the variables, except Load_InRoads_Ss2 = 1.
Load_InRoads_SS2 = 1
#Load_GeoPak_SS2 = 1
#Load_GeoPak_SS3 = 1
#Load_InRoads_SS3 = 1
Hope it helps.
Answer Verified By: Adam Wieczorek
Will this file "load_Inoads.cfg" be created by the SS3 installer?
since 1985: GIS, CAD, Engineering (Civil) Senior Consultant : [Autodesk Civil 3D , Esri ArcGIS, VertiGIS: in previous days : Bentley MS V4 - V8i, GeoGraphics, Bentley Map V8i, InRoads, HHK Geograf, IBr DAVID] : Dev: [C, C++, .NET, Java, SQL, FORTRAN, UML][direct quote by: http://en.wikipedia.org/wiki/Helmut_Schmidt]: "Wer Kritik übel nimmt, hat etwas zu verbergen"Wer Grammatik- und/oder Rechtschreibfehler findet, der darf sie behalten :-)
I created it for SS2 release by myself just to have a possibility to start InRoads from Application Menu in Microstation.
OpenRoads Designer 2022 (10.12) | OpenRail Designer 2022 (10.12)
I cannot seem to find the load_inroads.cfg file you are referring to. I do have SS2 and SS3 installed on my computer, and I'm wondering if this is something I shouldn't be doing, but Bentley staff encouraged having both versions running during the Bentley Learn Conference, so I assumed it was okay. I'm wondering if I need to install SS3 first and then SS2, maybe then I will find this load_inroads.cfg file.
I run both InRoads SS2 and SS3. I had SS2 installed prior to SS3.
load_inroads.cfg - you need to create this file on your own. It is a text file and AFAIK it tells Microstation which InRoads release is the main civil product and adds Application menu to Microstation interface.
My load_inroads.cfg file has just one line: Load_InRoads_SS3=1 and now I run mainly Inroads SS3.
With saying that I need to add that now I get similar error message when trying to run InRoads SS2. Hence when I need to go back to project made with SS2 I change line in my cfg file to: Load_InRoads_SS2=1
It is quite anoying and I am sure that there is a better way to run both ss2 and SS3 seamlessly.
I use AutoHotKey to make an Icon that when clicked, opens a little popup menu with a list of Bentley Programs to select to run. In the menu source, I have two items for MicroStation - one loads it with SS2 and one loads it with SS3.
However, in MBE (MicroStation Basic, not VBA) there was a function that can force MicroStation to read a specified CFG file when called. It might be possible to use that to load the CFG files live to get the desired result. I used it in my V7 workspace - I will see if I can locate it to share. I looked in the MBE help and did not see it, which now makes me wonder if I called an MDL function from within an MBE macro. Whatever the case, it would either work or not in V8 - I know I had it working in V7.
Here is my MBE Code. In the MDL API guide, it lists a VBA wrapper for mdlSystem_processCfgVarFile. There is no reason this cannot be used in VBA, except you can skip the part about writing a CFG file on the fly. You just need to force it to read one particular CFG file or another, on demand.
In my case, I needed to create variables in V7 but found no MBE function to do this. And also found the MDL function could (would) accept only fixed character strings as parameters to be passed to the funtion. (Well, at least I could not figure out a viable expression to allow me to pass a variable.) So after assigning certain "fixed" variables, I wrote a CFG file on the fly, used the wrapper function to read the CFG file and then deleted the CFG file.
'The next code items define config variables, but would not work if the strings were being
'passed as variables. These three are always the same so using fixed strings is OK here.
status = MbeCExpressionLong("mdlSystem_defineCfgVar(""_AB_Work"", ""work\\"", 4)")
status = MbeCExpressionLong("mdlSystem_defineCfgVar(""_AB_Survey"", ""Survey\\"", 4)")
status = MbeCExpressionLong("mdlSystem_defineCfgVar(""_AB_Field"", ""Field\\"", 4)")
'These variables need to vary which required a different solution. We found we could
'create a scratch CFG file and read it to assign any remaining variables.
Open "AB_TEMP.CFG" For Append Access Write Lock Read Write as #1
Print #1, "_AB_Proj_Name = " & us_AB_Proj_Name
Print #1, "_AB_Proj_Year = " & us_AB_Proj_Year
' MbeSendKeyin "DR=AB_TEMP.CFG" ' Uncomment if debugging is required. Allows one to View
' the CFG file if necessary.
' Use this mdl function to process the newly created scratch CFG file.
status = MbeCExpressionLong("mdlSystem_processCfgVarFile(""AB_TEMP.CFG"",4)")
' Delete the scratch CFG file as it has served its purpose
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration