Hi,
We are having an issue when inserting steel beams / columns / railings from the catalog. They come in at the wrong scale - they are coming in at 100x smaller than the dimensions of the item. For example, a 400x200 RHS comes in 2mm wide. The walls, doors, windows, ducts etc are not affected and come in at the correct size. An image is attached showing the difference.
The issue happens only on certain files which have been created from a seed file. The seed was updated a week ago when the issue first started so we believe it may be an issue that was created then. The issue only happens on certain PCs when using this seed file. Some PCs have the issue intermittently, with no clear pattern to what we are fixing to resolve it. We can amend the seed file settings - but don't want to replace it completely.
We have a Workset set up on a Network Drive where the catalog is stored, which should be shared across all PCs we're testing.
Are there any configuration settings / file specific settings we should be reviewing to resolve this?
AECOsim Connect Version Edition Update 4 - Version 10.04.00.69
Greg,
Is 400x200 RHS a custom section profile or is it from one of the delivered section profile xml files in the dataset?
The other elements being placed in the correct size, it would also be worth checking if the member sizes are correctly defined in the section profile xml file being used.
Best Regards,
RJ.
Raguram, this was one of the delivered Section profiles in the dataset. I did have a browse to, what I believe was the correct, xml file and spot checked a few of the properties (including the one we were inserted) - everything looked as it should with the correct member sizes defined.
Thanks for the update., Greg.
Glad, you got it resolved.
Raguram, will you raise a Sr to get this fixed? The structural member sizes should not be affected by the Annotation Scale setting. Or is the coder already following this thread?
Dominic,
In my test cases, for a dgn file created from default seed file, the section sizes remain the same during the placement, even when the annotation scale is changed. I am assuming this is a setting that got modified in the seed file being used and our support team would be able to assist, if the seed files are shared via an SR.
dominic SEAH said: Or is the coder already following this thread?
Yes, our teams are following every thread.
Hopefully, Greg will submit an SR, then.
In any case, could you ask the coder to confirm which bit of the dataset gets queried when OBD places the structural objects, please?
It would be good to get a list together to avoid future hiccups.