Weird thing started to happen in one of my Client builds. Went to place handrail and I get an error:
Error: Unable to create Railing. Please load section file.
Section and rail files are the same in several builds and the others are working.
Section files are all configured and loading fine, just won't place handrail.
Anyone come across this before?
Have you tried to remap the US.xml file using STRUCTURAL_SHAPES configuration variable ?
I'm actually using the onesteel file for AUS sections. It's in the STRUCTURAL_SHAPES config and appears fine in the modelling tools.
Config Explorer falls over with my custom config. I'm using Beyond Compare to see the differences between the working and problem build. I'm also using it to compare against an old version of the build which is still working. Just trying to find time to do it all.
Sounds like a plan. Definitely let us know if you find anything....
Bear, one thing if you haven't tried already, open Section File Manager (keyin: TFSECMGR DIALOG) to see what section files are actually loaded in your session.
Thought about that, all good:
OK, still completely confused with this one, but I've at least narrowed it down to trying to use any off the cell libraries. If I change back to Structural Sections, all good. If I use Cells or Profiles then I start to get the error, But only with this one Client build. If I load any of the other Client builds, all the same .cel files, and they work fine.
I should also say the issue seems to be with the Posts.
Fixed it, added the .cel files to MS_CELLLIST. All works now???????
So, on the builds where the railings were already working as-is, what folders did MS_CELLIST point to and what was in those folders?
The issue I had with this one was that a BHP build update changed the MS_CELLIST variable. It was the last thing I would have thought was the issue with all the other custom variables, but there you go. In the other builds the Client variables appended to the list rather then trying to reset the list. It's part of the issue i have with the BHP build in general as they usually cut access and use to all cell libraries other than those approved by BHP. Not ideal when we have additions in the 3D build, but lesson learnt.
Still, the error gave me NO indication that this was the problem. One for the memory bank. I'll need to test it on CE as well.