Jump to content

mjm

Member
  • Posts

    1,073
  • Joined

  • Last visited

Everything posted by mjm

  1. Jim, I'd be grateful if you could walk me thru the steps in more detail to get to the rending you displayed in this thread. Looks to me like you did something specific Line Render Options | Sketch Hidden Line results... area. But then the rest is not that clear to me. TIA
  2. Okay: Just tried, then immediately purchased Super Vectorizer, even tho I think the price is steep. The four to seven times a year I'll use it will pay for it in one cycle. Fantastically powerful yet simple tool. This is something Nemetschek should consider purchasing and embedding into VWX. Thanks for the recommendation Kaare!
  3. I note there's been no response to this question: "Why can't I apply lit fog to multiple instruments at the same time?" And there are other issues around this very topic: Changing intensities, changing beam characteristics (Smooth Falloff | Realistic Falloff).
  4. Try Josh Benghiat's Savvy Sequencer. A super tool. http://www.benghiatlighting.com/software/products/savvy-sequencer
  5. Just to throw my 2¢ in, I upgraded to EC, after several other articles and fora declared it a winner, then checked here. Some users said they'd no problems with EC/VWX2015 or 2016, so I proceeded, with near disastrous results. The new user account did solve the issue for 2015 & 2016, but along with that, the commensurate re-do on all my other high end softwares has been irritating. It occasionally requires having to change permissions on a huge amount of data on external drives so it can be read/write by the new account. All that was driven by caustics lust, as well as the delicious discovery of the inclusion of Ambient Occlusion. I will endeavor not to be so foolhardy in future.
  6. I have used a north/south configuration, where the upper cells have the label configured above the fixture and the lower cells have the opposite. I have also seen Left/Right configurations, but that impacts the spacing considerably in close-mounted shows. Currently, I use a 'combo' N/S+L/R label which is about clarity for the Color field (see screen capture for the idea).
  7. All: I am grateful for this forum beyond words, it' saved me many a time. And so I seek help again... In following the gist of the Linzey/Landru webinar, I cannot manage to keep the lens part of the fixture, once it's been inserted as a lighting instrument. At that point, the lens element is disappeared from the body. As far as I can tell, all classing / layering seems to be ok. Not attaching the lens to the body thru the data tab results in a a non-rotating lens. And that's it's own special mess. Your thoughts are appreciated! edited for spelling
  8. Josh was kind enough to point out that I had placed the two BD 4 fixtures in the same physical space and so there was a necessary collision of shutters. Once I created a space between the two fixtures, no problem with the beam draw shutters— yay! What that means to me is that what the wireframe shutters display closely matches the rendered beam of light, this is not what happens with the spotlight shutters as detailed above. Sadly, the Soft Shadows option does obliterate the BD 4 shutter cuts. I look forward to a day when all the parts of this puzzle come together.
  9. Josh: thanks very much for your input. I have tried BD 4 for this purpose but see some issues quite different from the SL/RW package ones. I'd be happy to understand if I am deploying your product incorrectly.
  10. KM: perhaps this is what you were asking about?
  11. That's an intriguing notion. Here's the side other... [img:right]https://techboard.vectorworks.net/ubbthreads.php?ubb=download&Number=12049&filename=Screen%20Shot%202015-04-01%20at%207.42.59%20PM.png[/img] Looks like they'e both confused. Also, the shutters seem to react inconsistently in the sense that the "right" shutter moves the camera right shutter (inconsistent with real world), but the :"top" shutter moves the camera bottom shutter (consistent with real world).
  12. And the mysteries accumulate, see screen shot. [img:center]https://techboard.vectorworks.net/ubbthreads.php?ubb=download&Number=12045&filename=Screen%20Shot%202015-04-01%20at%2011.11.21%20AM.png[/img] There are so many things wrong here with the shutter package
  13. Thank you very much for checking on this Jim. Sending you one now.
  14. Rant! I am actually too tired to go into detail now, but I have been struggling with the spotlight shutters for 4 hours in the hopes that they'd (as the SP5 package notes indicated) been fixed. NOT. So very delicate! They indeed do not crash the app anymore, but neither do they function in any meaningful way for rendering purposes. Upon deploying the shutters the first time, everything works as expected. Every time I changed a shutter, it lost functionality completely tho wireframe showed it as still in place. [font:System]How many renders could a render-man render if a render-man could render?[/font] Rant out. Couple more things: Base File was saved from a VW 2014 file. BUT all lighting fixtures came from VW 2015 libraries.
  15. mjm

    SP3

    Installed, & so far so good.
  16. I'd have to agree with Benjamin here. Up till recently I organized scene shifts by layer but began to run into issues like scenery / masking utilized in multiple scenes, yet not in every scene. I ended up deploying classes which worked exceedingly well. Once classes are created, it becomes a simple matter to create saved views / viewports, which are easily updated if things are added/changed. In the initial planning of a recent show, every scenic aspect was in play, from the masking thru flown scenery to deck-based scenery. and so creating views to reflect the various scenarios was a piece of cake. For example: the giant US platform in the Palace scene used straight steps. The same platforms in a later scene used a section of curved steps and additional platforming / steps atop the base install. It seemed to me that creating the layers to satisfy these types of requirements would end up not as elegant a solution.
  17. Phil: light doesn't work that way. And the point light tool attempts to mimic what a true point source does.That said, choosing "smooth" or "realistic" from the Point Light Specs... sheet would get you closer to what you want. After that, try the Custom Light or Spotlight modes. I often use the "Spotlight" Fixtures, as I can shutter them off areas I do not wish to illuminate.
  18. man how'd you get that version of VW! I thought it still under wraps!
  19. Scott—I looked into this as soon as you posted it. I did the following: a] Web searched spotlit fog images. A wide set of characteristics were displayed across the images displayed. b] a ran some tests in VWx 2015 and validated all your findings. c] I happened to be on-set yesterday with a hazer running and made a couple of iPhone snaps and again the characteristics captured varied widely and not necessarily as one might predict. A couple images to display some of the complexity: A MAC Viper, looking up into the beam. A Sharpy, looking down, along the beam as it hits the floor. Two radically different interpretations of fog vs photon. All this leads me to imagine that Nemetschek has chosen to offer one simplistic version of spotlit fog, instead of trying to compete with the incredible complexities of Real Life Physics.
  20. Josh—I did not know that. Thanks and am eager to try it. Have to get through a show first... I'll let you know how it goes.
  21. it occurred to me that "extrude along path"is another viable and quick method, which also gets you history in case you need to edit any of the base geometry.
  22. Josh, yes it does and I am enjoying the use for planning purposes already. But for rendering, I am out in the cold (or do I mean dark or both), unless/until you provide configurable light emitting sources to go with your wonderful shuttering tools. Can't wait!
×
×
  • Create New...