Charlie Hegelheimer

Thank you for your response. This is not the first time I have run into this issue. Before it was with the Chauvet Color Strike M fixtures. I had a festival stage that had 90 units and each unit has 14 rgb lamps and 28 strobe lamps within it. Having multi instance fixtures like this is very common and being able to adjust a fixtures sub instance luminance or reduce the distance of light that it is actually able to throw would be very valuable when trying to previz on larger rigs like the one I have here. Ideally, being able to dial in the way individual lights are looking in Vision needs to be something that can be done quickly and easily. This way when we are rendering for a client we can really shape the final look of the renders to something exactly that we want to convey. Often I find with LED lights like this that create a "wash" or light up the entire environment absolutely destroy the ability to be effective with the software. Again Thank you,

Hello, I am trying to render some images of a large festival concept for a client. I have 148 ACME Pixel Line IP fixtures. These are similar to the JDC Line, a 1 meter long led pixel bar with a strobe tube between two lines of RGB pixels. Typically when I have a large amount of fixtures like this I put them in emissive mode as they tend to crash the software or severely bog down my GPU. The problem I am having is when I set them to be emissive the LEDs are not bright enough to convey the purpose of the fixture. In the past when I set fixtures with large quantities or fixtures that put out too much light and kill processing into emissive, I will crank the Candela WAYYYY up and get a nice glow out of them and software is not having to process the light output. Currently with this fixture the Candela option is grayed out and says multiple. The only lighting adjustment it appears that i can change is the beam multiplier and even setting this to .01 does not help and. When I select the sub directory of the fixture there is no lighting options. Is there a way to easily adjust the light output of a multi instance device? Ideally id like to have a nice glow from the fixture and still have pixel control. ALSO, It would be really nice to have the option in vision to have lights NOT "highlight" when you select them, we don't always need this. For example if I try to select all 148 of these fixtures they automatically light up and just about crash the software. If it doesn't crash I have to wait several seconds till I can get to the Emissive check box and then several more seconds before the check registers. This seems like a simple option I should be able to disable, just like in real life we don't always need the fixtures to highlight when selecting them. I am including my MVR for your reference. Thanks. Test23_Conecept_1_v1.4 MVRNo Scenic.mvr

Wow! Thank you so much! Glad that this is possible. This is an area I am happy to know about!

Hey guys, Curious about something that I feel should be pretty simple... The universe/Address field ONLY accepts data with a / separating the univ and address. Could it be possible to get this field to accept and read a . as well as a /?? Reason I ask is I have been given a file that has 400+ fixtures for a festival. Whomever built this file put every single fixtures univ and address in a user defined field as Universe.Address When I use Find and Modify to copy that field into the universe/address field it will not take it. I feel like this should be an easy data migration task. Many people in the industry use "." to distinguish univ and address. Id really like to find a away of getting all the universe and address data from the user defined field to the proper location so I can export an MVR with correct patch info for use in my previz suite. Thanks in advance.

Question Regarding this fixture. OP also mentioned the issue with the zoom. I currently have a reversed zoom issue. I am running 2022 and fully updated Vision and the Library and restarted. Still getting same issue. Is there an easy way to fix this? Thanks

Any admin or Vectorworks/vision staff able to provide any help on this? I went and made a GDTF file for this fixture and imported that to spotlight. Then exported my MVR again which now the light moves but no color, gobo, prism etc. (must have done something wrong in the GDTF builder). At this point do I waste more time trying to build a fixture profile when I would rather be programming for a show?? This software seems frustrate me more than it improves workflow. On the verge of selling this dongle if anyone even wants one and going with one of the many seemingly better alternatives.

Hey All, So, it appears the Rogue R3 Beam has been recently added to the Spotlight Library, but the fixture has no profiles available for it. I have added it to the fixture request but I feel like every time I use that I never get a response nor do I see the requested fixtures added. Can anyone offer some advice as to how I can use this fixture in Vision as I have a show in a few days using this fixture and I'd really like to use this expensive software I bought rather than just exporting positions to MA3D and defaulting to something that actually works. Thanks in advanced.

