VW-PAD-Bristol-2014

+1

Just a quick update, I reinstalled Vectorworks with SP4 and I tried to publish the same sheets from the same document and the same thing happened again. The vectorworks 2017.exe deletes it's self. I have just done another reinstall with SP3 and preformed the same commands and it has worked fine. I will also say that I had our IT consultant run a check on the computer to see if there was an operational problem with my PC but nothing was found. Hope this helps

Hi All, I have just had a strange thing happen to my Vectorworks This morning I installed SP4 and this afternoon VW crashed while publishing images (with no notification or request to submit a report) Now it appears it has deleted it's run file and I can not open vectorworks. I am currently going through a re-install. (Huff) Has anybody else had any issues? Many Thanks

Same here, This would be a great feature if it was possible.

Hello, A few weeks back I Posted this in the Architect forum, Pat had a look at it and found that it was a Vectorworks problem, Any idea if a solution has been found? We have a custom title block for our company and it has worked great until now. For some reason the Issue data no longer lines up when there is more than one line in the :iNote. Previously we had :iNo, :iAppr and :iDate aligned vertically se to top and :iNote set to bottom. this worked great the note worked up to the top of the rest. Now it doesn't seem to read the issue data as a group of data, just as individual text boxes. Which means if there is more than one line of text in the :iNote we get an offset between the lines. I have attached the before and after screen grabs for reference. If anybody know a reason why this might be happening it would be great to hear from you. Many Thanks James By the way I have tried making a brand new symbol that hasn't been converted from VW2016 and it still seems to be happening. pad-VW 2017 Titlte Block Issue.vwx

Good Morning All, We have the same issue I our office, it is completely random and hard to replicate. It has happened on a few computers (4/5 out of 12), if we tab between VW windows we can see the new documents but all the commands are happening in the we have changed from. It can happen if we have two docs open or four or five, I can not seem to replicate why it happens. I have even closed and reopened the documents I had open in the same order and it work the second time. The only solution we can find at the moment is to shut VW down and restart Unlike Tom we haven't updated any of our systems apart from installing VW2017 We are using Window 7 Professional. Any ideas? Thanks

Hi JMW, Thanks for this. We also found that changing the "navigation graphics" in the display tab of Vectorworks preferences to "good performance and compatibility" seems to work too. Just another work around.

Hi Kim, We were having something similar happen to some of our viewports. We were told to change our settings in Tools>Options>Vectorworks Preferences, then under Display, set the Navigation Graphics to Good This seemed to help. Hope it helps for you too.

Thank you for this Pat, Very help as always.

Thank You Pat, Title Block attached Regards James pad-VW 2017 Titlte Block Issue.vwx

Hello, I have another issue today. We have a custom title block for our company and it has worked great until now. For some reason the Issue data no longer lines up when there is more than one line in the :iNote. Previously we had :iNo, :iAppr and :iDate aligned vertically se to top and :iNote set to bottom. this worked great the note worked up to the top of the rest. Now it doesn't seem to read the issue data as a group of data, just as individual text boxes. Which means if there is more than one line of text in the :iNote we get an offset between the lines. I have attached the before and after screen grabs for reference. If anybody know a reason why this might be happening it would be great to hear from you. Many Thanks James By the way I have tried making a brand new symbol that hasn't been converted from VW2016 and it still seems to be happening.

Hello, I was wondering whether anybody else has been having issues with design layer/reference viewports after converting 2016 to 2017. We have a set of drawings where the crop is not working. As we zoom in we can see the other objects outside of the crop. (see screen grab) This happens whether we are using the existing crop or a new crop. I have tried using different classes etc.. but this doesn't seem to help. If you have any ideas it would be gratefully appreciated. Many Thanks James

Hello, I have another issue today. We have a custom title block for our company and it has worked great until now. For some reason the Issue data no longer lines up when there is more than one line in the :iNote. Previously we had :iNo, :iAppr and :iDate aligned vertically se to top and :iNote set to bottom. this worked great the note worked up to the top of the rest. Now it doesn't seem to read the issue data as a group of data, just as individual text boxes. Which means if there is more than one line of text in the :iNote we get an offset between the lines. I have attached the before and after screen grabs for reference. If anybody know a reason why this might be happening it would be great to hear from you. Many Thanks James By the way I have tried making a brand new symbol that hasn't been converted from VW2016 and it still seems to be happening.

Hello, I was wondering whether anybody else has been having issues with design layer/reference viewports after converting 2016 to 2017. We have a set of drawings where the crop is not working. As we zoom in we can see the other objects outside of the crop. (see screen grab) This happens whether we are using the existing crop or a new crop. I have tried using different classes etc.. but this doesn't seem to help. If you have any ideas it would be gratefully appreciated. Many Thanks James

Thank you for your help. It sounds like we go through the same process as the suggestions. Import then using the wand selecting the by line weight and setting those lines to class thickness. Thank you for the tip of importing to the page scale to avoid the marker conflict.