Jump to content


Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Everything posted by bbudzon

  1. Hello all, There has been a slew of problems surrounding video capture cards and Vision. A large part of this is due to the number of manufactures that are out there and the number of proprietary drivers required. Some capture cards explicitly state that they only work with certain software suites. We have been doing a lot of investigation into the capture code to figure out why some devices were working and some weren't. As it turns out, this was more a matter of how the operating system handled the capture device rather than how Vision handled it. What we have found, and tested to a limited extent, is the requirements you should look for in a capture card. First and foremost, all capture cards must be supported natively by Window/OSX; meaning no drivers are required (they can be recommended, just not required). The way these devices work is through a universal driver for video capture called UVC. UVC drivers ship with Windows and OSX so again, no installation required; UVC ships with your OS. Lastly, video can be output in several formats; RGB24, RGBA32, ARGB32, ABGRA32, UYVY422, YUYV422, YUV420P, H264, MJPEG, and many more. Currently, Vision only supports YUYV422 and YUV420P. Once we were able to determine what the Operating System's requirements were for video capture cards, we were able to make educated guesses as to which devices may work. We happened to have a AV Bridge MATRIX PRO lying around (http://www.vaddio.com/product/av-bridge-matrix-pro) that we were able to determine supported UVC. We weren't sure what pixel format it was sending out, but we decided to give it a shot anyway. Turns out, it worked!! We will be purchasing more cards over the weekend that we believe meet the Operating System criteria to test them out. Once we have those cards in house, we should be able to determine that most (if not all) UVC compatible / YUVY422 capture devices will work with Vision.
  2. Agreed, @DBLD. The issue @LJ TMS is talking about is a known separate issue that tickets have been opened against.
  3. Outstanding! Thank you for the report and hopefully we can continue improving the product with future releases and SP's! Btw, Vision 2019 SP1 shipped with quite a few fixes in it as well. Take a look!
  4. bbudzon

    far clip plane vs look at distance

    I think this furthers the point that most users won't need these settings. I really like the idea of having presets ship with Vision, and furthering that - fostering a community for Vision in which people share their presets with each other. Spoilers Below: Something we did in the code that probably slipped through the cracks is portability of presets. Every time you save a v3s, we store off the document settings. Every time you open a v3s we restore those document settings. Simply open a friends document, go into the document preset dialog, and save off their document settings for later use 👍 Here's where it gets a little more interesting... we also store off the application settings in the v3s despite the fact that they are ignored when opening the file. We did this, for one, because it helps us with debugging customer issues. But, we also did it so that you can easily share your application presets with a friend! Simply copy their v3s into your Application Presets folder (you can rename it to something more appropriate/contextual) and it will now appear in your Application Presets drop down. Arguably, this is less helpful as the point of Application Presets is to be more specific to the power of the computer. But, this allows individuals with similar machines to share application presets which is a powerful thing for end users. I literally suggested that we write the code this way to encourage community and sharing 🙂 I will say this portion of the code probably has gone slight more untested, so consider it an easter egg feature 😛 (On OSX the path to the preset dir should be: ~/Library/Application Support/Vision/2019/AppPresets) (On PC the path to the preset dir should be: C:/Users/<USER>/AppData/Roaming/Vision/2019/AppPresets)
  5. Hello all, There have been a LOT of new settings (both document and application level) added for Vision 2019. We spent a lot of time updating the help documentation so that you can adjust them when necessary. But, perhaps people are having to adjust them more than they'd like. What we'd like to do is poll everyone for their most commonly used Application/Document Settings in Vision 2019. We will go over these and come up with some internally as well to ship as Presets for a future Service Pack. Some example presets might be as simple as High Quality or High Performance. Others may be as complex and as contextual as Night Time Rock'n'Roll Medium, Day Time Corporate Event High Quality, Large Indoor Venue High Performance, etc etc. The advantage of doing this is that many users will not need to care too much about the different settings and what they do. They can simply select from a list of descriptive presets that seems appropriate for their file. Thanks for all of your help!
  6. bbudzon

    far clip plane vs look at distance

    It does effect flyover but very little. Pan is somewhat effected (def more so than flyover). The one you want to be playing with is zoom (ie; mouse wheel).
  7. bbudzon

    far clip plane vs look at distance

    @VClaiborne Not quite but you're getting warmer. This is an extreme example to prove a point, but set your Push Looked At Distance to 1.0 (I believe it will go this low). Now, try to use your mouse wheel to get across the room. It will be very VERY difficult. Now, try the same thing with Push Looked At Distance set to 1000.0. You will notice the mouse wheel now moves the camera much more quickly. Edit: I wasn't done with my post but the enter key wasn't working and somehow posted this! Edit 2: The last thing I wanted to point out was that we picked a default value of 90.0 because it seemed the most reasonable and worked in almost all cases. Unless you are having problems with not being able to get close enough to something (ie; you should lower the Push Looked At Distance) or unless you are having problems with navigating too slowly (ie; you should increase the Push Looked At Distance) then you likely won't benefit from changing this from the default value of 90.0.
  8. bbudzon

    far clip plane vs look at distance

    All settings in Application Settings stick from document to document. All document settings are reset to defaults on new documents. I am getting ready to make a post in the general vision section about what presets users would like to see and what they are finding useful. Please make sure to contribute to that thread as hopefully it will spark discussion. I can talk with Tech Pubs about updating the help with better examples 😉
  9. bbudzon

    far clip plane vs look at distance

    We've worked really hard on getting the help documentation up to date. Here is an excerpt: So to summarize: - Push Looked At Distance is a way to make the camera tools interact the way you want them to. Small numbers mean you can get closer to objects, but this can make large motions take longer. Larger values mean you can't get as close to objects, but large motions will be faster. We decided on 90 as a default. I often use 300 unless I'm trying to get close to a fixture or scene object. - Far Clip Distance should always be set as small as it can be as this improves shadow quality, even if only slightly. I recommend zooming out as far as you would ever want to (given your current scene) and lowering the far clip plane until it starts to "cut out" geometry. Bump it back up a little bit so it's no longer clipping. That's the sweet spot, which is contextual to every document you create. Generally speaking, unless you find a need to adjust either of these, there isn't a need to adjust it! I know that sounds oxymoronic but some of these settings were created for the edge case where a customer really does need a radically different value than the default.
  10. bbudzon

    Fixtures not Showing Up?

    Are you using the CDM or Tungsten Nexeras? And are these the Wide Nexeras?? I may not be able to help as much with this one, but I would try clicking Help->Update Libraries to ensure that your copy of Vision has the latest content 😉
  11. bbudzon

    Vision 2019 first impressions and questions

    I think we may have found an elegant solution to the colors not coming over properly such that it wont need to be reworked later. We are testing the fix out in the beta. Assuming things go well, it should make it into the final SP1 release.
  12. Hey Dan, We found a pretty serious bug in DMX just before SP0 release and were able to get a fix into the initial build. Have you had a chance to test Vision 2019 SP0 to see if this issue still exists? It may require a new file as the bug may have been stored off in the v3s (the esc should be ok).
  13. bbudzon

    Beams going through walls?

    Glad to help! You are right about the menu not being called Application Settings but we will refer to the settings in that menu as Application Settings because they are stored in the Application and NOT in the Document. Similarly, Document Preferences (such as Render Shadows) ARE Document Preferecences and therefore will be stored in the v3s. When you email Vision files to others, the Document Preferences will carry along but Application Settings will not as they are set on a per user basis inside the Application itself. (This is similar to how VW handles Application/User Settings vs Document Preferences.)
  14. bbudzon

    Beams going through walls?

    On OSX, you can click the Vision menu and then click Preferences (on PC it is Edit->Preferences). You can also use the default OSX keyboard shortcut that is used by all applications on OSX: Command+, (note: this keyboard shortcut does not exist on PC). If you were unaware of this menu, make sure to check the help documentation, as well. There is a LOT of good stuff in there and you should try to understand all of these settings as they have direct impacts on performance and quality. The settings that impact performance the most (and in order of importance): Resolution Quality Volumetric Quality Render Fixtures (with large number of lights) Shadow Quality Texture Quality Dynamic Shadows (should almost always be set to "Objects", which should be the default) We tried to ship mostly sane defaults here, but feel free to try these settings out and store them off as presets.
  15. bbudzon

    Beams going through walls?

    I think I know what's going on. Go into your application settings (not document settings) and make sure Dynamic Shadows is set to "Objects".
  16. bbudzon

    Beams going through walls?

    The "Enable Shadows" document preference is now disabled by default because (you'd never believe me when I say this) most people don't notice they are off and the performance increase is astounding. Simply select ROOT and check the "Render Shadows" check box 😉 One last note (kind of tying in to what I said earlier), if you can run in realtime without shadows it will run WAYYYY faster. You can always toggle the shadows on and off in realtime mode to see what you need to see when you need to see it. I would recommend always enabling shadows for Rendered Stills and Rendered Movies.
  17. bbudzon

    Vision 2019 first impressions and questions

    I apologize deeply as it was not known that this workflow was so popular. When we redesigned the rendering engine, this was not taken into account and it slipped through testing because we weren't aware it was truly being used in the first place. There was also some confusion in house as to whether or not this workflow was possible in 2018, which it is now obvious that it is. The temporary workaround is to make a small texture that is the color you want, and apply that to the object. What I'd like to get done in the code is the automation of this, although the end result is the same for the user. The real solution involves using actual color, but again, with the way the rendering engine was re-engineered for Quality/Performance, this is no longer an easy task. About the VWX, there actually wasn't one. One of the new features of Vision is the ability to import new formats such as OBJ. The Sponza Model was created by a video game company called Crytek. The light plot was simply copied over from the Vision 2017 Demo.v3s. One cool thing we did to expand upon the textures in the Sponza model was to use a program called CrazyBump. This application takes a simple diffuse texture and does its best to create bump maps/normals maps/specular maps. This will NEVER be as good-looking as a baked model in, say Blender. If you are unfamiliar with the concept, I am only vaguely aware of how it works but let me try to explain. In some 3D modeling program there is a concept called baking. What this means is you create a extremely high poly count model and a fairly low poly count model. You can then feed these two meshes into a function that will bake the high poly model onto the low poly model. The result is normal maps and bump maps (I believe). This allows you to use the low poly model, while retaining VERY high quality renderings. Look at the lion in the sponza model, for example. If you had to guess, you would think it would be a very high poly count model. But if you enter wireframe mode, you would realize that it actually has hardly any polys at all. Not only is this good for performance, but it looks good too! The reason this is possible is due to normal maps (in this instance, no bump is applied). I hope all that makes sense. I'll ping @Edward Joseph and @Mark Eli as they may be able to correct any mistakes I've made. EDIT: I found the link to the original OBJ that we downloaded. Had to crawl the web archives because the site/model has since been updated. Here is a link to the old site/model that we originally downloaded from: https://web.archive.org/web/20180202205437/http://www.crytek.com/cryengine/cryengine3/downloads Here is a link to the new model, if you wish to download it and try to pull it into VW/Vision: https://www.cryengine.com/marketplace/sponza-sample-scene
  18. bbudzon

    Blackmagic Intensity Shuttle

    Unfortunately, I do not believe this is a UVC device (ie; will not work with generic programs like Skype). Vision requires UVC capture devices. If you can get any additional information about UVC support and supported pixel formats, that will aid us in giving you a for sure answer. FWIW, CITP and NDI are on the wish list 😉
  19. bbudzon

    Color Scrollers in Vision

    Attachments are actually broken in Vision and will take quite some time to fix. They are on the radar, but we need more reports to raise the priority. So for that reason I thank you! The more reports we get the more likely it is that we can solve the problem and the more likely it is that we can gauge our users come time for enhancement requests. I know this is far from ideal, but the closest we can get you to a color scroller is to leverage the extra color slots available in S4. You can adjust each color slot individually from the Properties Window. Yes, I know a S4 doesn't necessarily have this many gobo/color slots but it allows for a little extra flexibility when you run into a bug like this.
  20. bbudzon

    Saving global properties

    I'm catching up on this topic, but a lot of the concerns seem to be related to settings and saved views being lost. There also seems to be some commotion about bidirectional communication and/or Vision's Integration into VW. As far as settings and saved views are concerned, the intended 2018 workflow in this forum posts context would be: Prepare VW document Send to Vision for first time ...work... Now you need to update the Vision application with new VW changes without losing settings and views So, save a v3s in Vision This should store your saved views and global settings In VW, export an ESC with only the updated information contained in the export In Vision, delete the geometry/fixtures you are getting ready to update In Vision, merge the esc in to pull in your VW update Verify your saved views and globals in Vision are still in tact If this is not working as described, we can check to make sure bugs aren't already opened and open them. For the bi-directional communication and/or Vision's integration into VW; both of these are things that are discussed regularly in the office. It is an issue we are aware of and one we are hoping to find a solution to. GDTF/MVR may help solve a lot of these issues down the road.
  21. Thanks Dan! I got your email, downloaded your files from dropbox, and will take a look into the issue!
  22. You can email me directly at bbudzon@vectorworks.net 🙂 Thanks again for your report, gives us a better starting point! Just to reiterate my point, the more details you can give us about this file the better. What fixture was breaking? What was it's unit number? What are some of the DMX Addresses Vision has "burned"?
  23. This is a VERY detailed write up. Thank you very much for you investigations into this issue. We have had similar reports in the past, but never with this level of information. Hopefully with this added knowledge, we'll be able to tackle this issue once and for all. I'd love it if you could post your files and any additional information you may have such as what specific universes/addresses are hosed and the unit number of the fixture your having problems with in your file. It may also be beneficial to contact technical support and have them open a ticket for you if you don't have the ability to create one yourself in JIRA.
  24. bbudzon

    Video Capture Cards in Vision

    We have posted a Tech Bulletin which should hopefully answer some of you system requirement questions. I'd also refer you to the online documentation for workflow related help. http://www.help.vision.vectorworks.net/ Capture cards are what you want to search for and it all starts by assigning a capture texture to a MeshShape. Hopefully this will get you started. http://app-help.vectorworks.net/2018/Vision/index.htm#t=2018_Vision%2FVision%2FSpecifying_Textures.htm%23XREF_12646_Specifying_Textures&amp;rhsearch=capture card&amp;rhsyns= Lastly, Vision does not currently support CITP, but it has been highly requested feature; along with NDI. The best way to get multiple inputs into Vision is through a multi-input capture card, multiple capture cards, or a single hdmi feed that combines video into a grid form. Once Vision sees this single hdmi grid feed, you can crop it into individual live video streams.
  25. bbudzon

    Crash - Cameras

    Hey Richard, I apologize for the inconvenience. It appears there are some bugs in this code that had not yet been reported. So thank you for your feedback and we will look into resolving this issues asap. The cameras will take a little bit more work on our end to fix than the ambient, but I can at least give you a work around for the ambient in the mean time. It appears ambient is causing issues when it tries to update the Global Properties UI with the new DMX value. What seemed to work for me was selecting anything other than ROOT in the Scene Graph Dock when adjusting the ambient this way. (Since the Global Properties are only visible when ROOT is selected in the Scene Graph, selecting something else so the Globals aren't displayed works around the issue.) Thank you again for running through the software and reporting these issues to us so we can resolve them.


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.