Jump to content

Edward Joseph

Vectorworks, Inc Employee
  • Content count

    77
  • Joined

  • Last visited

Community Reputation

10 Good

1 Follower

About Edward Joseph

  • Rank
    Apprentice

Personal Information

  • Occupation
    User Experience Specialist - Entertainment
  • Location
    South Hill, Washington
  1. Vision SP3 Crashes

    Ahhh, well that would do it.Vision crashes out intentionally to save your GPU from overheating, unfortunately the D500's that apple puts into the Mac Pro's are just renamed and tweaked W7000's from 2012. Super shifty, I know. Here is more info on that subject: https://architosh.com/2013/10/the-mac-pro-so-whats-a-d300-d500-and-d700-anyway-we-have-answers/ Being that it's basically a w7000, that puts is on par with a GTX 570 (if not slightly below) which is under our minimum requirements, see the FAQs pulled from espvision.com here: https://forum.vectorworks.net/index.php?/articles.html/articles/faqs/vision-faq-r7 Now on to solutions, because you can still definitely run Vision: I see a lot of fairly large entertainment files coming in at around 20MB, I'm not sure why your file is so large but it definitely has something to do with the crashes. Soft goods can be really taxing on GPUs as they get converted to a mesh so they interact with light properly (this is also why a final quality render takes a bit of time with lights in the scene). 11 of them is hefty for anything but higher end graphics cards. Vision converts everything to a mesh so light actually interacts with it, when it's in Vectorworks, it's just drawn with a Vector calculation (I assume that's where the name came from years ago) which is much less taxing. My advice - create a new class or layer (depending on how your file is set up) and draw some extrudes in place of your soft goods, then make your actual soft goods invisible. I then put a curtain texture on my extrudes of some sort, sometimes just a dark grey fill color depending on the use of the softgood. That usually works well for me when my GPU starts to get strained. As long as your truss is simple and square profile you should be good, round and smooth = harder working GPU.
  2. Vision SP3 Crashes

    Hello, Vision will crash out to save your GPU if it's being overtaxed. This is usually caused by a GPU that is under minimum requirements, or a scene with complex geometry. What GPU is in the machine that's crashing? Desktop or Laptop? PC or Mac? How big in MB is the Vectorworks file you're exporting from? Are you using manufacturer truss symbols or truss tool? What about soft goods? Those questions can help me narrow it down a bit. Also, for any technical questions, feel free to email us at tech@vectorworks.net for a faster reply.
  3. Set Default DMX provider

    Hey Pat, this sounds like a permissions issue of some sort - Vision does remember the last DMX provider. Is this a university computer? Or a mac? Possible explanations are: Deep freeze (or similar backup software used often in schools) deletes the config file nightly, causing DMX provider to revert to default. Mac permissions can be finicky (especially in schools as well) make sure you have full admin rights if this is the case. Windows guest accounts or limited permissions could cause this. The last one I can think of is some super picky antivirus could be preventing the config file from being written (but this is less likely)
  4. Vision objects in Spotlight

    @Rob Books That's awesome, I always liked the VW people but the low poly models of the Vision characters is too hard to pass up sometimes. We also have a set of misc objects like keyboards, drum sets, misc stage objects and whatnot.
  5. Vision bugs

    Hey Dan, the black box is easy to make go away, just turn bloom strength to 0. It looks crazy high in that video. Bringing down bloom strength, bloom light strength and upping bloom threshold makes that artifact go away. I remember tinkering with your file and not seeing the artifacting myself on a gtx 980ti, which should be about on par with the 1070 (i'd have to check my charts) so it's very likely it's a bloom issue. Try turning that down and let me know. Oh, and sorry for the delayed response! I was out all last week trying to buy a house!
  6. Vision bugs

    Hey Dan, The black box (or colored box) is a GPU artifact, volumetric amount (or even quality) could contribute to this for sure. Basically, it happens when the GPU sort of...gives up on trying to calculate it. What GPU do you have in this machine? the curved LEDs....that's maybe the weirdest thing I've seen happen in a long time. I'll run some tests and talk to our main fixture guy. Do you have them focused to a focus point on that person? I honestly didn't know fixtures could...bend like that. The last time I saw a backwards fixture was when someone was importing old vision symbols. Make sure to use vectorworks symbols to get the correct rotation -but if you're getting that issue anyway - let me know. We changed thousands of fixtures around when we combined symbol libraries, and there is a chance a few got missed. Feel free to send a message over to me at tech@vectorworks.net with maybe the VWX file and I can take a look as well. Also, thank you for explaining this so clearly - screenshots and paragraphs! Lastly - make sure you've manually updated to SP2 via:
  7. Vision bugs

    Hey Dan! I'll number my responses to keep things readable. Raising Bloom Threshold and lowering bloom light strength will also make this go away. Basically what is happening here is the bloom from fixture A is "blooming" fixture B, and B is blooming C, etc. So what happens is the area at the center is being told to be at 100% brightness , and then 150%....and then 200%, etc. We are looking into a few options, but the point at which it "overblooms" is dependent on GPU and Vision scene - so 1 computer will overbloom, and another wont (with the same dmx being sent). I was unaware of this one! I never thought to check since they come in rotated correctly. I can see how this could be troublesome when fine-tuning conventionals or something. Is there any other reason for needing the angle? Maybe we have some sort of workaround. Sure! Just open the patch window via Window>patch. Double click the unit number and change it, then hit enter. You can also change it in the fixture's properties window.
  8. Focusing lights

    Awesome, I noticed in Vectorworks, if I don't hit enter, it doesn't actually apply the focus point. As in, the fixture I have selected don't change it's direction in Vectorworks, until I hit enter.
  9. Focusing lights

    Hey Pat, I ran some more tests today and there is definitely some weirdness in that file. (1) I just dropped in a leko, went to edit, and changed focus to the focus point I made. The geometry snapped towards the focus point in VW, then I sent to Vision, the leko is pointing exactly where it should be. (2)Next, I tried adding 2 lekos, one unfocused, the other I Just typed a capital "A" into the focus field and hit enter. Hitting Enter snapped the fixture towards A. When I sent to Vision I get one pointed upstage (just the default position), and the other pointing stage right (where my focus point is). Are you doing something different?
  10. Vision issues/bug?

    Hey Bud, I've been trying to break things over here since I read your post. It does look like we're having an issue with focus - and engineering is aware of it so they should be working on a fix. - Prisms and animation wheels all sort of work the same way so on certain fixtures, the issue would affect those features. As for flat beams, this one is an easy fix! Just crank up Volumetric Quality. If you have it super low, beams will start to look like paper (for weaker GPUs) as you roll it up, the beam becomes more defined, and the particles in the beam become more fine, making it look much better. Adjust this value to where you want - balancing performance and quality, although I find in my main Vision rig I can just keep it at 100 - there isn't much of a hit really.
  11. DMX Connectivity Articles

    Ah, that's actually great news! What happened is, as soon as you made the connection, you must have been telling vision to turn on a bunch of lights, so it did it all at once. Vision will crash to desktop to save your GPU. Unlike video games, or something we can predict GPU load, we don't have any idea how many lights the user will turn on at once, so to save the GPU from overheating and well...melting, we crash out. Bring your lights to 0 and bring them up one at a time, and see if they respond. If you are crashing when just bringing up a normal amount of lights, you're probably running into a GPU limitation - our minimum is a GTX 580 or equivalent benchmark. More info here: Also, make sure you're not sending over any needlessly complex geometry. Vision is essentially running something between a fast and final quality renderworks 60 times per second, so avoid things like truss symbols (which model nuts and bolts for some reason), large amounts of soft goods (smooth = more polygons = more GPU load), and stage tool stages with the support posts rendered (you can't see them anyway). All of this is subjective, and I just trim what I need to depending on the show and my hardware.
  12. Generic Solid Resolution

    Hey Robert, Exporting to Vision will definitely take longer if those circles are just extruded. Converting to generic solid changes them to straight line polygons (decagons I think?). Basically, Vision takes whatever is in vectorworks and converts to a mesh (vertices specifically) and re-creates it. If you're not seeing a performance impact in Vision, use extrudes. Since you are using 2018, you can also convert them to meshes, then go to Modify>Simplify mesh and simplify until you get the performance you want. Just eyeballing your scene, I don't see anything crazy like soft goods, truss symbols or anything like that. You should be good, but let me know.
  13. Instrument focus, part ducks

    That's a weird one. What happens when you export without changing 3d orientation, still pointing straight up? Also, are you able to select the fixture in Vision and change Rotate X? Does it rotate as expected? Lastly, is the fixture attached to a lighting position or is it floor-mounted?
  14. No problemo! Nope, no specific IP address. They should be in the same subnet (i.e. Both 192.168.X or 10.0.0.X) but if you just leave everything to DHCP they will be by default. Luckily, most manufacturers seem to have done away with the specific IP addresses. But yeah, you've got it then, just tell the offline to send something and vision to listen for it (DMX>Change DMX Provider). If they're on the same computer, they just connect auto-magically.
  15. DMX Connectivity Articles

    Hey Mauro, I will write a new one, it looks like when we migrated to the new forums that article got lost somewhere. If you have an MA2 (or dot2) console, just plug it in, send artnet or sACN and change dmx provider in Vision to artnet or scan, that's it. If you are using ma2onPC, and are in a windows environment you can use MA-Net (ACT hasn't made a driver for mac). Download and install the MA driver from: http://www.actlighting.com/MA/software/utility/ESP%20Vision/gMA-ESPVision[3.100][6.800]-v1.220.zip Then go to Control Panel>Sort by icons> ESP – grandma driver. Change it to ma-net 2, and 127.0.0.1 if using ma on the same computer as vision, or the other option (it will be your computer’s Ip address) if sending across a network. Luckily the article that was lost is also the easiest one to explain. Give us a shout at tech@vectorworks.net if you have any trouble!

 

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