Jump to content

Will

Member
  • Posts

    159
  • Joined

  • Last visited

Posts posted by Will

  1. Tried it, doesn't work for me. Sometimes quitting and reopening vectorworks fixes it for a while, but on some projects it comes back really quickly.

    On 8/31/2020 at 6:26 PM, Shneck said:

    Guys I think that I have solution to this :-)

     

    When I was importing reference DWG file in VW, I have to choose units of source file. Mine was survey file in meters. Then confirmed import and VW automatically created Layer with imported geometry. But this layer had huuuge scale 1:50000. Seems to be due metres to milimetres conversion.

    When I edit the layers scale to 1:50, all clipping issue is gone 🙂

     I can even reproduce this problem again when one layer with objects gets bigger scale, display issues is back. Then give it normal scale and all is good again. It also makes sense why it is only present in some of the files, because it is layer setting in this file.

     

    So - check Your layers scales if there are some with huuuge scale compared to rest of layers and make it smaller. 

     

     Hope Your issue is the same and this solves it 😉

     

  2. @Tamsin Slatter Thanks! Ideally, rather than making us interrupt our work to go and hunt down and delete the rogue bit of drawing, I think it should be an alert that says, "Some geometry is further than n km/miles from the internal origin. It will not been shown and cannot be snapped to during 3d operations"1 as a modal alert first time, then as a minor alert in the message bar bottom right subsequently every time the user switches to a 3d view. From then on any stuff too far away is just ignored by the vectorworks graphics module when working in 3d. Sometimes it is unavoidable to have some things which are too far away from the origin e.g site mapping information, but they are almost never things that would be relevant in 3d so when working in 3d they could just be ignored by the system.

     

    1 Where n would be whatever your programers calculate as the maximum the graphics system can cope with.

    • Like 1
  3. Update on this for anyone else experiencing the problem. Export the file to VW 2019 open the file in VW 2019 then make a minor change e.g draw a line. Save the file. Re-open the file in VW 2020. Reshape handles are back. It is apparently a bug and they are looking into it.

  4. I think it must be a file corruption bug @PVA - Jim as if I create a new file the reshape handles show up fine. Here is an example screen grab video. As you can see, its not my selection tool settings and it is really annoying when trying to work with site pad objects as you have to guess where the handles are for editing the slope. Why does this always happen to me when I'm trying to get finished for a deadline...😭

  5. Yes and the snaps that work in some contexts but not others. Why can I snap to intersections, line extensions and tangents when drawing or adjusting a polyline, but not when drawing or adjusting a polyline based object like a road? Likewise when drawing a line in 3d there are way more snaps available when drawing a line than when, say, adjusting a site model object or a wall. Why can't I grab the handle of something and get it to snap to a z axis locked intersection line with the face of a 3D object, but I can do this with a line. It's so confusing.

    • Like 3
  6. 9 hours ago, Amorphous said:

     

    The Australian distributor actually has a far superior window and door modelling tool called Windoor.

     

    Nemetschek should buy it from them and put it into the standard VW version.

     

    We concur with this post, and personally would prefer the following simple things fixed over giving us any new features (my list is all about productivity and workflow):

     

    - Section Viewports rendering time (snappy renders please, even with 'surface hatches)

    - 2D DWG export from 3D models (Usable files, smaller size)

    - Titleblock Object (Let multiple users modify different title blocks in Project Share. Any operations on TB is sooooo slow!)

    - Stair tool (SO INCREDIBLY SLOW)

    - Visibility tool (wait five seconds us to load the tool)

    - Slab tool (try reshaping it, SO VERY SLOW)

    - Floor tool (in 2019 totally broken, corrupt objects, wrong class appearance, disappearing fills) 

    - Grid Tool (appear in 3D, line thickness control!) 

    - Space Tool (try reshaping it!) 

    - Detail callout Tool (leader line goes crazy when line settings changed. Difficult to reshape geometry but maintain rounded corners) 

    - Undo Operations (Really should be so slow it crashes a computer)

    Yep totally agree with this list.

    Before they upgraded the title blocks I coded my own integrated with my own drawing issue system, issue sheets and automated PDF creation and collation. But we gave up on project sharing because our jobs are to small for it to be worth the hassle, so I don't know how well they would work with that.

  7. Still poor general reliability. I've submitted about 6 crash dumps to bug submit in the last day and a half and experienced way more than that. Having a weird problem where VW sometimes randomly hangs while drawing 2d objects on planes in a 3d view. I had huge problems with generating sections yesterday where I could only get them to work by shifting them around until VW stopped crashing when I hit the update button. Not great.

  8. Do you think that's something that might be in a service pack as there are often instances where a wall or component is slightly out. Is the tolerance tighter than the max decimal places (in degrees) we can see in vectorworks because I'm still having problems with interior elevation viewports. I've got a set of symbols with front and side 2d components and they are working fine in two out of 3 rooms, but my last interior elevation marker is not generating drawings with 2d components. I have switched on all layers and classes, verified that it is orthogonal to the max number of decimal places. I duplicated an interior elevation marker that I know is working in another room and checked the section lines, just not seeing any 2D components at all. Thanks W

  9. Also, can someone tell me, is there a tolerance on how orthogonal the a view needs to be? E.g. If a toilet is on a wall that is at an angle of 30.002º and the interior elevation marker is placed at an angle of 29.999º is that going to work? I'm having real problems with some interior elevations not showing the 2d components.

    Thanks W

  10. So I can recreate the problem by starting a brand new blank metric template. Draw a rectangle in plan. Create symbol based on the the rectangle. Switch to symbol front component, draw another rectangle. Create a section viewport on a sheet layer. Verify that the section shows the front component rectangle. Rotate the section cut line and the symbol by 30º. Verify that the front rectangle has disappeared. Results of this process are in the attached file. No data was imported, it was a fresh copy of an unaltered vectorworks supplied template and nothing more complicated than a rectangle was used. Seems like a bug in the 2d components feature to me? EDIT: But I'd really love to be wrong as I have a load of bathroom elevation drawings to knock out which I could have done in no time at all if I can get this working!

    Untitled 3.vwx

     

    Edit System specs. VW 2019 SP2. MacOS Mojave 10.14.1. MacBookPro Retina (Mid 2014) 2.5Ghz i7. 16Gb RAM. NVIDA GeForce GT 750M 2Gb VRAM.

  11. 15 hours ago, Tim C. said:

    @Will Hi Will, I wasn't able to figure out why this particular symbol is having problems, but if I re-create it the problem goes away. I've submitted a bug report for our engineers to take a look, but if there's any more info you can offer on how the symbol was created it might give us a better clue. Thanks for your help!

    Hi Tim, I created a new file from a standard vectorworks metric template, imported a dwg from a supplier, created a symbol from the plan view and then copied and pasted the front view into front view of the symbol. Should the front view geometry be on layer plane, 3d plane or screen? @Tim C.

  12. The best way to solve this would be to get rid of the concept of walls, slabs, roofs as different tools / objects. They are all composite plane objects built up of layers that need to interact with other composite plane objects at the edges. What I mean by composite is; built up from different materials in layers (called 'components' in the wall tool). What I mean by plane is objects defined by a plane like object or surface which could have an arbitrary boundary and holes cut in it. At each edge I want to be able to define if that edge is linked to the edge of another composite plane object and if it is how the layers (components) of object A interact with object B. Maybe you have a define connection tool which greys out everything and shows you a detail section where you can work all this out. Once you have worked it out for one edge, this could be stored as a favourite which would be available any time the same combination of two edges meet.

     

    While you are at it, can we have the ability to define repeating elements such as battens on layers in a way which preserves their orientation so they show up correctly in plan, but not section. Maybe just allow us to define an object which is repeating across a surface.

     

    The best bit would be that when the wall tool was improved, we wouldn't have to wait until next year for the corresponding improvements to the roof tool. So it would save a lot of development time as you would only have to solve the problems once.

    • Like 2
  13. Unfortunately it has occurred with both the 3D projects I have tried so far. The second one I tried was a clean project started in vw 2018. But obviously some wall styles and things like that are from libraries that have been updated.

     

    Its a shame as I really like the snappiness of 2019, the new zoom speed is fantastic.

     

    If I had to guess as to what has happened, they probably started work on improving the graphics module, which must have been a pretty major project that has taken a while, and they have forked the codebase before this was fixed in vw 2018 (I think is was maybe sp3) and now the bug is back. Hopefully if that is the case they can port the fix over pretty easily.

×
×
  • Create New...