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
We have been experiencing similar problems with the 'Place Wall' tool.
It seems that as soon as we create a new wall assembly the .xml file gets corrupted and returns an exception error causing the program to shut down.
We keep getting the appended error message.
I have filed two SR's for this but to date still have no resolution
We have been compelled to stop all new projects on AECOsim and revert back to BA
Incredibly frustrating
Rob: no resolution, and I have received no info on the SR I filled almost 4 weeks ago. none too thrilled
This may be unrelated, but I discovered when I was customising the frames path in our company dataset that if one of the paths was invalid then the tool wouldn't work and threw a 'Command cannot be completed' in the message centre.
This was despite the GB dataset and project dataset paths being valid - one invalid path breaks the tool seems like a bad way of doing things.
I'll have a go at breaking my parts and datagroupsystem in the same way as the frames to see if there is a similar effect.
As I said before, choices appear to have been made in the way the configuration works that make things very sensitive.