Jump to content


Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Community Reputation

118 Spectacular


About bbudzon

  • Rank

Personal Information

  • Location
    United States

Recent Profile Visitors

1,421 profile views
  1. Yes. Vision 2021 has moved to OpenGL 4.1 and we weren't able to get the text overlays working properly. We also found some bugs in the reporting, which I believe have been mostly corrected (but since the reporting is no longer public, this information is internal only). We had a very rough POC for putting FPS into the status bar (near the NDI status bar indicator). This is much simpler to achieve than a text overlay in the viewport, but does come with the downside that it is a single FPS counter for the entire program (and not an FPS counter per viewport). There are obvious ways we could remedy this (the most obvious being adding an FPS counter into the statusbar for each visible viewport, with some identifier as to which counter refers to which viewport). It would definitely be interesting to hear from users here on the forums if they preferred the text overlay on the viewport, or if a status bar counter would be sufficient. Alternatively, and the current suggestion/workaround, use a third party application for detecting FPS of Vision.
  2. Vision does not support transparency/translucency textures for meshes/geometry. However, we do support alpha mask images which we have leveraged to get the most out of Vision. If I had to get creative texture wise to do a frosty glass, I'd probably do something like we did for the skrim in our 2021 demo file (included with every Vision 2021 install). This technique gives you a color (in this case, most likely white for frost) but uses alpha masks to put "holes" in the material, allowing some light to pass through (depending on the size of each "hole" and the shadow/light quality settings). You can play with the image used for the alpha mask to adjust hole size. You can also leverage Vision's texture scaling. Getting transparency/translucency in Vision is definitely something we'd like to get done. It does take a fairly large reworking of the rendering engine. Hopefully, this little tip will help you in the meantime! (Part of what we are still performing in regards to transparency/translucency is competitive analysis as well as better understanding how our customers want these things to work. If you want to be able to shine a white light through a stain glass window, in real time, and get a stain glass beam of light on the other side of the glass... that gets really really expensive and I'm not even sure would be possible in real time if there were hundreds or thousands of stain glass windows.)
  3. Ohh! One thing I totally forgot to mention (as it's kind of a "hidden" by designed feature, imo) is there is a menu command under Render called Reset Video Inputs. When a file loads normally and successfully, this menu command spawns a dialog which prompts you to select a video input texture for which you would like to choose a new video input source. However, when we fail to find video inputs at load time, this menu command "re-triggers" the events that would normally happen at file load time, in regards to the loading of inputs! So, you may have stumbled into that code somehow. My guess was that the crops were properly written to the file, but we were just failing to recreate them somehow. Failing to remember this somewhat "hidden" feature, I hadn't considered that running the "Reset Video Inputs" dialog *may* get things to work (no promises hahahh). Either way, I seem to have gotten your DM. I'll try to find some time to look at it and hope that this information has helped.
  4. This is all very good information! You may very well be on to something with this only happening in files with many many crops. I'm not sure how well this scenario has been tested and your file would be greatly appreciated! Post here or DM me. It may help us narrow things down better, especially if your files exhibits the issue on our machines in-house. I do not have too many more suggestions as to how you may proceed with this many crops. One idea might be to try lowering a lot of your application document settings. Perhaps if we free up some resources it will help, although it unfortunately does not seem likely. I just realized... it might be interesting to see how 20 crops of 1 NDI stream (1:20) behaves differently than 20 crops of 10 NDI streams (1:2). Perhaps, if there are not so many crops for a single input, it will work better?? 🤞 In regards to the crashing, this may very well be tied to the file being large and your settings being too high. Specifically, your GPU being ~30-40% and CPU ~20% only indicates how much work they are doing. It does not indicate how much RAM is available/free. If the GPU runs out of VRAM, it would crash the program using the most VRAM, which in this case would be Vision. So, since we are concerned with the GPU primarily, while it is good that it is not pegged at 100% work, it may be that you have run out of VRAM given the size of the scene. One of the biggest VRAM consumers is shadows. Disabling them (or at the very least lowering the shadow quality) will lower VRAM requirements. Similarly, lowering the Resolution Quality will reduce VRAM requirements. You can try running at Texture Quality Medium/Low, as those also use less VRAM than their higher counterparts. My very general suggestion when it comes to tweaking performance/quality settings is to start with lower qualities (read; higher performance) and add in more quality where you find it is possible. Again, hope this all helps and very sorry that your experiencing these issues!
  5. If you are concerned about the forums not accepting a large file, dropbox or something may also be used. If you are worried about keeping the project private, I believe you can attach the file to a DM. Again, if the file is too large for the forums, you could upload to dropbox or something and DM me a private link. Are you able to reproduce this issue in a new unrelated test file? Perhaps, your file is not even needed. Ideally, we could reproduce this issue "from scratch".
  6. I'm not sure I've seen this issue before but there are definitely some oddities in the screenshots above. For starters, note that in the second screenshot the Video Inputs that could not be found seem to all be a Crop; more specifically Crops of NDI streams. The fact that no NDI streams are showing up as "no signal" in this list implies that Vision found the NDI Stream properly, but is somehow failing to find the Crop (which doesn't make much sense). This is also confirmed by the first screenshot, where the NDI stream is present. The big red flag to me is in the first screenshot. It appears that when Vision tried to recreate the crops from the NDI stream given the information in the V3S, it somehow created a "Capture" (UVC device) instead of a "Crop". If this did somehow happen, I imagine it would result in Vision thinking the Crops are "missing". I'll obviously want to try to investigate this more internally and may also ask here for additional help in finding steps to reproduce. But, for now, I'm hoping we can get you past this issue and at least provide some kind of workaround 🤞 First and foremost, please ensure you are always on the latest version of Vision and Vectorworks. One thing you may consider trying is unplugging or disabling any UVC devices (web cams, capture cards, etc). Similarly, plugging in a UVC device may also alter the behavior in such a way that things manage to work. You also stated that when opening an older file, the crops load. But, when this is saved to the desktop and opened again, the crops are missing. I'm curious if you open that file on your desktop where the crops are missing, and you recreate just two or three of the crops by hand again; what would happen if you saved this to a new location and opened that? Does it still fail to load the crops you did recreate? It may be that somehow this could "reset" the crops storing in the V3S and start working again moving forward? I'm not sure if it will be possible to work around this issue or not. But, either way, I appreciate you bringing this to our attention. Hopefully we can nail down what is causing this and fix it such that others do not run into this issue in the future. Any information you may be able to provide in regards to how this may be reproduced (including whatever may be necessary to create the initial file) will be incredibly helpful!
  7. I believe the ability to store the crop for every screen was added when NDI support was initially released for Vision. I just ran some quick tests against Vision 2021 SP1 and it seems to be behaving as I'd expect. I opened a test file I had lying around. Set one screen to the entire NDI stream (no crop). I set the other screen to a crop of the same NDI stream. I then positioned the camera such that both screens were easily viewable and saved the V3S. This is what my screen looked like before the save: As my NDI server was still sending NDI data, reopening the V3S in Vision resulted in the following dialog: Clicking Ok, the rendering was as I'd expect and the screens "automagically" picked up what video input they should be displaying: FWIW, if for any reason a video input cannot be found when opening a V3S, the following dialog should display: I got this dialog to spawn by closing my NDI server and loading the same V3S from above. As you can see, Vision has spawned a dialog stating that it is trying to connect to the video inputs mentioned (and it will keep trying to find them "automagically" until you click cancel). If I decide to not work with NDI/Crops for now, I can click cancel. Otherwise, starting my NDI server allows Vision to find the proper NDI stream and it's associated crop. This "search" is performed live and no action is needed on your part other than starting the server that sends the output. These video inputs are then applied to the proper meshes in the scene the get the renderings I've shown above. I hope this helps!
  8. correct the builder is currently PC only Just to be clear, the GDTF Fixture Builder is available at https://fixturebuilder.gdtf-share.com/ for both OSX and PC. Accessing the fixture builder from inside of Vision does, indeed, only work from PC, however. EDIT: at the moment the MVR format doesn't support Spotlight focus points or focus information Also, focus points should work with MVR when going from VW to Vision so long as the version of Vision is 2020 SP2 or newer. There was a bug introduced in Vision 2019 SP3, that we were able to ship a fix for in 2020 SP2 😉
  9. I've found the issue and the code and am working on getting it resolved. I'll try to post here when we are able to get the fix into a public release.
  10. Any data assigned to the Gobo/Color/Animation Wheels tabs VW-side I would consider to be "custom data". This data only works with ESC, not MVR. If using GDTF with MVR, you can customize the GDTF using the GDTF Fixture Builder. Simply insert fixtures in VW using the insertion tool, assign ETC Source4 19 deg Fixture Mode, click Edit, click Color Wheels, assign a custom color, export ESC, open ESC in Vision, select Fixture, verify custom colors appear in Vision Properties Palette under Color Wheels section. I think you have the current workflow figured out. I thought that multiple selections worked with Gobo/Color/Animation Wheels, however I'd have to verify this as I vaguely remember this deficit being pointed out before.
  11. So, in my tests, I was able to send an ESC to Vision and the colors came over as expected. I was, however, able to confirm that it seems like custom colors are not properly saving to V3S. Hopefully, we can get ESC's working for you and you can manage with those until we can investigate/fix the V3S issue. My apologies for the issues you're experiencing and my delay in response! Untitled.esc Untitled.vwx
  12. Yes, my apologies. If no camera is present, Vision will not "violate" any privacy. However, when a camera is present, Vision must be given access to the camera. If it is not, Mac OS will see it does not have permission but is requesting it anyway. Mac sees this as a privacy concern and forces Vision to close. Glad you seemed to have gotten things up and running 😉
  13. MVR, unfortunately, does not yet support transferring of custom gobo/color/animation data; whether using Vision's native fixture content (litfiles) or GDTF. If you want custom data in a GDTF, the GDTF Fixture Builder should be used to generate a new GDTF. However, I think you were on the right track with the use of ESC as the workflow is a little simpler. Let me just start by saying, I don't think you're doing anything wrong. It seems you're filling out the Fixture Mode properly, which allows you to properly assign custom colors Vectorworks-side as you have done. If this is not working, it seems like it is a bug and I can start to investigate. Similarly, it is odd that the focus is saving for your conventionals in Vision but not the colors. Using the V3S format is even harder to "screw up" from an end user standpoint, and should always "just work". It seems like this may also be a bug. I will look to reproduce and start investigations. We made some rounds of major reworkings for performance improvements with 2021. So, it may be that this is somehow a result of that. There may be a (fairly elaborate) workaround, if needed. But, my hope is that we can find out what is going on and either resolve things in the code or relay some information that should help resolve the issue. My apologies and I hope to be able to provide an update sooner than later!
  14. Would you mind creating a DMX Recording in Vision 2020 where it works? If you attach that DMX Recording and the V3S to this topic, I might be able to look into it a little deeper 😉
  15. As we've looked into it more and more, it seems SLI is going to be a thing of the past for nVidia. They are dropping support on almost all of their newer cards and the ones that do support it require code to handle it (whereas before the card handled SLI for the code). I have not yet heard back from our technology department on whether or not we have equipment to test. The last test we performed in house was on 2x1080Ti's, but one has died since. So, while I still cannot help much in regards to SLI, based on your post above you may find this helpful. Here is a list (in rough order) of application/document settings that impact performance in a significant way in 2021: Enable Shadows (shut this off for a big leap in performance) If you MUST have shadows on, consider turning them off globally by unchecking Enable Shadows and consider turning them on at a per mesh/layer level. Haze Texture Intensity; not to be confused with Haze Intensity (set this to 0% to disable 4D haze and get a big leap in performance) Haze Style (HQ 4D is usually best, but make sure you’re at half resolution and not full) Resolution Quality (esp when you are fullscreening Vision, setting this to something reasonable like 720p is ideal; the lowest value you can put up with is usually the sweet spot; I run 768x576) Haze Quality (the lowest value you can stand the better; I run 0.01 or 1%) High Precision (I recommend turning this OFF) Render Fixtures (I recommend setting this to OFF or Black)


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