GTHORN

I appreciate the response! I have 0 idea why the shutters aren't working, as I've been following the same steps that I've done in the past. I may just have to ignore it unless someone has any additional ideas?

Anyone else had this issue? I didn't set any shutters within VWX itself, as I wanted to wait and do it within Vision. But, when I brought up the channel and software console, the shutters aren't responding at all. Also, for some reason, the unfiltered lights are appearing deep red. If I connect to an actual console over sACN, I can bring them up and down to make them change the color temp back to normal, but then they will often overcorrect and go cooler than an actual incandescent. This seems SUPER buggy. Does anyone have any advice?? Thanks! Greg

Hello all! Recently, I've started to dive into the renderworks side of things. Today, I tried dropping multiple basic lighting tools into a document to light a basic extruded rectangle, and the software crashes either after dropping the second light, or if I use the flyover tool. This happens in both VW20 and 21. I have made sure everything is updated, and it continues to happen, which is increasingly more frustrating. Any thoughts? Thanks! Greg

So, I have been attempting to work with Vision via EOS Nomad (v2.91 with dongle), and there has been an extreme lag between the console command and the corresponding visual within Vision (about 3 seconds). I have attempted to use the software all on one laptop, on separate laptops (one for EOS and one for Vision), used Artnet and sACN, all to no avail. It's applying to all lights, even the incandescents. If it was a static look show, I could ignore this. But, I'm attempting to cue a musical with movers, chase effects, etc. This problem makes it impossible to see if the looks are timing out with the songs, as movers will freeze, jump 3 seconds ahead in the sequence, then freeze and repeat. I would assume the software is just overloading my computer (working with a macbook pro that's a few years old at this point), but I have been able to get it to run smoothly via restarting the software (all on one laptop, with a bigger file, no less). While that's a huge hassle of a solution, it's also inconsistent, as I can't get the software to work cleanly at all currently. I've been in contact with Vectorworks support about this issue, and I thought I had the issue solved by running a vision file sent directly from Vectorworks each time (again, huge hassle), but now the issue is back and worse. Has anyone had this issue/have any thoughts to fix it?