Jump to content

lgoodkind

Member
  • Posts

    208
  • Joined

  • Last visited

Everything posted by lgoodkind

  1. Thanks so much for creating these for all of us to use! Very Useful. I don't know enough of Marionette yet to be able to modify this but for some reason when importing to 2018 all the text gets messed up so it's not readable. If you ever get a chance please let me know what would need to be changed to fix it. Thanks
  2. Thanks, I was confused by the option to delete leader line in the OIP which wasn't working for me. The context click menu seems to work now.
  3. Thanks for that - not always apparently clear - I was trying to use the obvious 'drawing stamp' button in the OIP. Phew - another late night with 50 drawing sheets to go. Thank you
  4. There are other issues with this tool perhaps I should note elsewhere. The major beef I have with it is that in order to change the drawing stamp one has to convert to and unstyled sheet border then re-create the sheet border style. Did anyone think about the consequences of this with a 100+ sheet drawing set? Do I have to manual go to every sheet and re-assign the style just to remove or change a F-ing stamp? Am I missing something here? LG
  5. Vectorworks, Please! Fix this bug. another tool that doesn't work. I Wonder how you beta test these things? Delete leader line doesn't work,
  6. I Agree completely. I've had to create separate files where I render extruded boxes just so I can actually see the difference between the textures.
  7. Agree - totally useless when you can't really even see what you are looking at. The same goes for textures and image thumbnails - can't see enough to tell the difference between them.
  8. This is an unbelievably frustrating problem we have encountered throughout the last 10+ years and never seems to get resolved. For all the time we have spent correcting drawings that have randomly had referenced files shifted, Vectorworks technically owes us money.
  9. Why did the help menu move to the right side of the screen? I think this change is really silly and makes for an annoying transition since almost every other software wiki I use the menu is on the left of the screen. Why do you insist on changing things that aren't broken to begin with?
  10. Rendering a section view is not well thought in VW - here's why. You can't include a background/sky that extends past any of the objects in your viewport. So it will look like this with the sky cut off at the roof. The only workaround is to place an object in the background with no fill or line at the height you would like the background to render.
  11. This is ridiculous. What is the point of using a database for notes management if it doesn't have the ability to spell check?
  12. I've noticed over the years that when you save a file in a rotated plan view containing referenced files and then re-open the file later all of the referenced files are no longer located properly in the file. For instance you have a civil survey file referenced in to your architectural site plan file. For ease of drafting you rotate the plan view so objects are orthogonal 90deg to your view. if you save and exit this file when you re-open it your civil file will no longer be located where you need it. This has been a HUGE problem for our office over the years and makes the 'rotate plan' tool pretty useless and in fact dangerous. VW 2018 SP01 MAC pro 2009, 64gb, 12-core 3.33, 12gb titan pro
  13. 2018 - SP01. I just tested this in other files and it does the same thing in every file I tested.
  14. Chih-Pin, I have a rotated plan view in the left pane. I have a perspective view in the right pane. In the right pane I am not unable to select 'OpenGL' from the rendermode dropdown or 'view->rendering->openGL' menu. As you can see from the attached screenshots there are, oddly, rulers displaying in the perspective window pane. When I change the left pane to a non-rotated plan view I can render in openGL just fine.
  15. It took me a while to figure this bug out - If you have 2 view panes and one is in a rotated plan view the other will not render in anything but wireframe.
  16. Am I missing something? If you try and Document Setup>Sheet Border/Title Block and select your newly created 2018 title block style it's not there. Only the default content is available. How is it possible to create a document wide title block?
  17. Alan, Were you ever able to figure this out. I too am puzzled by this tool association with roof/wall clipping. If the core roof component is set to be clipped by walls for instance is the wall supposed to extend all the way to the roof component in question and be clipped at the angle of the roof? Or will the wall always have a square top section no matter?
  18. Peter - I think you may not have read the full specs. Are you saying a 12 core intel xeon 3.33GHz mac pro with a 12GB Titan video card and 64GB of RAM is well below par? On top of spending $$$ for 3 licenses and service select I'm supposed to spend another $$$$$$$$ on new hardware every 3-5 years? I've been sold on service select thinking it might save money in the long run but if the processors are only supported for 3-5 years and the software doesn't support older hardware what's the point of owning it? Now I wish I'd stayed with 2017 for the next 5 years. I've switched to 'best compatibility' mode and back and don't think this makes a difference with the tools I'm having issues with. I think however the problems are not hardware related at all. When we upgraded to 2017 I worked with tech support to solve issues with the new Irrigation module that were corrected in subsequent service packs. I guess I've reached a level of frustration due to the amount of $$ spent on this software and time needed to work with them to improve it that I don't want to anymore. Sorry to all if I offend with my venting. The issue with DTM's occurs on both the new iMac and older Mac Pro with the Titan video card and 64RAM. Currently I am trying to solve the problem with roof components/styles in 2018 and just can't get the tool to work properly either with imported styles or the default.
  19. I can elaborate and I will do so as I find problems however - again this is taking up a lot of time already. First Our hardware iMac retina 5K 27inch late 2014 3.5GHz Intel Core i5 (4 cores) 16GB 1600 MHz DDR3 AMD Radeon R9 M295X 4096MB 1TB FUSION DRIVE Mac Pro (early 2009) 2 x 3.33 Ghz 6-core Intel Xeon 64 GB 1333 Mhz DDR3 ECC NVIDIA GeForce GTX Titan 12288 MB 255 GB SSD, 2TB SATA Mac Pro, (Early 2008) Serial, G88431HZXYL 2.8 GHz Quad-Core Intel Xeon 32 GB 800 MHz DDR2 FB-DIMM Graphics: ATI radeon HD 5770 1024MB 120GB Solid State SATA Drive Macbook Pro 15.4” 2880 x 1800 2.6 Ghz Intel Core i7 8GB 1600 Mhz DDR3 500GB SSD NVIDIA GeForce GT 650M 1024 MB Though there are too many issues to mention I will list the latest - it has to do with the new Title Block Manager 1. When updating existing title blocks there are of course issues with layout - so you have to make them 'unstyled' to edit the layout. When you try and save this new style as a resource it does not save it as the name you type in the dailog. You then ahve to search for it randomly because you don't know what VWOrks saved it as. 2. Once this is done if you want to use this style in another drawing by importing it - the changes you made to it do not reflect in the new file so you have to go through the same exercise again. With Roofs styles in an existing architectural model... 1. A component of the 2017 roof style (sheathing that was bound to the inside face of bound walls) no longer bounds to the wall but the outside edge of the roof. No amount of changing the settings to the correct binding changes this. 2. A component of the same style listed above (roof shingles with texture) now shows as transparent with no effect on light hitting the model - as if the floor is open to the sky. Again no amount of configuraqtion changes to the texture, roof style, layer, class settings etc changed it. The same occurs on all files using this roof style when updated to 2018. There are more though i have work to do....
  20. Looks like we are all being played for beta testers - again - with this new release. Over the course of just a few hours I've run in to so many problems that our office will be going back to 2017. I don't think, for the price we are paying for this software, that we should have to serve as beta testers. This product is not ready for public release. Only as recently as several months ago has 2017 had most of its bugs resolved. I suppose it will take another 9 months for this one as well. Save yourselves and don't bother with it. There are great ideas in 2018 that just aren't ready for public release yet. Some problems we've had - Terrain models have problems updating and crash every machine. They had to be re-built from scratch to work in 2018 Roof styles randomly showing transparent when in 2017 they are solid Roof style components not clipping properly to interior wall surfaces Multi-pane mode crashes this is just in 24 hours of use.
×
×
  • Create New...