Jump to content

bbudzon

Vectorworks, Inc Employee
  • Content Count

    326
  • Joined

  • Last visited

Community Reputation

83 Excellent

2 Followers

About bbudzon

  • Rank
    Journeyman

Personal Information

  • Location
    United States

Recent Profile Visitors

929 profile views
  1. This has been removed. I'll wait for someone more familiar with Spotlight to chime in, but basically we have new fields in 2020 that must be used in order for ESC/MVR exports to export properly.
  2. I'm looking at the SGM Palco 5 and the SGM Palco 3 (these are the display names that should show up in the Fixture Mode / Vision). We may need to tie @Mark Eli in here as he handles our fixture personalities. From what I can see though, it looks like channel 1 controls both the strobe and the zoom, which doesn't seem quite right 😛 So, I'm assuming I'm reading the content wrong. Perhaps you could verify this? In theory, if you're sending 255 to channel 2 (the dimmer channel) and you send DMX values between 8-15 to channel 1, it should have a narrow zoom (5 degs) and the strobe will be in the On state. If you're sending 255 to channel 2 (the dimmer channel) and you send DMX values between 200-223 to channel 1, it should have a wide zoom (8 degs) and the strobe will be in the On state. Now that I'm typing this out, it may be that this is how the fixture is designed. Hard for me to say as I'm just a code monkey 🤣 Hopefully @Mark Eli can chime in and help get things rolling!
  3. Attachments aren't quite working and until they work better we should probably remove the UI. From what I can tell looking at that fixture, it accepts DMX in the range of 0-255 on it's first channel for controlling zoom. Keep in mind that VW doesn't handle DMX for movers but Vision requires it.
  4. Just for completeness, I'll post here as well. If anyone is experiencing this issue, please update to VW 2020 SP2 as a fix went into this build 😉 VB-165306 Some lighting devices won't accept a manually-applied fixture mode If you're still having issues, we'll try to track it down!
  5. I'm not sure if this is a separate issue or not, but please make sure you are running VW 2020 SP2 as this fix went into the build 😉 VB-165306 Some lighting devices won't accept a manually-applied fixture mode
  6. It's hard to say, but my money is on the Fixture Mode not being properly set 😉 Usually if a fixture comes over to Vision as just raw geometry, it is a result of the Fixture Mode not being set in VW.
  7. I'm not sure if you were able to use the new Rotate 3D Menu command to solve this workflow issue or not. But if you were, I'm glad that I was able to get that feature in to make things easy for you! (The new Move and Rotate 3D menu commands are so incredibly powerful in Vision as they allow you to perform arithmetic on multiple objects where you could not before! My favorite example is taking all trusses at various trim heights and "adding 5 feet of trim" to them all. Previously, this was not possible in Vision as you could only assign all sticks of truss to be at a height of 5 feet! 😛)
  8. 😛 No worries! I'm glad you go the brightness figured out. FWIW, I would _highly_ recommend tweaking your Application and Document settings to get better performance. It is obvious that this comes at the cost of quality. So finding a sweet spot is very much a personal preference 😉 Some of the biggest offenders of performance are: Resolution Quality Haze Quality Haze Style Render Shadows Shadow Quality Render Fixtures Surface Light Quality Dynamic Shadows Edit: Oh, one more thing. This is not always ideal but it IS an option nevertheless. If you have lights that are hurting performance but you don't necessarily need beams out of them, you can flag all of these fixtures via multiple selection as "Emissive" via the "Force Emissive" option. The best example of this is usually blinders as they are not casting light onto the stage but rather the audience. As such, these lights generally don't need to cast light/beams but simply need to "blow out" the rendering (ie; blinding the camera/eye/audience with light). This emissive intensity can be controlled via the Bloom Lens Strength option. I generally recommend keeping Bloom Percentage and Bloom Threshold at 1 and 1 (only adjust the Bloom Lens Strength value to get bright lens bloom).
  9. @Monkeypuzzle, I have an older MBP running 10.14. I have the "automatic graphics switching" enabled in the Energy Saver settings. I usually run with external monitors hooked up though which forces OSX to use my AMD card always as opposed to my builtin Intel. I also have a program called gfxSwitcher that lets me force certain cards when they would not be used otherwise. https://gfx.io/ If you want to increase the overall light output of fixtures, it is generally recommended that you increase your exposure value. This may result in you needing to lower than ambient intensity for the room to remain "dark". Edit: Just to be clear, you are talking about both "surface light" and "beams" not being bright enough? If this is true, exposure is the key. If you would like only the beams to appear brighter/thicker, you could adjust some of the Haze Intensity values to pump up the fog 😉
  10. You may have hit a point in which ESC may be better than MVR. Let me explain... The ESC File Format is Vision specific. No other program in the world can read it, including VW. VW is the only program I am aware of that can export ESC as well (Vision cannot, as odd as this may seem). My point in all of this is that because the ESC exported from VW can only go to Vision, VW can do "special Vision stuff" at export time. This means you can control exports in VW through things like the the fixture type being set to Moving Light. The MVR File Format is generic. Any program that supports MVR can import it. Any program that supports MVR could also export it. My point here is that because MVR can be sent to any program, VW cannot do "special Vision stuff" at export time. This means you cannot control exports in VW through things like the fixture type being set to Moving Light. Looking at it another way, VW flips Moving Lights during ESC export. So the lights are actually flipped inside of the ESC. Vision does not do any flipping at import time for ESC because VW already did the "flipping". Because VW could not do this for MVR (and because we haven't fully implemented GDTF in Vision), we had to implement the "flip" at import time in Vision instead of export time in VW. The downside to this is that you lose control over each individual fixture being flipped or not. (Note: It may not be obvious, but once we get GDTF reading properly in Vision most of these issues go away.) My suggestion would be to either use a mix of ESC and MVR, or use MVR entirely and use the new Rotate 3D menu command to fix all disoriented fixtures in (more or less) a single click.
  11. I'm glad that you managed to get things working! FWIW, I downloaded your zip, launched Vision 2020 SP2, clicked File->Open, navigated to your MVR, and opened it with default MVR Import options. All of the color temperatures seemed to be correct.
  12. If you select a light that is "white", what is it's color temperature in the Property Window? If you select a light that is "amber", what it it's color temperature in the Property Window? It's been a while since I've seen this. Perhaps you could post/pm this file as well and we can see if we can reproduce and see what problems may exist in the code.
  13. Would you mind posting your file or pm'ing it to me?
  14. Just to be clear, the Software Console that exists inside of Vision is intended to control conventional fixtures. Think of it like a stage hand. If you'd like to control movers, you will need to do as Rob says and hook up a light board such as MA. Once your light board is patched and matching Vision, make sure your DMX Provider in Vision is set accordingly. Once that is all taken care of you should be good to go!
  15. You absolutely should!! There are only a few select cases (namely things like lamp rotations on a conventional) where ESC is recommended. Check out my post for more details!

 

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.

×
×
  • Create New...