Gaspar Potocnik

I’ve encountered this problem more than once. Are you a service select member? There is a fixture form there as well.

I was expecting the same format as the Vectorworks list, any chance this can start happening?

Since it’s developed by Vectorworks why wasn’t vision the first app to include it? Any chance this will happen in the future?

Any chance we can get a lista of fixes the same way we get one for VW? Thanks!

Paste it into:

+1

You need something that outputs dmx, depending on the brand of consoles you get some free Chanels, but I believe there is no console manufacturer that will let you output unlimited channels... That being said, for MA Lighting you have two options, if you want to use GrandMA 1 or 2 OnPC you need to download the ESP Vision Connection Driver from MA website (https://www.malighting.com/downloads/products/grandma2/) which only runs on Windows (so your Vision also has to run on Windows), and allows you to use MA NET to connect to Vision and has no limit in the amount of fixtures you can control. The other option is to use GrandMA Dot2 onPC, which has one free universe through Artnet or sACN. I believe Chamsys also has a free universe, not sure on the rest of the manufacturers.

One option is to export as separate .esc (which is what I usually use) but what happens is VW exports everything that has the same texture together or if it has no texture then everything with the same color fill. So assigning different textures or color fills make separate meshes in Vision.

Count me in!

Coming back to this topic after a few years... So I’ve redone symbols so that everything is uses classes that work for me, but I still haven’t been able to change de default class of the label. I’ve edited the string in the plug in but still it isn’t changing, what am I missing?

For this you have to create a renderworks texture with an image from your content (or print screen of your output), apptly it to your four screens, an then with the attribute mapping tool "map" the screens. I usually use the actual raster file for the production. Afterwards in vision some cropping is always needed, but not time consuming at all. Regarding the capture device, here are some specs and options.

That’s a good workaround, but I am just creating new custom libraries that way... maybe the ability to edit the root class can be added into vw2020...

I'm on the same crusade @scottmoore is at the moment, after many years of using custom symbols, trying to see if I can get stock truss libraries into my workflow. One thing I need to get around is classes, is there any way of editing the label root class?

Sorry @BrandonSPP for the delay. If cameras are also DMX controlable it would be good, but what I am asking for is renderworks cameras created in VW to be exported to Vision, so you can get the same view in VW and Vision.

Can I do double Like?

I kept on investigating fixtures, turns out the Showtec Stage blinders are set to 6000 in color temperature (I'm guessing it is still in Kº) and they look much more like and actual molefay, so that is a good workaround... Same setting for a Jarag which looks even more warm than the showtec

The big drawback with this workflow is vision and lightwright.. Personally I'm pretty happy with 3d Label legends. but they are still not quite there. Hopefully we can get 2d info in 3d symbols views in spotlight too, that would also make a difference...

I've tried importing different molefays and all of them render a much higher CT than what they are supposed to. Comparing them toa generic P64 really makes you see the difference. I've tried lowering the candela with no difference in color and changing the color temperature which makes vision crash (already generated a report). None of them have the possibility to add a color so that workaround is no good. Getting nostalgic with the way Vision 2.3 rendered molefays 😞

Yep, definitely interested!

Strange this is, with no capture card connected, I still get the same limit.

I've had this same problem when using sACN, the workaround I found was either using Artnet or restarting the App n number of times until it was OK. JIRA has already been generated on my side a coupe of months ago...

2. Choose File > New Movie Recording and then select the input device. Set the recording to High from the dropown menu next to the recording button.

1. I am assuming this resolution because of the coordinates shown when cropping the input, is there any other way? All my setting are set to Very high and resolution to 4K for the purpose of this test. 2. Quicktime shows 1080p, or whatever other resolution I set the output to be.

@bbudzon my MBP 2016 camera is also being limited to 640 x 480 (I'm assuming this because of the coordinates of the crop raster). The content is 1080 and so is the config of the output. I can't configure the input since it is a driverless card (actually that resolution isn't event listed in the specs of the UVC grabber) I've trie3d two different computers and have the same issue. And I completely agree with the limit, I wanted to know if this was a known limit, since it is not listed anywhere, and if could be changed anywhere, just to know the limits and how it works...

So I have successfully tried the Ezcap 265/C. I did find that the capture is limited in vision to 640 x 480, although I've configured the device to 1080p, is this software limited or is there some other issue?