Dillon

Same here. Jim W? Dylan from tech support? Any news on your investigations?

Thanks for responding, gbland. I spoke to Dylan at tech support about this before I posted. He saw the same thing and said he would ask around but hasn't responded yet. I have to say I'm surprised no one else has responded to this post. This seems like such a basic feature to go buggy that I would think others would be upset. Maybe other people have a different way of showing existing and proposed contours that I don't use... I wish they would share... Dillon

FYI, NURBS curves set to the Site-DTM-Modifier class will also modify the site model.

Hi All, Tell me if I'm going crazy. I believe that in 2017 and previous versions, when I would set the 2D Display of the site model to be: "Proposed + Existing," VW would display existing contours with proposed contours overlaid. Importantly, proposed contours would only show where the contours were actually changed by site modifiers. In other words, all existing contours that were not changing would be fully visible with the graphic style for existing contours. See the 2017 example. Proposed Contours are in solid heavy black lines. Existing contours in dashed gray lines. This is what I want the software to do. This feature was buggy in 2017 and before. But usually with fiddling, switching back and forth with the 2D and 3D display settings I could usually get it to display correctly. In 2018, the site model shows all contours in the proposed graphic style underlain below all contours with the existing graphic style. In other words, you can't tell exactly where the site transitions from existing contours to proposed contours. See the screenshot. (Note: also in Proposed+Existing display mode the contours start making very odd connections (contours crossing contours) that do not show in Proposed display mode. That's another issue). I've made a test file that displays this behavior. Is this how VW is "supposed" to work? Did anyone else notice the change from previous versions to 2018? Thanks, Dillon test contours exst prop.vwx

Is there any experienced user out there who would say the Landscape tools work as expected out of the box? Is there any experienced user who would say that you can use the Landscape tools to go from concept to construction docs without complex work arounds?

I'm having the same problem with the stake object in 2D Graphic mode in VW 2015. My workaround is to set mode to "site modifier object", enter the data I want, then change mode to "2D graphic object." It then shows the elevation I want. Dillon

I have the same problem with 2D objects in 3D views when rendered with Renderworks. OpenGL is fine. I asked tech support about this and they say it is a limitation of the software. Jim, how do you get acceptable results? this is particularly a problem with the parking space tool which only produces 2D results (the "show 3D stripe option creates super blurry lines). This is the tech support response: Renderworks is optimized for 3D geometry. The ability to see any 2D planar objects in a Renderworks render is actually a fairly recent addition. In most cases, 2D planar objects should not be used if you intend to render in a Renderworks mode. When creating 3D models, it is best to use only 3D objects. In this example, simply converting the line to 3D polygon with drastically decrease the render time and allow the object to render correctly. Our engineering team is aware of the current limitations of planar objects in Renderworks modes and is working on adding better support in the future. Thank you. -- Michael Groves Technical Support Specialist

+1 on the shift-U to go backward through tool modes

I suggest that this info be put under the search bar in the forum pages. Too many people have wasted too much time using built in search of the forums. Or maybe you can just link to a google search that has "site:techboard.vectorworks.net" preset.

I suggest that this info be put under the search bar in the forum pages. Too many people have wasted too much time using built in search of the forums. Or maybe you can just link to a google search that has "site:techboard.vectorworks.net" preset.

I haven't done this myself, but I think others on this list have previously suggested using the roof tool for this kind of situation. Dillon

Thanks for the response. You hear this a lot, but your posts have made a world of difference in my feelings about VW.

Returning to a previous discussion--now that you are able to talk about the actual pending release--is there a significant performance difference between a low end MacPro and a maxed out iMac? Dillon

I'd like: 1. a search function for layers and classes. 2. folders for layers (could be similar to the way classes work with "-" creating nesting. But folders would be nicer).

I am constantly bumping up against out of memory errors when saving. Autosave works fine, but regular save doesn't. These are files in the 300mb+ range. Some days a file will regular save. Some days it won't. I can't find a pattern. I'm using 2014 with SP4. I thought SP4 was supposed to solve this problem. Anyone have a solution or a known conflict with another program?