Anyone have any idea why TFWALLS would not load (or be allowed to load) in a custom AECOSim workspace...obviously I've missed some variable, but I don't see it.
Thoughts are appreciated.
this is preventing an implementation, and not allowing walls and other items to be placed at all. Help!
Thanks,
Shawn
------------
Sean,
Did you get to the bottom of this.
I'm gradually getting to the bottom of our customized config but feel is that the configuration is much more complex and also more fragile.
Its also frustrating that a lot of variables appear to be repeated in either a BB a TF or a ATF context with no real evidence of which to use, whether they are interchangeable etc.
Rob
I will give it a go tomorrow. Thank you
I'm going to trial an install tonight on a sacrificial box - I'll keep you posted on the results.
Well I have no problems with what I would call a highly customized system here.
I owe a debug, I'll get that up soon. New job, so not a lot of time.
We'll try the .325 as well.
If anything, I would recommend .376.
All
I have just installed 376 + GB Dataset +1 and redirected my workspace to the S: drive. Updated all AECOSim folders in the workspace, plus the project.
I still get this TFWALLS unloaded.
If I run the Verify config all is OK.
I have attached the msbebug for you to look at.
If anyone is out there a quick turn around will be most appreciated.
Ian
Working with Carl Myhill in Bentley Support UK. We found this issue is related to the VAR ;
MS_DGNAPPS = synchbylevel.ma
If this is set within the Standards.cfg file the AECOsim tools stop working and you get the TFWALL not loading etc.
If you remove or comment out this line AECOsim works OK.
Working deeper to find a solution, I have found the following:
The above VAR is useful as it resets the Active colour, Line style etc to that of the active level i.e. ByLevel.
To overcome this issue change the VAR to :
MS_DGNAPPS < synchbylevel.ma
HTH
Interesting... thanks for working through the issue with Carl, Ian.
and that did it...how an 'append' vs. an 'equals' vs. a 'prepend' affects things is wonderous...
We had SynchByLevel as an "append"