Jump to content

Kevin McAllister

Member
  • Posts

    5,162
  • Joined

  • Last visited

Posts posted by Kevin McAllister

  1. If you export a single sheet and check "Export Viewports as 2D Graphics in Model Space" everything comes into model space. It seems to group them into symbols but it was more successful than I expected.

    KM

  2. ( I don't consider the Auto-hybrid a suitable substitute for this even thought it contains all the basic functions needed for this purpose)

    I certainly does but you can only have a few in a file before the overhead becomes crippling. All of these dialogs require real performance under the hood, something VW just doesn't have. The stair dialogs are heading in the direction of the roof dialog shown and they can be excruciatingly slow at times. (I have a top of the line Macbook Pro with retina display, other graphics applications fly along.)

    KM

  3. Quit and restart. Make sure Save Viewport Cache is turned on in the Document Preferences. Render viewports one at a time, saving after each one. If you get the error again and it won't let you save, choose Save As and save to a different location with a new name. It may tell you it can't but most of the time it still saves successfully.

    Kevin

  4. Let's see VW 2014

    Replacing "car" engine while moving on a highway was probably very tricky task.

    I would expect them to concentrate more on this core job and care less about improved aerodynamics and luggage space of the "car"

    I doubt that they are happy with half baked new "features" of the package ...

    This is a good analogy. What they should have realized is big changes for the user are ok if they're done fast enough. I would prefer to learn a new workflow in my existing software than learn a whole new software package. But we've had to learn a new workflow each version (the screen plane / layer plane adventure as an example) which uses way more resources than a quick change.

    Kevin

  5. I'd like the functionality of the Renderworks Camera improved when its used to create linked Sheet Layer viewports. Specifically I'd like to see -

    - improved behaviour when pasting camera viewports to new sheet layers. The error dialog "The Renderworks Camera tool cannot be used on a Sheet layer. Please delete and place on a design layer" is clearly a bug. Please fix this.

    - improved behaviour when duplicating camera viewports and changing the layer they look at. When you go to edit the camera view it defaults to the original layer view, not the new one.

    - direct access to the Fine Tune Camera View dialog from the OIP of the camera viewport. I don't want to go into the design layer to edit the camera, I would like to see the fine tune results directly in the viewport (wireframe is fine) with my crops in place.

    - a full overhaul of the Fine Tune Camera dialog to make it more responsive and user friendly (ie. don't jump to 2 degrees as I type 24 degrees for camera field of view).

    Even in Sketchup's Layout you can easily click in a perspective viewport and rotate the model in realtime on a sheet.

    Please and thanks,

    Kevin

  6. There is no way I know of to easily do what you're asking for (constrain to X, Y or Z is common in other 3D modellers). Sometimes the snaps will behave appropriately but often not. I often wish I could just slide things across the ground plane with no fear of them ending up in a random 3D position.

    KM

  7. Even Sketchup and other low end modellers are passing VW in some areas. NV uses the line "best in class" but I"m not really sure what class VW is in anymore.

    (I hope that secretly they've been developing/testing a revolutionary version in during the transition to the Parasolid kernel/64 bit version and that the current releases have essentially been maintenance releases of the old version to tide us over. In the VW/Revit thread there was a link to a quote saying the Parasolid transition was recently completed.)

    KM

  8. The only way I know of the fix the numbering problem is to renumber the drawings manually (a pain because for regular viewports you need to edit the annotation and individually select each drawing label, at least with section & detail viewports the drawing number is editable in the OIP when only the viewport is selected).

    I've only had drawing labels disappear during a batch PDF if all of an individual font disapppear (ie. font corruption). Do the drawing labels contain special characters (ie. degree sign, diameter symbol etc.)? These can cause things to disappear.

    Kevin

  9. The page boundary is usually located at the origin in the design layers. If you are working far away from the origin, that's why it feels like its jumping. The solution is to move your object close to the origin.

    (PS. if the page has been moved, you can get it back to the origin by double clicking the page move tool in the tool palette.)

    Kevin

  10. Please submit your example file to NV tech support as a bug.

    Does it only happen with copy/paste? Can you option drag? Can you duplicate? What are the render settings for the viewport? Is it possible the viewport is corrupted?

    I copy, paste, option drag and duplicate sheet layer viewports all the time and have never experienced the issue you're describing. I did a quick test and couldn't recreate it.

    Regarding the little arrows, are they red NURBS direction arrows or something else?

    Kevin

  11. The scale of the drawing title is determined by where its placed. If you place it on the sheet layer directly it will show full size. It needs to be in the annotations of a sheet layer viewport so it takes on the scale of the viewport. Double click or right click on the viewport and choose Edit annotations. Place the drawing title there.

    Kevin

    PS. I've added an example file. The blue elements are directly on the sheet layer. The others are in the sheet layer viewport's annotations. Anything in the annotation relates to the viewport's scale. Anything outside relates to the sheet layers scale.

  12. Its likely to do with the render state of the viewport. Is the viewport outdated with the dashed red line around it?

    Likely it worked on Friday because the viewport was rendered. Make sure Save Viewport Cache is turned on in the Document Preferences so the rendered state of the viewport is saved. If its turned off, the rendered state you had on Friday was lost when you saved and quit at the end of the day.

    Kevin

  13. I have submitted many bugs myself. Its very powerful but just not very user friendly as a container.

    Paste in place doesn't always work in this instance, especially I've you've moved the Auto-hybrid at all. They seem to have their own origins.

    Kevin

    Grant if you have a problem Auto Hybrid object can you please submit it as a bug.

    One option would be to enter the Auto Hybrid object, copy the 3D geometry, exit the Auto Hybrid object and then delete it with the 'delete' key. Then use paste in Place to insert just the 3D geometry back where it originally was so you can edit it as required.

  14. Just to note, whether something is "foreground" or "background" is a bit misleading. VW is basically just layering rendered versions of a viewport like tracing paper. There is no difference in the render time based on "foreground" or "background". VW just has to render twice if both are selected.

    The bigger issue is what resources VW uses for each render mode. Hidden Line is rendered by VW itself so it only uses a single core, regardless of your processor, and is only 32 bit so it can't maximize RAM. Its drawing lines not pixels. There has been a lot of discussion about having to render basic line drawings in other reads. You are not alone. Turning generate intersecting lines off in the viewports render settings can help, as can turning off things that aren't seen.

    Rendering using Renderworks modes will be far faster if you have a good machine. Renderworks takes advantage of all your processor cores, is 64 bit and can maximize RAM use (it's Cinema 4D underneath). Resolution of your sheet layer can make a difference here as can lighting and other factors.

    OpenGL mode uses the graphics card. If you have a good card, it will render faster.

    Using symbols and other efficiencies will also affect render times. Check your " conversion resolution" on the 3D tab of the VW preferences. High or Very High can slow things on slower machines. And make sure "Save Viewport Cache" is on in the documents preferences so you don't have to rye render each time you open a file.

    Kevin

  15. I've never been able to get this to work (not for lack of trying as I always draw by geometry). My workaround is drawing a single arc through the corner and crossing the edge first. As long as the arc and the bounding rectangle are on the same plane, and Snap to Intersection is on, it will snap properly.

    Kevin

    PS. What are the VW1 and VW2 palettes at the bottom right of your screen? They look useful....

    ubbthreads.php?ubb=download&Number=9022&filename=Screen%20Shot%202013-05-10%20at%208.45.34%20AM.png

  16. John,

    You need to insert the drawing label/title in the annotations of a sheet layer viewport. Its likely if the drawing label is on the design layer and then viewed in a sheet layer viewport the scale will get confused. If the viewport already exists, right click on it and choose edit annotations.

    Some people may work differently, but I only ever put drawing labelling and dimensions in the annotation of a sheet layer. My design layers are geometry only.

    Kevin

  17. I think you're probably right. I tried it on a project soon after installing 2013 but discovered/reported a bunch of other bugs.

    I thought I would revisit it after SP3 and now have a couple of projects using it. It is much more stable but still needs more work.

    Its fairly well suited to my work and the type of stuff I draw, especially for single set elements.

    Kevin

×
×
  • Create New...