ramooo Posted April 28, 2014 Share Posted April 28, 2014 Please help!! I am getting the "wall end caps" located in a very different elevation than its related wall. In a 3D view they show up as phantoms above my walls (see attached image). Does anyone have a clue about why I getting this weird behaviour? Quote Link to comment
Dieter @ DWorks Posted April 28, 2014 Share Posted April 28, 2014 I also have seen this from time to time, and it isn't a big deal as they will render just fine. It's just the wireframe that isn't correct. Quote Link to comment
michaelk Posted April 28, 2014 Share Posted April 28, 2014 Probably just a shot in the dark: Are your walls a very long way from the origin? mk Quote Link to comment
ramooo Posted April 28, 2014 Author Share Posted April 28, 2014 Well yes, it is only in wireframe but still very annoying because when I select a wall in a 3D view I get three objects selected instead of one (see the images). Although they only show up as phantoms I can easilly erase them by mistake. They are only 20 Mts away from the origin. Quote Link to comment
michaelk Posted April 28, 2014 Share Posted April 28, 2014 If you copy and paste the walls into a blank document, do they still misbehave? Quote Link to comment
ramooo Posted April 28, 2014 Author Share Posted April 28, 2014 They show fine copied in a blank document. Is it then a problem with the layer settings configuration? Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted April 28, 2014 Vectorworks, Inc Employee Share Posted April 28, 2014 Usually if it is a wireframe selection glitch like that, moving it into a new document just resets the highlighting. If it was a layer configuration problem, it would have been more than just the highlighting. Copying into a new doc is a good way to get away from possible corrupted or stuck objects, you can use this as a more automated way of regenerating files that are experiencing problems: http://kbase.vectorworks.net/questions/790/Layer+Import But sheet layers will need to be recreated. Quote Link to comment
ramooo Posted April 29, 2014 Author Share Posted April 29, 2014 Well guys, thanks for the answers. I have tried the import layers option without any luck. The problem was imported as well. Aparently only the copy paste procedure works. Any idea about why this happened? is it a bug? I would like to know what not to do. Quote Link to comment
michaelk Posted April 29, 2014 Share Posted April 29, 2014 I haven't seen this for a couple years. I thought it was gone. Back then I suspected it was a distance from origin issue. Jim - not to change the subject, but I've always wondered this: if ramooo was to take his original file with the bad wall caps and export it as VS and then take his new file with the pasted and good wall caps and export that file as VS, would running a diff reveal the problem? Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted May 8, 2014 Vectorworks, Inc Employee Share Posted May 8, 2014 (edited) Jim - not to change the subject, but I've always wondered this: if ramooo was to take his original file with the bad wall caps and export it as VS and then take his new file with the pasted and good wall caps and export that file as VS, would running a diff reveal the problem? I do not know enough about VS personally to answer that for sure. It can indeed be a distance from origin issue, but I have also seen it when files are converted between multiple versions. (In addition to happening for no discernible reason at all) Ramooo: Please send that file to the address in my signature and I can have a closer look. Edited May 8, 2014 by JimW Quote Link to comment
michaelk Posted May 16, 2014 Share Posted May 16, 2014 (edited) I do not know enough about VS personally to answer that for sure. It can indeed be a distance from origin issue, but I have also seen it when files are converted between multiple versions. (In addition to happening for no discernible reason at all) I just tried it on a file that was misbehaving. I did a layer import from the bad file to a blank file and it cleared up the problem. The exported VS files did show a bunch of differences. My VS skills aren't good enough to know what all the changes mean, but there are a bunch of setObjectVariableBoolean parameters that are different, among other things. mk Edited May 16, 2014 by michaelk Quote Link to comment
ramooo Posted January 14, 2015 Author Share Posted January 14, 2015 Hello Guys Its been a while since I have been suffering this issue and until now I realize that each end cap wall has it own properties apart from the ones of the wall itself. Well at least now I know that I can fix it by changing the height of each end cap (although it is boring process). This problem not only happens if I move the z position of a wall but also if I change the height of an entire layer. It seems like the walls move but the end caps remains in place. I would like to understand why the end caps have a separated height preference from its wall? or why they have separated properties at all?. Does any one know its utility ? I guess the issue is a bug. Does anyone know if it has been solved on 2015? Quote Link to comment
Benson Shaw Posted January 14, 2015 Share Posted January 14, 2015 ramooo - Do those wall caps move, but leave a phantom selection outline in the original location? I have seen some v2015 objects behave similarly. No experience with wall caps, though. The object moves but leaves a selection outline in the source location. Not sure of cause. Seems to be related to changing layer or story heights. Usually I can fix by Group then Ungroup the selection. Or shift selection to and from another layer. Or Cut then Paste in Place (dangerous!). The vectors need to be redefined in some way, then returned to orig status. The phantom selection outlines reassociate with their objects in the new location. I will try to find a predictable example. Best of luck with your end caps. -B Quote Link to comment
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.