I have been using referenced DLVPs to 'import' building models from individual source files into a main site model file. I think I always find that something gets lost in translation but can generally get around it somehow. For example I've found that certain Roof components often decide to ignore their offsets + in the target file I'll notice that the rafter component is projecting out beyond the building edge instead of being contained within it. In such a case I can just make the rafter class invisible + unless I'm wanting to take a section through the building can live with this. However today I am finding that in the DLVP in the target file my wall clipping is being ignored + some of my doors aren't displaying properly.
The original model in the source file:
The model as displayed as a referenced DLVP in the site model file:
I will send this to Tech Support or file a bug but I just wondered what other people's experiences were? I know others have recommended using Layer Import Referencing instead of referenced DLVPs + this is what I'm going to try now, but the reasons in that discussion were more to do with being able to more easily control layer/class visibility rather than geometry being mistranslated. Are there any tricks to prevent this happening or do I just give up on DLVPs + move over to Layer Import Referencing instead + hope that works better?
Actually as I write this I think I remember what I describe above happening in another file + the way I got around it was to create duplicate walls layers in the source file where I manually brought the height of the walls down below the roof level so that they looked correct in external views (but not in section views) + treated these as special 'DLVP' layers that I only turned on in the site model file. Bit of a faff though. And doesn't help me with the doors which are rendering white. These particular doors use a custom leaf symbol so it must be something to do with that. The other doors which just use a standard leaf created within the tool display fine.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Tom W.
I have been using referenced DLVPs to 'import' building models from individual source files into a main site model file. I think I always find that something gets lost in translation but can generally get around it somehow. For example I've found that certain Roof components often decide to ignore their offsets + in the target file I'll notice that the rafter component is projecting out beyond the building edge instead of being contained within it. In such a case I can just make the rafter class invisible + unless I'm wanting to take a section through the building can live with this. However today I am finding that in the DLVP in the target file my wall clipping is being ignored + some of my doors aren't displaying properly.
The original model in the source file:
The model as displayed as a referenced DLVP in the site model file:
I will send this to Tech Support or file a bug but I just wondered what other people's experiences were? I know others have recommended using Layer Import Referencing instead of referenced DLVPs + this is what I'm going to try now, but the reasons in that discussion were more to do with being able to more easily control layer/class visibility rather than geometry being mistranslated. Are there any tricks to prevent this happening or do I just give up on DLVPs + move over to Layer Import Referencing instead + hope that works better?
Actually as I write this I think I remember what I describe above happening in another file + the way I got around it was to create duplicate walls layers in the source file where I manually brought the height of the walls down below the roof level so that they looked correct in external views (but not in section views) + treated these as special 'DLVP' layers that I only turned on in the site model file. Bit of a faff though. And doesn't help me with the doors which are rendering white. These particular doors use a custom leaf symbol so it must be something to do with that. The other doors which just use a standard leaf created within the tool display fine.
Bit annoying...
Link to comment
13 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.