Jump to content

SB Lighting

  • Posts

  • Joined

  • Last visited

Everything posted by SB Lighting

  1. Thanks for continuing to look into this! I can change the gel color for conventional lights and get a dark blue so Vision is able to create that color. It seems like Vision just isn't reading information from the ETC EOS software correctly. The EOS software has its own visualizer and the color looks correct there. When it comes into Vision, though, the color is much paler. I'm attaching a photo with the side-by-side comparison of Vision and ETC Augment3D. Both are rendering the same information but look very different. (on a side note, they both also treat the VL2600 very differently. I won't know which is correct until I get into the theater)
  2. Thanks Mark! I just assumed that the Quick Preferences would work the same as the Preferences, which is apparently not the case. @Zoomer - I don't think i can make a template that saves quick preferences, though it is easy enough to switch them on and off now that I know how the quick preference button works. I do still think that the Preferences setting should do the same thing as the Quick Preferences button. I don't understand the point of having a setting that just prevents you from editing the existing drop shadows.
  3. I tried default settings and safe mode settings but there was no difference. I've also tried both PC and Mac computers and it is the same on both. Attached is the Vision file. SpongeBob Plot.v3s
  4. Hi Kevin, Thanks for the suggestion. Unfortunately it does not give me the option to replace the Light Info Record format when importing, even after I reset the "Always do the Selected Actions" option. It asks if I want to replace the "parts" record format, but for the Light Info Record it still just gives the options to either use the current format or cancel the import. (see screenshot) Are there any other ways I might be able to import the Light Info Record?
  5. Hi Mark, I've been trying to remove c-clamps from some lights in the way you demonstrate in your video but it doesn't seem to work for me. I'm not sure if I am doing something wrong or if it doesn't work the same in the latest VW2021 software. I have the clamps set as "static accessories" and have "base" selected under the "Parts" Record Format. They still seem to be treated as part of the light rather than an accessory, however, and I can't use the remove accessory tool to take them off. (nor edit them in the accessory edit space) Is there another step that I am missing? Thanks! Scott
  6. Thanks for continuing to look at this @bbudzon! Yes, those images look the same as the Vision files when I look at them on my PC. Not sure why they render differently on my Mac(s). Sometimes the beam is red as well. When the beam is red, though, it doesn't interact with surfaces. (see attached photo) There are so many different weird things happening that I haven't documented them all. You say the file isn't loading textures properly. Is there anyway to help Vision locate the textures? Both the Vision file and textures folder are on my computer's desktop so I'm not sure why Vision is having trouble finding them. I am using a 16" MacBook Pro (2.6 GHz 6-Core Intel Core i7, 16 GB 2667 MHz DDR4, Intel UHD Graphics 630). I also tried it on a 13" Macbook and had the same issues. (1.4Ghz quad-core Intel I5 128 MB DRAM Intel Iris Plus Graphics 645) Thanks! Scott
  7. Thanks for your quick response! In answer to your questions: Two different files have the same issues so I don't think it is a file issue. I did transfer the textures folder. Changing Candela / Color Temperature / Color Wheels / Gobos has no effect. Changing "force emissive" to "true" turns off the light. I turned off shadows and got a slightly different kind of strangeness but still very strange and unusable. The weird shadows are not fixed by changing the shadow quality or refocusing the light. They persist even when render shadows is turned off. I transferred the files using a thumb drive and had the same issues so I do not think that DropBox is the culprit. I'm attaching the files and textures to this message. I am using a 16" MacBook Pro (2.6 GHz 6-Core Intel Core i7, 16 GB 2667 MHz DDR4, Intel UHD Graphics 630). Thanks again! Scott Archive.zip
  8. I created Vision files on my desktop PC at home that are very buggy when I open them on my MacBook at work. When I select a light, it either turns on with a red beam or doesn't turn on at all. Many of the beams also seem to pass through objects or have strange shadows in the middle of the beam. This was a problem my students had frequently last semester but which I could never replicate. Now it has happened to me and I'm not sure how to fix it. I've tried dropping all of the settings to low quality and it still happens. Maybe it has something to do with screen resolution? My monitor is 3072 x 1920, which is not a resolution option in Vision. Or it could be PC to Mac conversion? Or is it from transferring files via DropBox? I've moved the file from DropBox to my desktop and still have the same issue. Has anyone else experienced (and solved) this issue?
  9. Also, the fixture shows up in Vision as only having one channel but lists the both the Candela and Color Temperature as "multiple", even though they are only listed once in the file. I'm attaching the .xml in case anyone is willing to take a look. Nexera test.txt
  10. I am also having problems getting GDTF fixtures to work with VW/Vision. I am trying to build a Wybron Nexera because the Nexera Fixture Mode in VW is broken. I have made a fixture in GDTF Builder and have compared the GDTF files I created with the Generic GDTF files in VW. They seem comparable. Yet I still have two major problems when I merge the fixtures into vision: Fixtures turn on when selected but do not respond to DMX. I have turned all four DMX channels to full and nothing happens. I have tried creating several different custom fixtures in EOS and none of them work. Fixtures appear in very different locations in Vision from where they are drawn in VW. Units in VW drawing are set to mm and I am merging the lights as GDTF fixtures, also using mm as units. If there are any GDTF wizards out there I'd love some advice! Thanks! Scott
  11. Thanks Kevin! I was hoping not to go that route as I'm not quite sure when to find the time to teach myself to build a GDTF fixture. I was really hoping there was a simple data mapping solution! It's good to know what is possible though, so I can focus my energy appropriately. Cheers,. Scott
  12. We have some Wybron Nexeras in a theater space that we are using for class and I need to have a Vision file of the space for students to use in a project. Unfortunately, the Nexera fixture mode for Vision seems to be broken. When the Nexeras import to Vision, the lights are constantly on and the intensity channel has no effect. The three color channels work fine and all the other fixtures work normally. (MAC 550s, MAC Auras) I assume this is an issue with data mapping. Is there a way I can fix this myself? I wrote to VW but haven't heard anything back and it is something my students need right away. Thanks! Scott
  13. Hi Mark - thanks for this tremendously helpful video! Could you explain how you offset the overhung par can? I can't seem to do that in my own drawings. I'm trying to draw a light ladder with lights overhung and underhung on the same rung. I want to preserve the 3D geometry but can't figure out how to do that without the overhung lights completely covering the underhung lights in the schematic view. Thanks! Scott
  14. Thanks Pat! I guess I'm glad that I wasn't being an idiot, though it still seems awfully labor intensive for something that could just be click and drag. It only takes one button to remove a menu from the workspace. Seems silly to require so much additional effort to add a menu. Instead of a one step-process for me, this is now something like a 150-step process. Guess I better get started...
  15. This is really stupid, but I can't figure out how to move an inactive menu into the list of active menus. I'm in the workspace editor, with the list of all the menus in the pane on the left and the list of active menus in the pane on the right. I would think I should just be able to drag an inactive menu from the left pane to the right pane but it won't allow that. I can drag a new menu over, rename it and then move each tool over individually but that seems like a stupidly labor-intensive process. What am I missing here?
  16. Thanks for your quick responses Mark! I'm curious about why you would use the style function for the situations you describe rather than using symbols. To my thinking, if I had a set inventory of pipes then I'd want to use a style to keep the overall look of the pipes consistent and then use symbols for the different lengths or pipe. That way, if I had an installation where I wanted to say, use 25cm tick marks rather than 50cm tick marks, I could just change the style and adjust every pipe in the system while still using the same symbols I always use for different pipe lengths. Otherwise, I'd have to individually re-style every pipe in the inventory to make that change. The consistency of approach makes sense to me as an argument. Though you could still have some attributes default to "on" or "off" without changing the consistency of having the "by instance" or "by style" options. And it might make it easier for beginner users to go through fewer menus to get to what seems to me would be the most likely scenario. Though, as you point out, it may only be the "most likely" from my point of view!
  17. Yes, that works - thanks! I still feel like pipe length should probably be off by default rather than having to go to a separate menu to change it to "by instance". I literally cannot think of one situation in my industry when having pipe length as a part of style would prove useful, particularly since you already need to create a symbol (with a set pipe length) in order to make a hanging position. That seems to accomplish the same thing without impinging on the style function. Still, now that I understand how to navigate, it is a real time-saver, so thanks!
  18. The lighting pipe style has the potential to be a wonderful feature. Unfortunately, it has a major downfall in that it records pipe length as part of the "style". This really hampers the effectiveness of this tool. If it didn't record pipe length, it would be a fantastic tool for quickly setting the look of every lighting pipe in the theater. As it is, you need a new "style" for every different length of pipe. That means it functions essentially the same way that a symbol does, rather than providing a unique and tremendously useful feature.
  19. Great - thanks Josh!
  20. SB Lighting


    How does the lighting pipe footprint work in Spotlight 2020? There used to be a Footprint section in the OIP but that is no longer there. I see that you can assign a footprint class but I don't see how you make the foot print visible or interact with it
  • Create New...