• Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About tsw

  • Rank

Personal Information

  • Location
    United States
  1. One other thing you can try (but it's very dependent on how the original Sketchup model was made and how complex it is): Select your imported Sketchup mesh. Modify > Convert > Convert to NURBs. Ungroup the resulting group of NURBS surfaces. Model > 3D Power Pack > Stitch and Trim Surfaces. If all goes well, you should end up with a Generic Solid object that will appear in section correctly.
  2. Looks like VW2018 Service Pack 2 fixed it. Thanks!
  3. Broken section line viewports don't seem to be rendering correctly in Vectorworks 2018 SP1. It appears to be cutting a section along the initial line instead of following the broken line. See example below. If I export this file to VW2017, it renders correctly. Is this a known issue with VW2018? section test.vwx
  4. Not sure on the first, but for the second question: I think you have to open those resource files individually which will convert them to version 2018. After resaving as VW2018 files you should be able to add them to your Resource Browser.
  5. Has anyone tried playing with the new "Shadow Catcher" shader in VW2018? Looks like it's made for this type of situation. Attached is a test file and the resultant PNG with transparency. One advantage is that you could deform your shadow catcher plane or apply the texture to a site model. This would make the shadows appear to be hitting an irregular surface, which could look more realistic in the final composite. Edit: I tried applying a displacement map to the shadow catcher plane, thinking it would be a quick way to simulate shadows cast on a rough surface like the beach in barkest's file, but unfortunately once you make a texture use Shadow Catcher, it greys everything else out. (You can't have both a Shadow Catcher in the Transparency channel and a displacement map in the Bump channel.) Still a pretty cool new feature though! Shadow Catcher Test.vwx
  6. Thanks for taking a look at the file and confirming it happens on your machine too. Good to know it's not something specific to my set up! I submitted the bug report with a link to this thread.
  7. Here's another quick test file. I can get the look Bertf is going for in VW2017, but when I open the same file in 2018, the previously dashed line renders solid. Is this happening for you too? Screenshot of how the Hidden Line viewport looks in 2017 (vwx file also included): dashed line test v2017.vwx
  8. I've been having the same problem in Vectorworks 2018. In VW2017, I could make objects in a section/hidden line viewport display dashed by making sure they were set to use class attributes. However, this no longer seems to work in VW2018. See this thread for an example:
  9. In addition to the suggestions in the thread Andy linked, you could try applying a transparent texture to your object then duplicating it in place and removing its fill. It will then display as a wireframe in OpenGL (albeit without anti-aliasing, so the lines are a little jagged). It's a bit of a workaround (and makes further edits a little tedious), but it kind of achieves what you're going for. Here's what it looks like in a rendered viewport:
  10. Sketchup 3D Warehouse is a good resource for free 3D models (and they're easily importable into Vectorworks). The quality can vary quite a bit, but there are a lot of common objects (some even provided by manufacturers). https://3dwarehouse.sketchup.com/search.html?backendClass=both&q=radial arm saw
  11. If you add a crop object to your viewport that extends above the roof line I think it should work as you've described without the need for a background object.
  12. I've been playing around a bit with parallax mapping too. My understanding is that the intent is to simulate displacement mapping, but without creating real geometry (thus avoiding the increase in render times). Here's an example image and VWX file that uses a PNG for the bump/parallax shader. Note that I think you need to also have something greater than zero in Bump Strength for the effect to show. The biggest advantage is that parallax mapping can occlude itself vs. plain bump mapping which cannot. If you look closely at the examples you'll notice the pebbles in front are covering those in the back, while the plain bump map looks "pasted" on the surface. The difference is even more pronounced at a steeper view angle (bottom image). What's odd to me is that shadows don't appear to be effected by parallax mapping, so it looks a little artificially flat on the sphere example. I'm not sure if that's a limitation of parallax mapping. (It would be really cool if it was possible to turn on Self-Shadowing with parallax mapping!) Parallax.vwx
  13. Yes, I've run into a similar problem as well (VW2018 Win 7 64-bit). See attached file. Callouts don't seem to be using the correct class attributes, even though the Attributes palette shows it's set to use class. If I manually set the object to use class it works, but not if I simply assign the callout to the custom class. As you can see in the screenshot below, the Attributes palette even shows the correct class color (black), but the callout remains its original color (red). I haven't noticed this bug with any other object type. Callout test.vwx
  14. I ran into a somewhat similar challenge a while ago and received some great suggestions. Take a look at the thread below:
  15. I'm running into problems getting line types to display in hidden line viewports in Vectorworks 2018 (Windows 7 64-bit). In VW2017, if I setup a class to use a line type (dashed, dotted, etc.) it would display that way in hidden line viewports. In VW2018, objects inherit the correct line weight/color from the class, but not the line type. Attached example files in v2017 and v2018. Anyone know of a workaround, or is this a bug in v2018? Thanks for suggestions! Line Type test v2017.vwx Line Type test v2018.vwx