Jump to content

Bradley King

Member
  • Posts

    106
  • Joined

  • Last visited

Posts posted by Bradley King

  1. I have a row of Colorforce 72 LED strip lights focused at a white wall, replicating a cyc.

     

    When I bring the lights up in the console at 1%, the fixtures are visually about where 25% should be on the dimming curve (this is a real-life problem too). I'm trying to essentially quash the output of these fixtures so they're about half as bright as Vision thinks they are, to allow for finer control of lower-level intensities. 

     

    When I make adjustments to the candela in Vision, the output seems to disappear entirely from the top half of the dimming curve. IE: once the console reaches 50% output, the light does not get any brighter. It's as if 50% has become "full" in Vision.

     

    Is there a different way I should be going about this?

     

    Thanks!

     

  2. Hello friends,

     

    Forgive the basic question, but does anyone have a quick RW formula for an eggshell (or semi-gloss) paint texture? I'm looking for a bit more depth than a basic color texture, and was wondering if there was an easy way to up the reflectivity a bit.

     

    Thanks!

  3. 1 minute ago, Bradley King said:

    Interesting... I'm running 588748 (VW) and 26.0.3 (586381) Vision.

     

    Nor am I sending data via GDTF. Just regular "Fixture Mode"

     

    Any other ideas? Would a file be helpful?

     

     

    Actually I just figured it out. I wasn't exporting the focus point objects as part of the MVR export, but it seems as long as I include them, the fixture focus gets sent. I didn't realize the two were linked.

     

    Assuming that's WAD?

     

     

    • Like 1
  4. Hello friends,

     

    What is the proper workflow to send conventional unit focus information from Vectorworks to Vision? 

     

    My lights are focused in VW using focus points (and have the correct pan/tilt information in the OIP), but arrive in Vision pointed straight down.

     

    Any help would be appreciated.

     

     


     

  5. Hey everyone,

     

    Has the console connectivity instructions for ETC Eos been updated? That link is now three years out of date, and I am having some issues connecting Eos Offline (with Previz) to Vision (both are running on the same computer). When I bring up channel one on the console, channels 1-7 (all identical fixtures) come up as if they were patched together. Same thing happens on sACN. And the Vision DMX Viewer is showing no output even though those lights are turning on and responding (albeit as one fixture as opposed to 7).

     

    I should also note that if I try and bring up those fixtures by address, the problem persists. It's as if they were all addressed the same, even though they are patched correctly in both VW/Vision and in the console.

     

    Thanks

  6. So was looking for a solution to this exact problem, and here's a quick hack. If you drop a helidon anywhere in the same layer as your lighting fixtures, it will essentially replace the ambient lighting at more or less the same values. It's not *exactly* the same but it's pretty close.

     

    Just make sure shadows are turned off on your OpenGL rendering settings.

    • Like 2
  7. Hey @jeff prince - curious which way you went. I'm in the same position; my iMac is approaching end of life (late 2013 model) and I'm torn between a fully loaded iMac (core i9, 32GB Ram, 1TB SSD, Pro Vega 48) vs a base model 8-core iMac Pro (32GB ram, Pro Vega 56, 1TB SSD).

     

    The new iMac comes out to $3675, and OWC has factory refurbished iMac Pros with those specs for around $3800.

     

     Especially curious if the Xeon processor + ECC adds any stability. FWIW, I do very little rendering, although I do spend a considerable amount of time in flyover/OpenGL.

     

  8. On 6/23/2018 at 8:03 PM, DBLD said:

     

    The most ideal situation would be for Vision to be built in Vectorworks, so there is no application switching and any update that is made in Vectorworks is automatically updated in the visualiser. 

     

    This this this this this. In my ideal setup, Vision would be a viewing mode just like Renderworks. I want to incorporate Vision into the design process more: if it worked like this, Vision could be used to check and compare angles, positions, etc. How does this light look on the boom versus on an electric? Where should I place this moving light so it's most useful to the overall rig? Where's the best place to hit this piece of scenery from? Vision + something like @JBenghiat's Beam Draw tools could revolutionize the layout process for a lot of theatrical LD's.

     

    But right now it seems to function best as a "OK, I am *completely* done with this plot, absolutely no more changes, here we go to Vision" tool, and that's not how I think it's most useful to the most people.

  9. Hello Marionette gurus:

    Is there a way I can get Marionette to draw me a line using a start point, a point on the line, and a distance?

    This seems to be giving me more trouble than I had expected. My current workaround is to draw a line from the start point along the X axis of distance D, then draw a line between the two points, get its angle, and rotate the first line to match.

    But I know there's probably a more elegant solution.

  10. Regarding the new "Number Instruments" dialogue:

    Is anyone else driven completely insane that "Unit Number" doesn't default back to 1 after number a position? I can understand why it might be useful for *anything* else, but don't you start at Unit #1 99% of the time when labeling a position?

    Has anyone figured out a work-around? Thanks.

    -Bradley

  11. Awhile back I posted about Spotlight resetting my origin; I've nailed down what's causing it:

    -Select any symbol and then click on the instrument insertion tool

    -Click once in the workspace to set the coordinates/rotation but DON'T click again to insert the object

    -Instead, interrupt the process by clicking any other tool or hitting the ESC key. The origin will shift.

    The 6 of us working in the lab today were all able to re-create the above (thanks to John McKernon for helping me nail it down). Also of interest is that the origin seems to reset to the same point each time, but was different for each user. Not sure why, but this seems like it should be an easy fix.

    -Bradley

    Vectorworks Designer 2008 SP2

    Powerbook G4 1.67gHz

  12. Yes: you have to fill the blank fields with "-" because, I believe, VW doesn't recognize a blank space as a field entry; it'll just skip it.

    Also, I highly recommend Sam Jones's Autoplot Tools for Spotlight:

    http://www.autoplotvw.com/APSL_Download.asp

    The entire package is fantastic, but the macros for import and export to lightwright (he includes automated actions for LW as well) is alone worth the $35. I have rarely, if ever, had a single export/import error when using them.

    _____________

    Bradley King

    Powerbook G4, 1.6ghz, 1GB Ram - OS 10.4.9

    VW 2008 Designer SP2

  13. Has anyone experienced a problem with Spotlight randomly resetting the user origin (I touched nothing in the way of either the "set origin" menu option or the set origin button). I haven't yet been able to pin down exactly what I did before it happens; but I have had it occur about half a dozen times when working with Spotlight files in '08.

    I'll keep looking to see if I can find the action that triggers it, but I'm curious if anyone else has experienced this phenomenon.

    Thanks,

    Brad

    Powerbook G4 1.67

    1GB RAM

    Mac OSX 10.4.11

    VW 2008 (13.0.0)

×
×
  • Create New...