Jump to content

LarryO

Member
  • Posts

    236
  • Joined

  • Last visited

Reputation

27 Great

Personal Information

  • Location
    Victoria BC Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Start first by asking yourself if the effort is worth in time and or money savings to pay yourself to learn Pascal, Python or C++ or to hire someone to script for you. If yes, identify / document what type of interaction you hope for when first creating the object, the basics of how and what you expect when editing a point. Select the best predefined plugin object to suit the profile you just documented. Then just start coding. You can start by mimicking the steps you would you would do if you were manually creating the object. Adding in the variables to store values and locations as you go. Take a look at some other coding work to get a feel for some conformity in the writing structure of your code so it remains easy to follow afterwards. Invariably you will want to tweak and correct the functionality of how you interact with your object and other aspects. Inquire in the Vectorscript area if you are willing to take the plunge in learning scripting. Good luck and don't be afraid to share your mistakes.
  2. Arrgh, Thanks Matt for find that. It was a bad day VWs crashed to desktop three times that day while working in that file.
  3. I was able to reduce the file size while retaining the rendering error for anyone capable of hunting down this bug causing these dimensional errors. File attached. (edit: error is still present in today's SP4 602791 update) VP RENDERING INCORRECT OBJECT SIZE.vwx My bad, I forgot these needed to posted here in trouble shooting. Please delete the double posting over in general if not applicable. Thanks.
  4. The size of the HSS in section B-B is as labeled using the 3d square tubing. 1. BUT when rendered in the section viewport it is only 74mm as evidenced by the sectioned tubing being slightly larger when they are all the same size. I had to fake the vertical dimensions. 2. Also the solid line parallel to the bottom edge should not be there. The smoothing angle is set to 5°. These lines appear unpredictably in part or whole from radial point(s) along an extrusion when said solids have been operated upon by one of the 3d modelling tools (add, subtract, section, etc.). VW Mod8402 Custom's House - roof hatch frames in ventilation shaft.pdfel file is 12.8MB8402 Custom's House - roof hatch frames in ventilation shaft.pdf 855.12 kB · 8 downloads
  5. My bad, I forgot that these need to be posted to the trouble shooting forum. (edit: please move this posting to Trouble Shooting if applicable, Thanks.)
  6. Has the forum ( and Nemetschek/Vectorworks) simply stopped elevating problems to the known issues part of the forum? If we don't acknowledge it, it doesn't exist premise! (Just like politics.) Nothing new was elevated throughout all of 2020. (unless the site's sort feature is broken) In working more with 3d elements and viewports in VW2019 and VW2021 I have had more crashes to desktop (CTD) this year than the past 5 years. Somewhat reminiscent of the MiniCad 4 days. Now this could partially be due to switching to the Windows platform and its frustrating implementation of palettes which prevent the keyboard shortcuts from being activated unless escape is pressed first. But I find with my mouse (Razer if that's a factor) that selecting buttons in the info palette, the layer button in the titlebar and a few others are causing crashes to desktop. Today it seemed like a keyboard shortcut triggered CTD. In addition, the inability to select the note text of an exploded dimension remains as a bug. Rendering viewports are having multiple issues with lines that should and shouldn't be displaying. This week I had an object in a section viewport that was drawn incorrect and therefore dimensioned incorrectly. Fixed, not a bug.
  7. This would depend upon how you have implemented your titleblocks. I our company's instance we have a symbol with editable fields installed by our plugin. We simply edit that symbol and the new logo will appear relative to the symbol's origin. Our pages have different borders depending upon size of page but the actual titleblock size and its orientation remains the same. This fixed symbol size helps when working with other applications such as Bluebeam that look for page numbers and other identifying features based upon location in the document set relative to the page corner or origin.
  8. I was able to reduce the file size while retaining the rendering error for anyone capable of hunting down this bug causing these dimensional errors. File attached. (edit: error is still present in today's SP4 602791 update) VP RENDERING INCORRECT OBJECT SIZE.vwx
  9. 8402 Custom's House - roof hatch frames in ventilation shaft.pdf The size of the HSS in section B-B is as labeled using the 3d square tubing. 1. BUT when rendered in the section viewport it is only 74mm as evidenced by the sectioned tubing being slightly larger when they are all the same size. I had to fake the vertical dimensions. 2. Also the solid line parallel to the bottom edge should not be there. The smoothing angle is set to 5°. These lines appear unpredictably in part or whole from radial point(s) along an extrusion when said solids have been operated upon by one of the 3d modelling tools (add, subtract, section, etc.). VW Model file is 12.8MB
  10. Illustrator has the ability to open Autocad's dwg format directly without the use of Autocad as an intermediary. My suspicion would lie in either Illustrator not supporting a certain type of curve or spline or the accuracy of the file is too low. Or the exported dwg file had insufficient accuracy for the units involved. The first can usually be addressed by exporting to version 12 of autocad's dwg. The second by using six decimal places of accuracy when the units are inches or one decimal place if they are millimetres.
  11. Bluebeam's pdf viewer may save the state of the on off layers. It saves the last page viewed when closing a document. But of course it will not trim the fat of the file like that print to pdf printer can.
  12. The list was not populated with anything when I opened it, but I think I may have observed from your photo why that was so. I think that I may have been in the annotation space with the drawing label selected rather than selecting it's parent viewport. I was attempting to get HB02 show in the bottom half of the drawing tag of the section viewport on page 03. I'll have to look at this one again when I'm back at the shop.
  13. Can you explain this more? The viewport name when created and the selection to use drawing number/sheet number is selected names the viewport in the manner expected example: 1/HB02 Now if I want to change that drawing number assigned to the viewport, I select the viewport and in the object info palette change the drawing number to 5 or C or whatever, then the prefix of the viewport's name will also change once you allow the OI palette to refresh but only under one condition. The suffix of the name must still match the sheet name. If one changes the sheet name beforehand, as we have observed, the suffix of any viewport names on that sheet will not adjust to reflect the new sheet name and the process of updating drawing numbers to the viewport name will cease to function too.
  14. I don't understand this. Your Drawing Label "Accord Primary" doesn't call up the drawing title. Your Labels "Accord w back ref" & "Accord Secondary " updates ok when the vp is selected and the drawing title or number are changed in the OIP. Are you seeing different? See attached screen recording. That part was the improvement, it started functioning after checking the "use automatic drawing configuration setting" you mentioned.
  15. @Boh I sent you the file via private message. Don't worry about the titleblocks not updating; I built my own script to synchronize them.
×
×
  • Create New...