Jump to content

Search the Community

Showing results for tags 'rendering'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Occupation


Homepage


Hobbies


Location


Skype

  1. I've just upgraded from VW12 to VW17. I am creating a 3D model, but I can't seem to make the colored axes disappear when I render the model. Since many most renderings don't have the axes, I'm sure there must be a simple toggle switch to turn off the axes, but I can't find it. Any suggestions? Thank you.
  2. I would really like to see some improvement in rendering directly on the design layer using Renderworks. For the longest time this worked exceptionally well. Over the past several years it has become buggy and unpredictable. Interestingly enough, the common response is “you shouldn’t render directly on the design layer. You should use a viewport on a sheet layer.” Frankly I find that a terrible solution. Of course I use sheet layers to output designs but during the design process? What a huge waste of time and it completely takes one out of the design head space. If you want to see how that new texture you created looks, or check the lighting you just added, you should simply start rendering. Since you are probably centered up on the item you want to evaluate, you only need the render to run for a moment and then cancel it once you’ve seen what you needed to see. The idea that you have to create a viewport and then set your rendering and lighting options and then render it from a sheet layer seems an absurd workaround. The render bitmap tool is not much better. You have to wait for entire thing to render before it displays anything. If you set the dpi to something slightly better than 72dpi, so it looks halfway decent it takes far longer. I get that I only should draw out the bitmap to the size I need to see, but it still takes longer than a quick keystroke to start a render. Rendering on the design layer used to work great all the time. It would be really helpful if that were the case now.
  3. Is it possible to render solar animations in the cloud - my desktop struggles to do high quality rendering at the best of times. Being able to send the process up into the cloud for processing would be awsome! Thanks, R
  4. Hello, I'm having a seemingly funky rendering issue across multiple files. I'm running VW Spotlight 2018 SP4 and am unable to render in Final Renderworks or as Custom Renderworks. Its as if the operation never starts and all my objects, symbols, etc. become transparent (as in they become invisable). Everything is still selectable and appears with an orange outline when selected. Also of note is that when I zoom in and out with the mouse, I am able to briefly see all objects crudely rendered. However, the moment I release the mouse when zooming to lock in a view, all objects revert to their incognito modes and disappear once again. Open GL rendering seems to work just fine. File uploaded below I cant find anything else about this problem on the forums, so I know I'm missing something. Or perhaps I'm just a victim of not enough GPU for VW? Any thoughts would be appreciated. Specs: MacBook Pro 10.13.6 (13-inch, 2016) 2.9 GHz Intel Core i5 8 GB 2133 MHz LPDDR3 Intel Iris Graphics 550 1536 MB Running VW2018 Spotlight Chandelierv1.vwx
  5. Hi, I am looking for a laptop (to work from home) that can handle vectorworks architect as I use it for rendering and 3D modelling. Can anyone suggest any laptops that have a suitable specification to do the job which are under £1000? Thanks in advance, Sam
  6. I am trying to produce a 3D model of my 2D plan. I have decided to take the 2D polygon hatch areas and turn these into Hardscapes. This has worked, but when I look at them in flyover mode they are only in wire frame, not solid. I only want them as white blocks. I think it has something to do with what class they are in, but I am completely confused.... I changed the Site-DTM-Modifier class to a white fill and then they all come in as black. Which I don't want, I want them in white. Thank You
  7. This is probably a question that has been asked many times before, but I have difficulty in accessing it, so here goes. The vast majority of our day to day work is to produce plans, sections and elevations to a standard that can easily be understood by clients, statutory authorities, contractors etc. I am not trying to produce photorealistic or 'high resolution' renderings on a daily basis - I actually don't want to produce a render, I would very much like Vectorworks to draw a set of lines that are representative of an elevation or a section and the ability to add some colour or detail without having to create an 'image' and worry about the resolution, the giveaway is in the name - Vectorworks - means lines, the name of the software should really be changing to Rasterworks as it is nearly impossible to produce vector drawings. The problem is that we need sometimes just to see what something is going to look like quickly and to produce an elevation or section from a model that shows just a modicum of colour or detail, is now so complicated that we as an office have all but given up trying to do it - doesn't look good when trying to run a business. How come that to generate the model in Open GL in the design layer, spin it around to my hearts content, zoom in and out, switch classes on and off, take screenshots etc. only takes seconds, but to generate the same level of detail in a sheet layer can take hours?? The real reason for this post however is because I am sitting at my desk trying to generate a set of simple elevations - taking 20 minutes each time because if just one thing is changed in the entire drawing, everything has to be generated from scratch again. And we wonder why other designers are continually mocking Vectorworks - ability to create instant and live elevations / sections. Live updates etc. Come on guys - what's the problem????
  8. Since the introduction of the current rendering engine, volumetric lighting effects, which are crucial to presenting concepts to clients in the entertainment industry, have been sorely lacking. This functionality is available in the rendering engine in Cinema4D but the necessary parameter controls are not available to VectorWorks users. There are several real time visualizers (Vision, Light Converse, MA3D, Wysiwyg) that produce results that are far and away superior to anything VW can do currently. Having to rely on other expensive and time consuming applications simply to produce this one crucial effect (which by the way worked much better in VW2010 and earlier) is a serious weakness to an otherwise great platform. For those that are not aware of the issue, I will explain it as this: 1.) A beam of light exiting a lighting fixture should appear to originate at the same dimension as the aperture from which it is emitting. In other words, If the lens of a lighting fixture is 8" in diameter, the origination of the beam of light should also be 8" in diameter. Currently the beam of light originates as a pinpoint. Completely unrealistic. 2.) A beam of light in nature follows the law of squares. In the simplest of terms, the light is brightest where it originates and then falls off in intensity over distance. Currently VW appears to deal with a volumetric cone of light as a piece of geometry. The larger the cone, the brighter it appears. The result of this is that the beam of light is then, in fact, dimmest at it's origination point and gets brighter as the beam widens which is exactly how lights do not behave in the real world. A program such as Vision produces both of these results quite well and do it in real time using OpenGL. Using the render engine in VW to produce volumetric effects takes a very long time and the end results are far from satisfactory. I am certainly not suggesting that OpenGL is the solution, however, it is unfathomable to me that a program as expensive as VW that markets itself to entertainment professionals is so completely lacking in a feature upon which a majority of those professional rely to sell concepts to their clients. Attached are images comparing the 2010 rendering engine to 2015. Nothing has much changed since 2015. The quality of the volumetric space is much more smooth and less granular than in 2010, but you can clearly see the difference the fall off. Also note that neither 2010 nor the 2015 examples address the aperture.
  9. Please see two screenshots attached below... The first image is a screenshot taken from a design layer in OpenGL, when orbiting the lenses remain clean and exactly how I want them to render. The second is taken from a sheet layer of a viewport, rendered in OpenGL only this time I get random artifacts appearing on the lenses of this particular fixture. My first thought was that there may be some overlapping geometry (although this doesn't explain why it renders correctly when in the design layer) regardless, I tweaked the position of this polygon but no success. I also played around with crease angle, removing texture, setting solid colour, various lighting settings, turning off ambient occlusion and DPI settings of the sheet. Any suggestions on a fix would be greatly appreciated. Many thanks Dan
  10. I have models created in Sketchup that I want to include in my Lumion file. Do I have to save my files a specific way to be able to explode imported models and adjust textures? I have had success doing so with some models but others have pieces that will not allow me to select textures.
  11. Hi All, Every time I try to render a section viewport VWX crashes. These viewports worked fine until sometime after upgrading to BIG SUR and probably after upgrading to macOS 11.1. These viewports render fine with hidden line, but I am trying to render them with renderworks background with hidden line foreground. I imagine this might be a RAM issue, but on my activity monitor my Ram is not spiking and I have plenty of ram available. Is there some sort of RAM govenor in VW 2021. thanks in advance for any help. -patrick iMac (Retina 5K, 27-inch, Late 2015) 3.2 GHz Quad-Core Intel Core i5 32 GB 1867 MHz DDR3 AMD Radeon R9 M390 2 GB
  12. Bernat

    Fabric

    Hi, is there a way to simulate how the fabric behaves? And by that I mean, for example, when it hangs from different points (think of two people holding a blanket, how you get the curve for the fabric and how it folds). Bernat
  13. Rendering locally on my computer would render fine but when rendering from the cloud, the image comes out mostly white. Is there a setting or something we're missing? It was previously working fine up until a few days ago and then realized I wasn't the only one with the issue. Using VW 2020. Below you can see rendered locally on the left and without changing any settings, the cloud render on the right.
  14. Just placed a bit of Christie Lites 7'10" F-Type truss in a drawing straight out of the VW library... As you may be able to see from the attached screenshot, when in OpenGL (or anything other than Wireframe) the truss does not render, however, is still there as it highlights when hovered over and is selectable. I did have other truss in the drawing that was rendering absolutely fine. I have also tried in a blank file and checked the 3D component to make sure that it's solid. Can't work out what's going on after having a good look. Any suggestions/help would be greatly appreciated! Many thanks!
  15. I think that a "re rendering" confirmation is needed before VW starts going to town on a custom render works setting. I can't tell you how many times I will be working on something after trying a rendering setting, and thinking I am no longer in a render mode and then all of a sudden, VW re renders because I switched views slightly or hit a button that starts the thing over. Then, of course, things start to get disjointed, pixilated, and my button clicks all lag to the point where I can even stop the rendering because my keystrokes don't register in real time and I can't figure out the magical key stroke to stop the thing. (escape escape I think). How about a pop up or some sort of giant red "STOP RENDER" button that is in an obvious area. Also, and perhaps more importantly, how about a "PAUSE RENDER" button also so I can look at other stuff when I need to keep working on things, and then hit resume when I have the time to go back to it.
  16. Hello. Anyone finding it hard to change the colour of glazing bars , and glass, on the Wasco Skylight "Ext Pyramid 350PHYG 1212 Slab" ? I downloaded this symbol fromm VWX libraries. Great detail. As expected it's several nested groups. At the core of these the glazing bar is a Generic Solid. Which seems not editable (Edit/greyed). I've experimented with class attributes, changing classes, etc etc. But black is the only option is seems? Wasco actually ship in various colour options. Any insights welcome. Thank you. VWX 2020, latest SP.
  17. I can't get my camermatch to work. It's always way off no matter how I put my reference lines. I've tried multiple reference marks and lots of different placements of the reference lines and I can't get it anywhere close. Is it just me or is something strange going on? CMA_Cameramatch.vwx
  18. Honestly, is this what one can expect from VW? Please have a look at the video attached. LINK TO VIDEO: https://photos.app.goo.gl/vCbW8r4R4SMqHK5d8 I'm doing a seating plan for the arena I'm working at. And the file isn't too complex yet, size around 50mb. I've also shot the Task manager as well, so you can stats while I'm cliking about. I'm not doing to much stuff here as you can see, but still really slow. Please let me know why occure and if there's some kind of fix to it. Many Thanks! INFO: VW 2020, SP5, 64-bit Windows 10 Pro CPU: Intel i7 9700 3,00GHz 16GB RAM NVIDIA GeForce RTX 2060 Super
  19. Hello, I am attempting to model some fixtures by a manufacturer using their IES files and finding that the light output in FQRW is highly unrealistic. Fixtures don't read at all until I manually set the lumen output to north of 2500 lumens (the environment being a very small office). The IES contained within has a lumen value of 261, which should read fine in a small environment. I currently have the Emitter in Lighting Options set to around 1,400% based on another thread I looked at, but am hoping there is a way to get more lumen-realistic output with these fixtures set at 100% so that I can provide the manufacturer with renders that even somewhat realistically reflect the actual light output of his fixtures. Any thoughts on how I can work these spotlight fixtures to create renders that are accurate to the actual details of the fixture/IES file and not just dialed in by eye? The biggest reason for this is that the manufacturer and I work remotely from each other and I don't always have the chance to use his new products in real life to get a visual sense of how bright they are in space and would love to rely on the data in the IES. Thank You! Office.vwx
  20. Is the Vectorworks University rendering course completely broken? The downloadable example file is in 2020 format, but the accompanying video appears to be referring to tools and operations that I find completely different in VW2020? For example, I have got as far as the rendering viewports example on a sheet layer. The tutor is asking me to select 'high quality render' in the 'resource browser' palette. Isn't the 'resource browser' now the 'resource manager', and if so, the 'high quality render' option is not one of the resources I can find. I note from the tutor's screen that he is using VW Designer 2016 - a software version that is now 4 years out of date. Isn't this module completely obsolete now? If it is, where can I find some up-to-date resources about this topic?
  21. I am looking for someone who can help me take a Vectorworks Architect small residential model and create realistic interior and exterior renderings. These renderings would be used in an advertising campaign for my firm. This would be a project for an independent contractor.
  22. Hi guys, I am trying to render in 3D using open GL but it seems I can only use the solid colour in the attribute palette but unable to choose an image. It does seem to upload when i choose one from the library in the resource manager. My layer option is set to show/snap/modify others and I use only one design layer so surely I must do something wrong? I can render the wall in solid colours but as you see the bricks don't show if I choose the image - Same for the roof! Can someone advise? I am sure it must be something simple which I have not figured out. Thank you
  23. The only way to preview grass is to click edit on the texture if you want to see it on a plane? Seems to me it would be very useful to see texture previews on whatever object type you want in the RM (as the editor does): Plane, Sphere, Cube, Flat. Can this be done / am I missing something?
  24. I've noticed that VW2020 sometimes hangs up when switching render modes, and the expected results are inconsistent. Sometimes, I get the spinning Mac OS ball (VW is unresponsive / hung up), and there's a long delay before the tea kettle displays and then begins to show progress. Since it works this way, it's hard to tell if VW is hanging up (freezing) or just taking its sweet time. I have a decent CPU/GPU and plenty of RAM. Finding these inconsistencies make the tutorial process really difficult because it's hard to know if you're doing something wrong or the program is behaving badly. At the end of this trial and error process, I took Jim's render styles and followed the same debug example below with a very simple file (4x4x4 cube on a small slab and a single light). Everything behaved as expected. So either VW has issues with rendering bigger, complex files, or Jim's tutorial file is bugged somehow. For file consistency and to make sure I'm testing the same situation, I am using an exercise file from the "Rendering in Vectorworks" tutorial, filename "02-renderworks-camera-effects-v01.vwx". The Renderworks styles I refer to (I.e., "Quick" and "High Quality Render" are styles that Jim is using in the tutorial). I am going through the Renderworks modes in Design Layers (not sheet layer viewports). For Fast Renderworks, this doesn't seem to be an issue, but for Final Renderworks, Artistic Renderworks, Hidden Line, Dashed Hidden Line or any of the Polygon settings, there is an issue for render progress and render behavior. If I select "Fast" and then switch to "Final", the tea kettle displays for a moment and then nothing changes. Similarly, if I go from "Artistic" to "Fast" or "Final" nothing changes. If I go from Fast --> High Quality --> Final it works as expected, even if I interrupt High Quality and force a switch to Final. If I work this way, the Final render only takes 30 seconds. Switching to or from hidden line always seems to hang up VW. Other modes hang up based on what mode is currently active. Debug Example: I'm in Open GL and I switch to Renderworks Style --> Quick Render - it works as expected, immediate tea kettle and it takes 43 seconds. Correct! I'm in Quick Render and I switch to Hidden Line - it hangs up for a couple minutes and the render doesn't tell me how long it took. But crazy that it takes longer than Quick Render. Doesn't display "Rendering Complete" text. I'm in Hidden Line and I switch to Renderworks Style --> Quick Render - it hangs up for a couple of minutes and then the render says that it takes 44 seconds. Hmm. I'm in Quick Render and I switch to Fast - it works as expected, immediate tea kettle and it takes 04 seconds I'm in Fast and I switch to Final - it just stays in "Fast" even though "Final" is selected I'm in Final (but it's displaying as Fast) and I switch to Renderworks Style --> Quick Preview - it works as expected, immediate tea kettle and it takes 51 seconds. I'm in Quick and I switch to Final - it works as expected and it takes 45 seconds. Correct! It seems that depending on the file I'm working in, the Final setting has different behaviors and different results. An update tutorial to how the different modes function in VW2020 would be extremely useful. For now, I'm going to use my really really basic file and try to go through Jim's tutorials that way. I sort of expect that there would be some kind of render cache somewhere that needs occasional cleaning for optimization purposes. Could that be it? Or am I fundamentally misunderstanding how rendering works in VW? QA issue? I don't know. It's great that there's a time / progress bar as well, but like the hang up issue, whether or not it functions as expected is inconsistent. Would be great if it showed "Time Remaining" as well...
×
×
  • Create New...