_James Posted June 14, 2019 Share Posted June 14, 2019 We're running VW2019 SP3 and when we publish a batch of drawings directly to print, the order goes awry. Instead of drawings 1,2,3,4 etc. it goes 1,3,2,5,11,22,4 etc. - incredibly frustrating! It even does this when printing two sided which completely ruins the set, at least with single sided you can rearrange. Is there any reason why this seems to happen and a potential fix other than exporting to PDF and then printing the PDF? Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted June 14, 2019 Vectorworks, Inc Employee Share Posted June 14, 2019 Hello @_James, Could you make a screen recording showing the steps to reproduce this? Thanks, Nikolay Zhelyazkov Quote Link to comment
Pat Stanford Posted June 14, 2019 Share Posted June 14, 2019 The order you are stating sounds strange, but that definitely sounds like a Text sorting versus Numeric sorting problem. The field you are using is probably stored as Text. That way if you need sheet 3A you can have it rather than just numbers. But when you have a Text field it sorts using alphabetic (ASCII) sorting rather than numeric. So it sorts by the first character, then by the second character, then the third, etc. So you get something like: 1, 10, 11, 2, 3, 4, 47, 48, 5 .... The traditional work around for this is to use leading zeros so that all of the numbers are the same number of characters. 01, 02, 03, 04, 05, 10, 11, 47, 48. If you need more than 99 sheet you need to pad to 3 characters, 001, 002, 010, 011, etc. But send Nikolay a movie anyway so he can make sure there is not another bug hiding here. 1 Quote Link to comment
_James Posted June 14, 2019 Author Share Posted June 14, 2019 The numbers I used were just indicative, in reality we use 3 digits, (100s for planning, 200s for demolitions/site, 300s for general arrangements etc) so the numbers were late 290s and then into 300s - there were no letters (although we do occasionally do a 330 and 330a for example). The order was something like 298, 303, 299, 320, 350, when it should have been 298, 299, 300, 301, 302, 303, 310, 311, 312, 313, 320. We have the jumps because we'll do 300-309 for plans, then 310-319 for 4 elevations, 320-329 for sections, 330-339 for M&E etc, and there aren't always enough storeys/sheets to fill take up all the numbers, but doing it in multiples of 10s gives us some flexibility if things are added - perhaps this causes problems? . It was still printing as I wrote the post, but the strangest thing was that it duplicated the same sheet (350) about 5-10 times before I stopped it. I'll upload a movie a bit later but thanks for your replies. Quote Link to comment
_James Posted June 17, 2019 Author Share Posted June 17, 2019 (edited) @Nikolay Zhelyazkov here's the recording - hopefully it will shed some light on it. Publish Error.mov Edited June 17, 2019 by _James Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted June 17, 2019 Vectorworks, Inc Employee Share Posted June 17, 2019 Hello @_James, The first thing that caught my eye was that your naming scheme is messed up. How did you create it? Make sure to use the popup for inserting new formulas and add your custom text only between 2 formulas and not in a single formula, which will result in invalid formula. Try printing with one of the default naming schemes and let me know if you still get messed up order. Thanks, Nikolay Zhelyazkov Quote Link to comment
_James Posted June 17, 2019 Author Share Posted June 17, 2019 @Nikolay Zhelyazkov I think this was just me messing around showing some colleagues how you can do this now as they were saying how great it would be if Vectorworks could do this before we upgraded. Will try to see if this affects things - but nothing strikes you as odd how we do things otherwise? Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted June 17, 2019 Vectorworks, Inc Employee Share Posted June 17, 2019 2 minutes ago, _James said: Will try to see if this affects things - but nothing strikes you as odd how we do things otherwise? - At least to me, everything seems normal. Quote Link to comment
_James Posted June 25, 2019 Author Share Posted June 25, 2019 @Nikolay Zhelyazkov An update to this - not only did publish to print mess the order up, but it was incredibly slow to print. It would pause for minutes (not exaggerating) between sheets. It would take over an hour to print around 70 sheets - this was from a project sharing file. We have since converted the file (for an unrelated reason) to a normal .vwx file rather than .vwxw/.vwxp and the print speed is significantly better. There is no wait between sheets, and the set just prints out as expected. Any idea what's causing this and if it can be remedied? If you would like a copy of the files please let me know. Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted June 25, 2019 Vectorworks, Inc Employee Share Posted June 25, 2019 @_James, a copy of the files would be nice. If I am not able to reproduce this I can only assume what is going wrong. Quote Link to comment
_James Posted June 25, 2019 Author Share Posted June 25, 2019 @Nikolay Zhelyazkov I've sent them via message - thanks for your help. 1 Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted June 25, 2019 Vectorworks, Inc Employee Share Posted June 25, 2019 @_James Thanks for the files. 🙂 I will have to spend some time investigating this. I will let you know here if I have any progress. 1 Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted July 15, 2019 Vectorworks, Inc Employee Share Posted July 15, 2019 Hello @_James, I have looked into this for some time. I have noticed that you have a field in Sheet Data that has empty name, which is causing the naming schemes to be messed up (I think I did not see this before). Could you try deleting this field and then printing and tell me if you still have problems? Best Regards, Nikolay Zhelyazkov Quote Link to comment
_James Posted July 31, 2019 Author Share Posted July 31, 2019 Hi @Nikolay Zhelyazkov On a quick test this seems to have solved it. I think the trouble comes from merging the two records and a lot of useless data being carried over. Thanks for all your help on this. 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.