Jump to content

P Retondo

  • Posts

  • Joined

  • Last visited

Everything posted by P Retondo

  1. Pretty sure this is a class issue. Turn on all your classes, and you will probably see your tables. If a symbol is assigned to a visible class but the objects in it are assigned to an inactive class, the objects will not show up. Go into the symbol edit space to see what classes are assigned to the objects. Sounds from the terminology you use that you are trained in AutoCAD. "Page view" in VWspeak is a "Sheet Layer." The viewport on your sheet has class controls that are separate from the class controls that determine what objects on your sheet are visible. So you have to look at both sets of visibilities.
  2. Go to "Export PDF" - does the window contain a checked box next to "Update visible out of date viewports prior to exporting"? PS: I wish everyone would get in the habit of posting both VW version and platform (Windows vs Mac) when they post a problem.
  3. Did you try hitting "ctrl+i"? (Windows version of the keyboard command) If that doesn't work, and re-booting your computer doesn't work, I would suspect VW has somehow become corrupted and would need to be reinstalled. I've had to do that on a few occasions over the years, it's a bit of a pain but not that terrible. Another possible fix is to re-create your workspace, though as far as I know, the workspace does not affect palette display preferences (but I could be wrong).
  4. NNA, please note this issue. Keynotes are a great idea, but the user interface and implementation are flawed. I have used keynotes frequently and with success, but even I can't keep track of all the quirks and workarounds. This should be a straightforward feature, but version after version fail to fix the problems. I sometimes wonder if it is worth it to pay for upgrades. Please do something!
  5. You can scale your hatches on the Sheet using the OIP. Select the viewport, look at the bottom of the Object Info Palette for "Advanced Properties," and enter a number for the hatch line scale. Given your screen shots, I'd start with a value of 0.25.
  6. Benson, Kevin, thanks - those are very helpful. NNA should hire you to help write the manual! I think there are mathematical definitions that would help those who care about what is going on understand. I.e., NNA should define a normal to a profile shape (some people understand that, some may not), define the relationship between that normal and the path or spatial axes (only the software designers are likely aware of these).
  7. Sinead, it is possible to remove, edit and replace openings in a roof. For anyone to give you useful advice, however, it is essential that you identify which version of VW you are using.
  8. Benson's explanation is intriguing, but I think it went over my head a bit. I'll have delve into those options further. It would be helpful if NNA would provide a precise mathematical explanation of the various checkbox options. The explanations in the help manual are intended to be understandable, but they sacrifice precision in favor of over-simplification. cberg, it looks to me like your specific problem is that the shape of the extrude is rotated 90 d from what you intended. The easy fix for that would be to edit the profile (right click the extrude object and chose edit profile instead of edit path). Then rotate your shape 90 d. I don't think the extrude along path command is necessarily aware of the relative orientation of your extrude shape, so it is picking an orientation based on its own logic instead of what seems to you to be your obvious intention.
  9. Jonathan as always is correct. You can assign the surface hatch in the edit window for the texture by clicking on the button "Edit Surface Hatch ..." in the lower left portion of the box. As far as I know, you will only see the surface hatch in "Hidden Line" view, it does not display in OpenGL or Renderworks.
  10. First, check to make sure your roof in Design Layer appears with a fill in Top/Plan view. Then in your viewport, set "View:" to Top/Plan view, then check both "Display Planar Objects" and "Display Screen Objects." Things should look right. This assumes that your roofs are roof objects, which are hybrid objects as opposed to something like an extrusion, which is not a hybrid 2d/3d object.
  11. No problems with Chrome here.
  12. As of v2017 SP4 it is still not possible by any method to rename a viewport, except possibly with a VS routine. Is there anything I am missing here? Is this fixed in 2018? Any why in the world did anyone mess with something that worked, was reliable, and that we all knew where to find? It drives me crazy to see things like this occur when I'm paying good money for updates every year, only to get a program that seems to accumulate as many bugs as it fixes.
  13. Sharon, I use the legacy "Cut 2D Section" tool, and it has never disappointed. A much better way to end up with a 2D section. One caution: if multiple layers are involved, your layer mode has to be "Show/Snap/Modify Others." Also, be sure all the necessary classes are visible. This method has been foolproof for versions up through 2017, no experience with 2018 yet. You can install "Cut 2D Section" by editing your workspace. Another tip: "Cut 2D Section" places all lines in an automatically-created new Layer. When you go to that layer, be sure you are in "Top/Plan" view for more reliable snapping & selection. Screen plane objects in any view other than Top/Plan have become problematic as of v2017.
  14. Wow, this is disappointing news. I have already noticed a big lag in booting between 2016 and 2017. I installed an SSD just so that 2016 would boot faster - 15 seconds. Now with 2017 it is at least twice as slow, and if 2018 makes it worse, that is a very bad trend. I am blaming the handling of resources as at least one problem. The resource palette is now very unwieldy, and doesn't really do any more than the old more compact palette did. When I click on the attributes palette to apply a hatch, it takes seconds for the hatch selection dialog to open, and then instead of just clicking on the desired hatch I also have to click on "select." I told my sales rep at NNA that if 2018 continued in this vein - making things slower and not solving longstanding issues such as window sills, stairs, etc., plus adding new unresolved display and snapping glitches - they can count me out for future upgrades. As a loyal and longstanding user and renewer for full Designer, I think I am entitled to make this complaint, and unless I see better reviews of 2018 I will not be installing the upgrades that I have paid for!
  15. Mark & Jim, I converted the file to VW2017. I still have this issue. On a sheet with 4 Renderworks perspective viewports (Realistic Exterior Final) I can change the Lighting Options / Ambient Lighting Brightness, but I cannot have a different Brightness % for each of the viewports. If I set one, they are all changed because the edit window changes the Renderworks Style. My request is to allow a viewport-by-viewport override of the style in much the same way we can override class settings. You often want to do that when looking at different views of a building, just as a photographer would adjust the camera depending on whether the subject is in the sun or in the shade.
  16. Has anyone else noted that when you have more than one rendered viewport on a sheet, you cannot separately set the ambient lighting percentage, even though from the OIP lighting control seems like a viewport property? Whenever I change the ambient lighting in a viewport, all the viewports on the sheet change as well. If this is truly what we are experiencing (VW2016), the request is to make each viewport separately controlled for ambient lighting %, as the viewport "Lighting Options" dialog box implies.
  17. Jim is correct. I installed an SSD on my tower computer over a year ago, and boot time for 2017 VW Designer with Renderworks is now 32 seconds - authentication is the one thing that remains slow. But SSD is just a disk storage device, it doesn't improve the speed with which the computer handles operations. That depends on the speed of your processor, and the amount and speed of your RAM - the dynamic memory into which the disk storage loads your program. I have an Intel Xeon processor at 3.47 Ghz, with 6 parallel processors, 6 GB RAM, and (also important) an nvidia Quaddro 4000 graphics card. I highly recommend this set of hardware for speed.
  18. The "Move by Points" tool is the latest addition to the array of tools for copying and moving. It was an attempt to provide something equivalent to the AutoCAD method of copying or moving an object, but it does have its annoying aspects. In addition to this tool, there are 5 other methods: Duplicate (either in place or offset, a preference you can set) Copy and paste Click and drag using "ctrl" modifier to duplicate the object being dragged Move command (moves any object by user input distances) Duplicate array (copies and distributes copies along x, y, and z axes according to user input) Each one of these has its place, but I tend to use "Move by Points" most often because it is more efficient, and you can click on any two points anywhere to determine the move vector. To me the annoying things have been mentioned. I leave the settings to one copy, move without duplication. I use the "ctrl" key modifier which, when pressed while moving, toggles to move + duplication (technically, it saves the original object). Multiple duplicates and the distribution modes are powerful and helpful, but we need to disagregate those functions so it is easier to control which method we want. To me, having a modifier key that always gives you move the object without duplication regardless of settings, and another modifier key that always gives you move the object with 1 duplication, would be a good improvement. Too many times I have inadvertently created 10 copies of an object because I forgot to change settings back.
  19. Thanks, Pat! I figured out is was the design layer viewports, but I didn't know how to fix it other than deleting them. Good to know! What I don't know is why the schedule object was ever designed this way . . .
  20. Suddenly, all my doors appear 4 times in the schedule. They are not in the drawings 4 times - if I change a door to uncheck "On Schedule," all 4 instances disappear, and vice versa. Anyone have a clue why and how to fix?
  21. I know this has been discussed in the past, but it's a daily hassle. We need to be able to have dimensions on our sheets stay in form even if we have to switch the units preferences. For example, when we have surveyor information in decimal feet, in order to work with that I switch my units to decimal feet. Then, all my sheet dimensions change from feet and inches to decimal feet. Similarly, when we want to work in inches, sheet dimensions again change on us. If we're not careful, this can result in embarrassing and erroneous output. So, 1) there should be separate settings for units in the IOP and in the various tool inputs, and another preference for dimensions. AND, 2) once a dimension has been placed, it should stick with the unit format and not change with a change in preference - or have an option to update all dimensions, yes or no.
  22. I use InfoEditor, a 3rd party program. It's still working with v2016. Look up Info Editor for Vectorworks on the web. It costs $20, saves a lot of time.
  23. Jimbo, there is a legacy tool called "Cut 2D Section." It will automatically create lines along any section take through a 3d object. Make sure if the objects are on separate layers that your layer mode is "Show, snap, modify others". If you don't see that tool in your workspace, you can add it via the workspace editor.
  24. Ditto LW and rDesign. For what it's worth, I haven't found any method more expedient than masking. But it has gotten to the point where I usually use the old 2d Section tool to extract geometry, then compose everything in 2d for sections and for elevations alike. Unlike Top/Plan view, the idea about having these boilerplate drawings automatically generate from the 3d model has failed. Due to a lack of resolution of many little details, it all adds up to an unacceptable presentation. I do find that the background generated from a Section viewport is useful, and can be cleaned up with a few masks. It strikes me that part of the problem is the lack of an equivalent to the Top/Plan view, where wall components can be properly joined to make for a proper 2d presentation. We don't have the same graphical interface when it comes to looking at the model from a side or in section.
  • Create New...