Jump to content

Mark Aceto

  • Content Count

  • Joined

  • Last visited

Posts posted by Mark Aceto

  1. 13 hours ago, line-weight said:

    We've been complaining about this for about 100 years now and very little has improved, in terms of fixing existing broken stuff, and making things more consistent. So I doubt much is going to happen in the next 100 years. @abshapi see this thread:




    Your experience is the same as mine - the closer you look, the worse it gets. It's become a familiar process - I decide to try out some tool that I've not really used before, because I think, let's invest some time in better understanding VW and taking better advantage of all it has to offer. After a day or so of investigation, in perhaps 75% of cases, I don't arrive at a point of "great, now I understand this and can use it to make my work more efficient" - I arrive at a point where I've figured out exactly which bits don't work at all, which bits of the interface are needlessly confusing, and often, that the conclusion is that the tool is effectively useless. Then I write a thread on here complaining about it, including often a quite detailed explanation of the problems (other posters do this too) there's a half-acknowledgement if I'm lucky, and hardly ever are any of the problems fixed.


    The door and window tools are the classic and most outrageous examples of this.


    Thanks for reviving that thread. VW is due for a maintenance release (not a rebuild).


    Meanwhile, Apple is long overdue for another 'Snow Leopard.'

  2. 1 hour ago, abshapi said:

    Speaking of Speaker Array; I cannot use a predefined symbol as apart of the array


    As Andy pointed out, the Landru version of the audio tools are capable of inserting symbols (and have been for over a year now). The functionality works and looks exactly as you'd hope. I take a Soundvision report from my audio engineer, and replicate it in VW. The Landru versions also have more annotation options for plating up your plots. And, as I'm sure you noticed, the developer is very responsive (vs waiting for who knows how long it will take VW to update the tools).

  3. 10 hours ago, halfcouple said:


    Hi Mark,


    I think I know what you mean, I always use child classes to switch to certain detail levels of presentation, for example switching of the decks of a scaffolding stage to show the underlaying structure or showing trusses only in their axis to project  their position on ground plans.

    Switching forward and backward these classes is always a question of mutiple clicks. My "tool of the day" for this is saved views that only contain settings for classes. By switching between these views you can keep the parent/child structure. Maybe this is what you are looking for ?






    Saved Views would certainly be a workaround but it would add as many clicks as it would save in the long run.


    Another similar workaround I've been entertaining is Filter Views but that hits a law of diminishing returns pretty quickly too.


    I'm really trying to work within the framework of how the app is designed / intended with a minimal amount of tweaking and fiddling, and just wondering if I'm missing a setting that's buried in some hidden document preferences menu (or even in hiding in plain sight but oft overlooked).

  4. I just watched the excellent Hidden Treasures Seminar presented by @BSeigel, and was thinking maybe there's a setting hiding in plain site that I've missed all these years... 


    See attached screenshots:

    1. Some Child Classes are set to Invisible
    2. Parent Class is set to Invisible to hide that entire department
    3. Parent Class is set to Visible to restore #1 settings (but overrides them)

    Is there a "nondestructive" way to change Parent Class visibility? The reason I continue to use Layers for Departments is because I'll have my Classes set to all manner of Visible / Gray / Invisible, so I can easily hide an entire Department by hiding it's Layer. Then, when I restore that Department's visibility, the Classes aren't affected.


    In addition to using VW the way it was intended (Layers are "where" and Classes are "what"), this also helps myriad other areas, like exporting to DWG.


    The goal is to have a proper Layer hierarchy like

    • Production Air
    • Production Stage
    • Production Ground

    Surely, there must be a way to do this that I'm overlooking.


    Screen Shot 2020-03-25 at 2.17.52 PM.png

    Screen Shot 2020-03-25 at 2.17.58 PM.png

    Screen Shot 2020-03-25 at 2.18.05 PM.png

  5. On 3/22/2020 at 2:16 PM, grant_PD said:

    I have tried this and it works well.  The advantage you gain in exporting the file to c4d and then opening it in c4d is that you can add other channels to the materials that VW does not support, like a normal channel.   VW will export all bitmapped channels like color, bump, into a tex file that Twinmotion can read from.  


    Sounds like The Human Cinemapede.


    • Like 1

  6. Twinmotion 2020 is out now, and available for $250 (half price) or free if you were already using v2019:




    It also introduces direct link (1-click synch) with Rhino in addition to ArchiCAD, Revit, SketchUp and RikCAD.


    Safe to assume the new release will be buggy until at least 2020.3 so save, save, save.


    • Like 2
    • Love 1

  7. 36 minutes ago, JuanP said:

    To answer some of your questions:


    • Lumion - Completed last year 2019

    • Enscape - Soon, good news. All I can say without getting into much troubles

    • Redshift - We are working on getting Renderworks "REDSHIFT Ready" for the 2021 cycle.  Even though this is not a realtime renderer per se, It is a faster RW rendering.  It will be a quantum leap for Vectorworks built-in rendering.

    • Twinmotion - We are working with Epic Games to connect Vectorworks with Unreal Studio, Twinmotion, and any other Unreal-based applications.  Ready for the 2021 cycle.

    "We are opening up our data connections so that all the work a user puts into a model can convey outside Vectorworks.  We are investing a lot in real-time rendering and connections to real-time rendering engines.  We are giving our users more options.  These new options will greatly speed up their workflows." - Dave Donley Director of Product Technology


    Dave Donley  will be covering these topics in more detail during the 2020 Design Summit April 22-24 in San Diego, California. 





    Surprised to see Twinmotion at the bottom of this list. I'm not mad; just disappointed (that Unreal can't get their sh*t together by SP3).


    Sounds like mid-March (aka SP3) for limited beta support from Enscape: https://enscape3d.com/features/


    Enscape system requirements for Windows or Bootcamp (not compatible with mac OS): https://enscape3d.com/community/blog/knowledgebase/system-requirements/


    @JuanP how long until the Update (viewport) button disappears from the OIP?


    • Like 3

  8. 10 hours ago, line-weight said:

    They don't have the time or brain space to learn multiple programs on top of everything else you have to keep on top of in architectural practice.


    In the hours and hours and hours and hours spent rendering in Renderworks, one could very easily learn another set of very similar tools. And ultimately save time in the long run. Not to mention that Cinema runs circles around Renderworks in both quality and speed.


    • Like 1

  9. This was posted on Facebook yesterday:




    The comments quickly turned to Redshift GPU support which is currently limited to NVIDIA. Does anyone know the roadmap / timeline for Redshift AMD GPU support (if at all)?


  10. 10 minutes ago, Tanner Shelton said:

    Currently with my workflow, I don't texture at all in Vectorworks. My only items in the resource browser has been symbols. I also don't light or even try to mess with cameras either. And then I do all lighting, cameras, and texturing in Cinema with Coronas material node editor and Corona lights. This way my Vectorworks file is a lot smaller, and others can work on my layouts without having all of the fluff slowing down their computers.


    This right here is how everyone should draw (although cameras are the only way that I know of to outsmart the distorted 3 point perspective in VW).


  11. @Tanner Shelton I'm following that Twinmotion thread like a hawk. Fingers crossed for SP3 TM live sync... 


    Renderworks aka "Cinerender" is just a ported (watered down) version of Cinema that's been gathering dust over the years. I totally get why it existed 10 years ago but if it were up to me, I'd remove it from VW altogether. It does not spark joy. #maintenance-release


    In 2020:

    • The only rendering that belongs in VW is OpenGL and Hidden Line
    • VW should integrate (sync not export) with as many thirty party rendering apps as possible


  12. 20 hours ago, Amorphous - Julian said:

    That’s really awesome to know @Diamond I’ll sign up to follow the news. 


    I’m open to getting C4D + REDSHIFT for our office, but than everyone have to learn another software (C4D) just for rendering our models, it would be so much better if a REDSHIFT plug-in was available for Vectorworks directly.


    Lets hope the guys from Vectorworks will shed some light on this.


    That would be a nice option for some users but for the rest of us, we don't want all of that entourage and all of those pixels ballooning our file size, especially if working in a shared project environment. That said, I don't believe Redshift offers a library of entourage objects (or textures) as it's meant to be a plugin to speed up GPU biased rendering. VW is the tool of choice for building the bones in the design layer, plating it up in the sheet layers, and using the data for everything from worksheets to Bracewurst. Leave the rendering (and entourage) to an external program like Cinema with plugins like Redshift (see also: Lumion, Twinmotion... ). The key word from your original post is "integration".


    • Like 1

  13. 23 hours ago, zoomer said:

    Depends on what realtime Raytracing is.

    Twinmotion or Blender Eevee do "screen space" Reflections/GI only to stay realtime.

    (a mirror won't show anything object behind the camera and such things)


    Blender Cycles is a real GPU renderer, which does real Raytracing and GI like VW RW.

    Still a GPU renderer with raytracing and faster than RW, but far from realtime.


    So far AMD had not the fastest GPUs overall (RTX 2080 TI) but attractive midrange cards.

    That may change soon ("big Navi"), beside that Nvidia's next generation is expected

    to be pretty faster again too.

    Not very important for Apple users as AMD is their only choice.


    AMD has a real GPU Renderer since years which is AMD Pro Render.

    But that is a real Raytracing engine like Cycles, VRAY RT, Octane, ..... so not for real time usage.



    For Real Time Nvidia offers an OpenCL, Vulkan, Cuda, RTX and Optix API.

    With these anyone can develop a Realtime Engine, using any or all of these.

    AMD offers all open standards but of course no proprietary Nvidia stuff like Optix, Cuda and RTX.

    Nvidia RTX API is necessary to use their RTX cores at all.

    If AMD will really offer another kind of special Cores for RT like Nvidia, that needs again a new special

    API to access these cores, isn't very important. Maybe they will do that raytracing compute work

    just do on regular cores.

    The only problem for AMD users would be if all developers would support only Nvidias proprietary stuff

    (no matter if that would be RTX or just Cuda) and nothing else (unlikely), or that Nvidia can offer

    much faster and more effective GPUs forever (let's see).



    But current GPUs are still years away from offering enough power for real Raytracing in Realtime.

    So currently Games with RTX can only choose to use one single raytrace feature - either GI or Reflections.

    And even though, activating that single RTX feature means 40 FPS instead of 150 FPS without.


    I'm basically comparing RTX 2080 Ti to whatever AMD plans to offer in the next year or so for those of us stumbling around in Apple's walled garden.

  14. 5 hours ago, zoomer said:


    Game Engines like Unreal can afford support for Metal.

    So I see not much  problems with Unreal on macOS/AMD in the future.


    Apple support may just have lower priority.



    AMD will support Raytracing Accelleration soon.

    Not sure if AMD will need or offer any special GPU cores, similar to RTX cores

    on NVidia. RTX also runs on NVidia GPUs that have no RTX cores.

    If such special raytrace cores are really faster than standard cuda cores for

    that specific task - than fine.






    My point is that Apple only supports AMD (after High Sierra), and AMD does not offer realtime ray-tracing. When asked about it in mid-2019, AMD pretty much dodged the question, so it sounds like we could expect realtime ray-tracing in 2021 (3 years after NVIDIA introduced it).


  15. 10 hours ago, grant_PD said:

    I would welcome TW as lumion style interactive real time window for working within VW.  After investigating the Unreal engine for a bit, it seems that TM is really just a very light version of Unreal, geared towards architecture.  

    And it does a fantastic job for exteriors, placing entourage and exporting video, hands down.  I realize how important that is for lots of users.  Just not for entertainment users.  


    I worked at a design team that used Unreal Studio (on Windows), and your assumption is fairly accurate. While Unreal Studio is far more powerful, it requires infinitely more tinkering to output the final product. That's where TM comes in by building a front end GUI, specifically for us (not gamers). While our renders weren't as polished as Cinema, they were literal screenshots.


    Also, to clarify, someone above used the term "baked". Real time does not = baked. Baking lights into a scene is more akin to what we've experienced in Cinema/Renderworks. That's also why one of the toughest things to render in Unreal/TM is atmosphere: smoke, fog, beams (of light). It always has that uncanny valley.

  16. January has become my new favorite time of year.


    It's worth noting that VW2020 didn't port the revolutionary Audio ToolSet 2 update from a year ago. And the stock text fields for LED screens are severely lacking compared to the original.


    • Like 1


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