Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

261 Spectacular

About EAlexander

  • Rank

Personal Information

  • Homepage
  • Location
    Princeton, NJ

Recent Profile Visitors

2,084 profile views
  1. There is no gallery on this forum, but I bet if you post and ask for constructive criticism, you'll get it. The community is pretty good around here. I'll give you some feedback.
  2. You could also build this as a sweep and that would let you adjust the segment angle, so you can control the "resolution" of the arc. Lower number = smoother curve.
  3. Nice to see you @L_M! Miss you. Let's catch up!
  4. A few ways to approach this: You could draw a nurbs curve as the backbone of what you want and then extrude along path with a simple profile. I'd run the profile "long" so it burries into the deck and then trim/slice the bottom flat at deck height. You could also draw a nurbs curve for each side (and maybe even centerline) and then loft them. Again, trim the bottom flat after the fact as well as upstage and downstate edges. With any approach, I would get the mass of the shape correct and then slice it up into stock and custom decks or any way you want. Hope that helps some. e.
  5. I'm not sure about putting the product into context, but have you looked at Sketchfab?
  6. For a quick hack: I would render it out with the texture blowing out to what ever lights the room correctly and then overlay clean artwork on the screen in post (Photoshop).
  7. Thinking about this more - some things that may or may not help you (forgive me - I don't know if you use Cinema yourself, so ignore if you know all this): 1. I always name my objects in VW - or at least name the group they are in. Those names will carry over to Cinema so your client can see the names in the Cinema object manager. If not named, they will get 1000 objects named extrude...... 1786 objects named Solid Addition, etc. 2. I try to solid model as much as possible instead of POIs and convert things to generic solids once I'm ready to export final model. Keeps things cleaner - though if you do this, name it AFTER you convert. 3. In Cinema, you have to be careful of complex or PIO objects splitting into dozens of polygons and should be fused back together to keep the file running efficiently (Connect objects + Delete command in Cinema. For example - a stick of truss will come into Cinema as a folder with each chord and each piece of lacing as a separate object. Multiple this by all the truss and your got thousands of objects slowing down the scene when not needed. I go through and connect them for efficiency sake. 4. Layers translate to master folders in Cinema (called Nulls) - so if you have all the truss on it's own layer, your client will automatically get a folder in cinema with all the truss in it (and anything else on that layer) - so use layers with that in mind. I certainly use more layers then I normally would in VW, knowing that this will help me stay organized in Cinema later. 5. I always use "Export to Cinema (3d Only)" and never use Send to Cinema. I found it buggy, but haven't tested in recent versions. I prefer to export and open the generated file in a clean shuttle file and then copy and paste into my master document. 6. Find out what render engine they are using. If native cinema, then you can texture in VW and they will carry over. But if they are using a 3rd party render engine (Redshift, Octane, Arnold, Corona, etc.) they would have to rebuild the textures anyway. So you could still make texture for unique materials (concrete, glass, Iron beams) but those could just be all white with no dialed in properties. Then they come through as white and assigned correctly, and the client can just swap your blank concrete for their, say, Redshift concrete and go. Make sense? No point in using specific materials in VW if they are using 3rd party materials in the end since they will have to rebuild. There are material converters, but honestly, they don't do a great job and get messy fast. 7. If you are adding lighting instruments (as lighting instrument objects instead of just symbols) - do some tests with client. Lighting instruments lose their rotation and focus when you export a lot, so dial this in with some test files first. I realize a lot of this is more on your clients side, but might be useful information. Let us know how you get on.
  8. Following with interest. I'd set up a test file with one version of everything you have going into file (PIOs, truss, hybrids, lighting instruments, walls, etc.) and kick that back and forth a few times before starting the actual build out.
  9. Also: Delete or Backspace key (can't remember off the top of my head) will undo your last point, and you can keep hitting that and back up point by point.
  10. ...annnnnd, if you miss the end point, you can check the CLOSED box in the object info palette to close the shape (must be closed to extrude correctly if going to 3D.)
  11. Hi Nick, If you ever think you want to do any rendering - be it via blender/Cinema 4D or right out of VW with Twinmotion or Lumion - I would go with Nvidia hands down. Modern rendering leans heavy on GPU and it's fastest on CUDA based cards. If you are just using VW, I'm not sure it matters anymore, but I'm not up to date on AMDs latest offerings for GPUs. The question will be when can you actually get your hands on a 3xxx card.....
  12. Wow - amazing! So which way is north then? *runs
  13. I wish, with clip cube, I could create a 3D object and use it like a boolean directly to viewport. I'd be able to move and manipulate that parametric object like any other solid (or add solid/subtract solid/generic solid) and be able to build variation in length, height and depth. Then update viewport.


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...