Jump to content

PO4

Member
  • Content Count

    27
  • Joined

  • Last visited

Everything posted by PO4

  1. yes, gumball would be amazing! also, push and pull for edges and points! in rhino I can select a collection of edges or polygons and adjust them directly. this is very efficient if you have custom objects you need to adapt quickly. example: creating a sloped slab takes a second in rhino. in vectorworks you would have to do a series of boolean operations or construct a slab out of polygons to create the same result. 5 seconds vs. 10 minutes at least.
  2. dear forum our architecture firm is experimenting with VR since the first oculus rift dev kit in 2013. back then we modelled all our 3d content in rhino, simply because modelling in rhino is much more efficient. vectorworks has luckily improved a little in that respect (although there is still quite some way to go). to achieve a better workflow, we would really love to do as much in vectorworks as possible. unfortunately, there are still some big issues with vectorworks that prevents a smooth workflow. we really love vectorworks for 2d work (I've been working with it since around 2004), I'd love if vectorworks became as strong for 3d work. the most issues I have with vectorworks are: navigation navigation in 3d space is simply horrendous. please look at how rhino does navigation, or blender, or any other self respecting 3d software for that matter. I don't need a context menu and would much rather like to use the second mouse button for navigation. I bought a space mouse which is the only way to make working in 3d space bearable. texture mapping texture mapping isn't transparent at all. also, why is there no way to cube map objects? I love the 3d hatches but they don't work if I try to project a texture top down (onto terrain for example). modelling as far as I know there is no projection mode, so moving 3d objects in 2d space often moves/snaps objects onto a different z-axis. very annoying... modelling is generally very unintuitive and frustrating, lots of steps to create simple objects (again, rhino...). 3d export cinema4d and fbx export works ok. but it would be nice to be able to have more options (for example merge all meshes with the same texture instead of having thousands of individual objects (look at how rhino handles for example .obj-export). rhino3d-export doesn't work if the project gets too large. very lucky that we have rhino import export at all. and by far the biggest issue NORMALS. it frustrates me so much that normals still aren't solved. there are posts about this topic going back to at least 2013 about this topic. there is no way to display reversed normals in vectorworks itself, so no control whatsoever. also mirrored objects get exported with reversed normals, and there are various random objects where there are normal errors. this creates so much working cleaning up the geometry. vectorworks is really becoming a very strong software package, also for 3d and BIM and I really hope that these issues are taken seriously and under consideration. thanks :)
  3. dear forum I'm right now working on a landscape design wich is in full 3d. for the execution plans I would like to have a more abstract plan presentation which is why I'm using hidden line drawing and surface hatches. to my problem: I'm having issues with mapping my materials onto my geometry. for my use I'd prefer a top down/global projection so that my surface hatches are aligned correctly over different polygons. unfortunately if I try to map purely top down, my surface hatch vanishes... coming from cinema4d, a cubic projection would be quite helpful in this case. if I use the default projection, the surface hatch on every polygon is oriented differently. see the grass in my screenshot. is there any way to resolve this? I also tried to use flat shading but then all edges are displayed which is not usable either... thank you for any input on this!
  4. hey sorry for the late response, thank you for the additional info, that helps! best
  5. we are in the process of using Vectorwork's BIM capabilities in conjunction with a wooden construction project. generally things are going great. but I have been asked by the engineer if vectorworks is able to read and write ifc information via tables. I am able to export IFC information via tables but is the opposite possible? thank you for any help on the matter.
  6. In the process of working more and more with BIM in our office I recently discovered energos, which seems to be is generally a fantastic addition to vectorworks. Unfortunately I find the documentation somewhat lacking. I'm right now trying to add my custom window symbols to the system and I have found the necessary documentation here: http://app-help.vectorworks.net/2018/eng/VW2018_Guide/EnergyAnalysis/Designating_Drawing_Objects_as_Custom_Energos_Systems.htm and especially here: http://developer.vectorworks.net/index.php/Energos:_Use_Record_Formats_to_define_energy_analysis_data#Window The problem is there is very little information about what exactly the parameters mean and what their effect is. I have for example no idea what frame length is. Is it enough to simply add window area and u/r-value, or do I need to fill in glacing area, glacing length (?), orientation etc... Thank you and best regards Yves
  7. Hi Matt Thank you so much for that solution! I have no idea how that geometry was added to my 2d view since I never edited them (only the plan view). it's interesting too that the original geometry is displayed correctly while the mirrored geometry is not... Again, thank you!
  8. I made a file illustrating the problem. can someone please confirm and add this bug to the list of things to fix? this is driving me nuts, do I really need to create a mirrored symbol of the same geometry? vectorworks really need to fix their geometry normals issues!!! test.vwx
  9. I could not resolve this problem yet. all vertical same looking elements are the same symbol, I have no idea why they are not all showing when mirrored. has no one else encountered this error?
  10. I think I just found a bug: I have a section with background view enabled (only visible lines). unfortunately mirrored 3d symbols are not displayed. if I mirror the symbol, the geometry appears. funnily enough, on the 2nd and 3rd floor, which are simply layer viewports of the 1st floor, the symbols are displayed correctly... can anyone confirm?
  11. thank you for your input. I experimented a little bit more and I think I have found the issue now: I have a lot of meshes in the interior of the building, mainly in the bathrooms (toilets, bathtubs, sinks). if I hide this class render times a reduced to around 20 seconds. the terrain on the other hand does not impact render times very much. so... do NOT use mesh objects in elevations :).
  12. ok these are my results and settings: the red elevation is simply using front view while the grey elevation is a section. render times are around 7 minutes for the front view and about twice that for the section. this is unbearably slow unfortunately... if the project was even bigger I'm not sure it would finish at all. vectorworks is using around 50 gb of ram right now.
  13. hi matt thanks for the input! I tried that but I lose a lot of detail/lines like this, at times symbols aren't rendered at all. not sure if my model is too complex maybe? I'll try to post some images later...
  14. I trip over this topic over and over again. I'm now working on my second bigger project in BIM and generally happy with how vectorworks handles things. plans and sections both work rather well. what I'm still having issues with are visible lines behind sections and especially elevations. what would be the ideal way to create an elevation from a model? right now my workflow is to create a viewport of a front view in a design layer and choosing only visible lines as foreground render mode while opengl is used as background render mode. this works most of the time but sometimes random lines are missing or lines that shouldn't be seen are rendered. this is a problem of quality and control which I'm confident can and will be improved in future versions of vectorworks. the second (and this is a big problem for me) is render times. the project I'm working on has 5 stories and rendering a facade in 'only visible lines' takes 5-10 minutes using only 100%/1 core of my machine. Is there any way to improve these render times? this really breaks my workflow and I'm sure I'm not the only one. or am I missing anything?
  15. we could solve the problem as follows: by using a pad with retaining edge and projecting the retaining edge upwards by using the command 'send to surface'. since I'm using the german version, the command is called 'z werte anpassen'/'adjust z values'.
  16. I sent you a PM, thanks!
  17. thank you for the quick reply. I tried both pad modifier and pad modifier with retaining edge. I'm preparing the file now and send it to you asap.
  18. when I try to introduce a vertical excavation into my site model, I get very rough edges as seen on the attached screenshot. the site model is based on a 10x10cm resolution laser scan. the rough edges are probably the effect of the triangulation vectorworks uses. is there any way to get smoother geometry when editing site models? thank you yves
  19. hi paolo thank you for your feedback! since I'm working on macOS and prefer it that way, your help is not really applicable to my scenario. I made a video of my issue which explains the problem quite well. please notice the status bar on the bottom right. as long as there aren't any coordinates visible there I'm not able to move my view. as you can see, it takes more than a second between the stop of my movement and the coordinates reappearing. I think this has more to do with the number of objects and seems to be cpu related, not an issue of the gpu. also, this is something I noticed on several macintosh systems. does no one else experience this issue with bigger projects? vectorworks2019_delay.mov
  20. Hi Paolo I'm working on a Hackintosh right now, but I had the same behaviour on a Mac Pro (late 2013). When I say delay I'm talking about 0.5 - 1 seconds, nothing much but very annoying for my workflow. Best Yves
  21. Hi Paolo I'm working on macintosh: macOS High Sierra 4 Ghz 32 GB Nvidia GTX 1070 Vectorworks 2019 Thanks
  22. I have a problem that annoys me for quite some time now. I just invested in a space mouse which makes this problem even more apparent and I'm wondering if other people also experience this and if there is anything that can be done about this: if I'm in perspective view (I normally use open gl but it's the same in wireframe mode) and I try to orbit, pan or zoom, there is always this slight delay between clicking and the view actually changing. as soon as the view actually changes rendering is very smooth, even with complex geometries (I have a nvidia gtx 1070). this delay happens right after I try to make a view change and also again after the change happened. so it's really not smooth working like this. I was able to improve the situation by deactivating some interactive activation options, but it's still not good. it seems as if vectorworks need to actively change it's mode of operation to 'view change' and than back to 'edit model'. is anyone else experiencing this? again, I don't think it has anything to to with rendering, it's the same behaviour if I display the model as wireframe. this is with vectorworks 2019 sp3 by the way. thank you for any help with this! yves
  23. oh wow, thank you so much! I was trying all morning to resolve this issue. Am I correct that only the internal vectorworks origin is moved like this? I still see the correct coordinates when looking at the ruler – fantastic!
  24. hi hans-olav thank you for the reply! I first thought that as well, but that's unfortunately not it. vectorworks really is behaving quite strangely. other 3d elements are cut correctly but all wall elements are grey and have a super bold cut line. one thing I noticed is that if I copy the geometry to a new file and close to zero, it sometimes works. If I copy the geometry to the same location as the original file, the result is the same. unfortunately if I move the zero point in the original file the result stays the same. I attached the file I'm working on, maybe someone of you could take a look. thanks! test.vwx
  25. hi forum I just updated to vv2019 and I must say coming from 2017 there are some impressive and long sought for changes! Especially being able to finally merge objects that have the same class is a very welcome change. I have stumbled over what I think is a nasty bug. I'd be glad if someone could help me out/confirm this issue? maybe it's user error but the same worked fine in vv2017. if I create a section of a wall which has wall components I get a very ugly bold line, neither in the color nor with the width it should have specified by the components class. if I remove the components, everything looks as it should. what could be the issue here? thank you and best regards yves

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...