Thank you for your Thorough response on this. Regarding overall performance, I re-exported the MVR file to remove truss and also the crowd/entourage as non of that is really needed to create the time code and will just use the full file when I record everything. This has helped a bit, not as much as I'd like but at least its usable. The Elation Chorus Line fixtures did not automatically have a profile in VWX but I was able to manually find the correct one and the fixtures are working now. The VL 4000 do have the correct channel numbers in the fixture profile and are working as expected minus showing the gobos. Again this is very odd as I can see all the gobo images in Vision under the Properties window so it must be something in the profile or programming. I can see in MA the DMX output sending values for the gobo wheels its just does not seem to be translating to vision. I am going to spend some more time with them and see if I can get them to work. Overall I really hope to see the performance increase in Vision. I am not a software engineer so I am out of my element here but it really doesn't seem like it runs very smoothly when trying to run large designs. I get countless crashes and it seems like inconsistent performance. This may very well be me/user error or even my machine but I am excited to see this software grow/improve as I am pretty highly invested in it now. 🙂

Hey guys! I have a few questions here today. 1. I have not used Vision too much but have watched most the videos in the university to optimize and understand the settings to increase performance. My goal was to complete some time coded shows to use as a demo for some artists I am working with. I have exported my stage design as an MVR and then saved the scene and settings as a v3s file. The other day I was able to use the software fairly smoothly to get a bulk of the time code done but have since tried to launch Vision multiple other times with the performance just being abysmal. I did not change any settings but now I can barley use the software. I have shadows off and texture quality at Med. I am running an RTX 3090 and the graphics card seems to only be running around 40% yet the software seems like it just cant do what its supposed too. Other than MA2 there is nothing else running on the machine and have been on fresh boots every time I launch Vision. It just seems like Vision runs very inconstantly. Additionally when it was running very "choppy" I would try and lower texture quality from Med to Low/very low and it almost takes an hour to relaunch the file. While its running it doesn't seem like the CPU or GPU are being utilized. When the file finally re launches after adjusting texture quality its almost worse performance. Granted I have built a stage that would be considered very large at a 600 Fixture count (bulk of the fixtures are non moving LED) but have set most of the fixtures to "Force Emissive" Being that Vision is part of Vectorworks and essentially the industry standard for drafting designs I would really like to think that Vision should be up to the task of handling stages of this magnitude. When things were working well the other day my setting were 1920x1080 HD Haze No Shadows Med Texture quality Since, I have lowered everything and its performance is worse and essentially unusable. Any insight on how/why there would be such inconsistency and how I can fix this? Second question is in regards to fixtures... In my stage I have : Martin Mac Axioms VL4000 Beam Wash Martin Mac Quantum Wash Elation Chorus Line JDC-1 -The VL4000s gobos are not displaying in vision. When I select the asset/fixture in Vision on the right side I can see that it has the gobo images for each wheel but they just don't show up in the visualizer. -The Chorus Lines do not light up at all. Even when I select them manually they do not "Highlight" like fixtures usually do in Vision. I imported the MVR file and used the "Vision" Fixture when opening the MVR. If there is anything I can provide please let me know. Thanks in advance! Charlie

Thank you! that makes a lot of sense. I was rendering at 4k on all high settings with a decent sized rig with many multi instance fixtures. I will use your method of checking with rendering stills. Thank you so much

Hey guys, I am experiencing a Vision issue when rendering. I recorded DMX, and on a fresh boot of Vision I play back the recording and all lights are working as they’re supposed to. I then render and the resulting video only has two groups of lights turning on/working (Spots & Beams). I then re play back the same DMX recording live after the rendering and the issue is replicated. Only spot and beam fixtures are turning on. If I reboot vision and open the DMX recorder, load the file, everything plays back correctly. Non of the lights are set to “force emissive”. I’ve browsed through the Vision forum with no luck and really would like to get this video rendered correctly. Any help would be greatly appreciated. This is my first time recording and rendering out from Vision so entirely possible it’s user error. This is on Vision 2020