Getting a bit fed up at the moment because I spend hours and hours of bug hunting in Aecosim...
There have been numerous discussions on communities about Bentleys inability to provide proper support for costumers outside the US. In addition there I do have a bunch of Service Requests that are not reproduceable by Bentley staff, because they just test against US dataset.In my opinion the core problem of the whole thing is that BuildingDesigner.cfg has this definition.TF_DATASETNAME : Dataset_USThis should be changed to a metric dataset instead.
SR 7000185460 filed.
I have a long time wish to go one step further - a pure ISO install!
No feet or inches anywhere in the software.
regards / Thomas Voghera
So one thing you could try is this:
In C:\Program Files (x86)\Bentley\AECOsimBuildingDesigner V8i Ss5\AECOsimBuildingDesigner\config\appl
create a file ZZ_DefaultDataset.cfg
it needs to contain the line TF_DATASETNAME = Dataset_NM (or whichever dataset you are using)
However I don't think that really has any effect that would not be applied by setting the same value at the project level because the default value in BuildingDesigner.cfg of TF_DATASETNAME : Dataset_US is a 'use this unless re-defined later' statement.
The product is delivered with the US dataset to provide a working and testable out of the box installation.
Setting TF_DATASETNAME = <regional dataset name> has the same effect as a hypothetical product only installation followed by the regional dataset installation (or a hypothetical product plus metric dataset installer), the US dataset is ignored.
The current design is intended to use the TF_DATASETNAME value in the project configuration file.
Marc
Sorry, but you are breaking the #1 rule in Microstation configuration.
Never make any changes to the Aecosim installation folders!
I have at least 2 issues at the moment where Bentley support is unable to copy the behaviour, and I have no idea why, as we run default installation (for these testing purposes).
What I really don't like (to say it mildly) is, that there are some predefined settings against an US-dataset. Even if we do define TF_DATASETNAME or other variables, I can never be sure that there isn't something which doesn't point to something strange. And US-values are the least we want to have.
All default values should be ISO.
I think it must be done 'earlier' in the install process than the dataset. Even with the Swedish dataset I get dimensions with feet.
Thomas, In a case where you get imperial dimensions, and I'm assuming they are in an imperial dimension style, if you open the Dimension Styles dialog (where that style should be listed) does hovering the cursor over the style show the location?
Andreas, I'm not changing the installation folder structure or their contents, just adding one new file to change a key variable (just the one in this instance as a test).
The effect is the same as configuring a shortcut but does not rely upon the correct shortcut being used, the configuration is applied whichever way you start AECOsim (which may be seen as a good or a bad thing depending on your situation).
The problem is not that I am not able to change a variable, however I appreciate that you gave a solution to this issue as well.
My issue is that the default - or fallback situation should not be US with imperial settings.
There are many ISO standards, do you have a particular ISO standard in mind and can you tell me how you see this solves the issue at hand. Most ISO standards that support building support both imperial and metric units.