Jump to content


  • Posts

  • Joined


18 Good

Personal Information

  • Occupation
    Theatrical Lighting & Set Design
  • Hobbies
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeeee Haw!! Solved it. Look in Windows Defender Firewall... Allow An App... It's called "loader" (lowercase, just like that) but if you click on Details you will see that it is actually in the Vision folder, so I enabled this mystery "loader" and all of a sudden... it works! Of course we figure things out as soon as we have asked for help... But hopefully this will help someone else!! peace aj
  2. We are trying to connect Vision to MA-Net2 with a dongle. Works fine when all on same PC using loopback and onPC - all parameters available. Using sACN, MA-Net2 is limited by parameter count. In our case we have as many MA2 Lights as we could ask for, which only grant 4096 parameters even when in the same network. Can't get our hands on an NPU and this is time sensitive, unfortunately. When using a real MA2 session with consoles, Vision does not respond to an MA2 session that is not the loopback. We can connect our onPC on the Vision computer to the network, but Vision itself won't respond to DMX from MA2-Net. Switch back to Loopback and it all works. Any ideas?
  3. @bbudzon By "Bucketing" do you mean the process of rendering one "rectangle" at a time then stitching together like a panorama photo? In the original version of ESP Vision, when you asked for a still render this process happened right on the screen so that it appeared that it was panning across the scene... This is what I was thinking (though I'd have no idea how to fix it)... that perhaps the first of these "snapshots" was missing some line of code that reappeared when the program cycled to the next one... and it only applied to non-light geometry since we could see the light beams from fixtures in that "frame" All of my tests were with viewport resolution of 1280x720 rendering to a still at 3840x2160. Interesting that changing that gave you different results.
  4. I can confirm that this does NOT happen in the previous version of Vision 621747 However, any MVR exported with the new gITF feature will not render that geometry in the old version (obviously), so all MVRs have to be exported with the legacy .3DS option to show up in that version of Vision.
  5. OK here it is with just a big block (extrusion converted to Generic Solid) where the SR PA should be. This black hole is affecting that top corner of the rendering in every instance: Realtime: Rendered Still: These images began as a blank VWX document and that big box SR is the simplest geometry, so there's no possibility of some weird "speaker array tool" problem or other thing due to records, etc. This is simple geometry that won't render. It gets more interesting when lighting devices are added behind that big block. I tried just copying a few PA stacks behind that block in the model, and they still don't render. However, lighting device output will render through the black hole. The geometry of the fixtures themselves, however, don't render. Again, this is realtime: And this is the render: I'm out of quarters on this one... The same MVR files would render properly before the SP3 update, so i'll have to see if i can find an old installer and get back to work. I have attached the VWX file from which I created this MVR and these renderings in case someone can break the code and figure this one out. Thanks peace aj Arena PA CornerRenderProblem.mvr Arena PA CornerRenderProblem.vwx
  6. Tried re-exporting the MVR in both "new" gITF format (the new default) and "legacy" .3DS format. Same results. Tried opening a new VWX document and copying all of the PA from my document and pasting in to a fresh layer in a blank document, then export MVR... This is what I saw upon copying: So perhaps my PA symbol, originally created with the Speaker Array tool, is compromised in some way. aj
  7. Discovered two things: 1) The SR PA (the one that disappears) was the original from which SL was mirror copied. 2) It happens with a new document with just the MVR of the PA: Realtime: Rendering: Attached .mvr for reference - see if it happens to you! Thanks aj Troubled-PA.mvr
  8. Here's a weird one that I just want to document before looking further or coming up with a workaround: The Stage Right PA disappears... or has a partial "cloaking device"! This is a screenshot in real time: And here's a rendered still generated from this exact scene: What's happening here? I suspect maybe the PA symbols were mirrored when inserted in to the VWX model, so I'll start there. But right now there's a black hole that swallows these objects on rendering. Notice that the bottom cabinets on the SR PA are visible, and it's not all black; the fixtures on the truss behind are quite visible. I suspect Romulan technology, stolen by the Klingons... but i'm not enough of a Trekkie to take that metaphor any further... Any thoughts? aj
  9. @klinzey Aha! Had not seen that option; MVR export is such a reflex for me now that I didn't notice that little box! Found it in the release notes, no less: VB-185453Export MVR with glTF breaks glTF textures I have confirmed that the legacy .3DS export works as it did before. I just had a crazy idea (but maybe a good one)... A "check engine" light for Vectorworks that draws attention to the features you use most often somehow. Opening the full release notes and searching for one's favourite features is a start... Thanks Kevin! aj
  10. The workaround for this is to first create transparency images for any image you plan to turn in to a texture, then assign the transparencies individually from within Vision. This is of course tedious, adding hours to any model build since you need to prepare the image in a different program twice (three or four times if you're adding Bump or Reflectivity).
  11. When exporting to MVR from Vectorworks, texture transparency and bump are no longer exported. The example is of 3d polygons with a texture that has an alpha channel. The texture is of audience member silhouettes and their transparency (image mask with alpha) allows their heads to be seen with the rest of the rectangular polygon transparent: In the Properties window, you can see that the above selected geometry has been brought in from the Renderworks texture properly: When exporting MVR from VWX2022 SP3, we can see that the name of the geometry has now been changed to "meshes[0]" and the transparency is no longer there. Note the black rectangular polygon outline where there should be transparent alpha channel: And now the Properties window indicates that the geometry has no Alpha texture: This happens when "Image Mask" Transparency is used in the Renderworks texture from "This Texture's Color" then selecting Alpha Channel It also happens when a separate transparency image is prepared in Photoshop by generating an image with white for the pixels you want rendered and black for transparent (essentially the same process that Renderworks is doing, but manually). Could this be repaired? Transparencies are an essential part of the Vision workflow, saving countless polygons when illustrating complicated objects with just a few polygons. Thanks aj
  12. Dude, you already got my money, and I have been using your awesome symbols for some time now!!! I think that I was using the VWX model because you didn't have that particular Ampeg symbol? Or maybe some other reason. Perhaps I need to throw you another $50 for the 2020 models?? I'll help you shamelessly plug your library... I just switched a bunch of VWX guitars for your symbols to reduce the polygon count for pre-vis... Keep up the good work! peace aj
  13. Luckily I have a console here and not a viz-key, because I can still output sACN on all my granted universes. I believe that when recording DMX, the MA3 connection is smoother and better than recording sACN. When I rendered out an animation with Absolute Camera moves using MA3 Connect, the camera was quite smooth. When this problem happened and I switched to sACN, the DMX recordings resulted in jerky camera movements. The model is now more complicated, so perhaps that has something to do with it. That Absolute camera is wonderful, but it is frustrating to see it work smoothly one day and jerky the next. However, I don't have time for these experiments any more. My solution has been to go back to MA2 for lighting programming and MA3D (2 version) for pre-vis. It just works better. I'm sorry, but I'm done debugging Vision for now. I'll be using other tools to get my programming done. I really appreciate your efforts and detailed responses, but when an upgrade breaks a working feature and it gets released, it's really frustrating. Some will say "don't upgrade while working on a project" but I HAD to upgrade to get the MVR texture import to work after identifying that problem. Covid time was great for learning new software and experimenting, but now that real work has returned, I find myself fighting the newest software more than using it. Very disappointed that all of this work has not resulted in a more usable product. Seems we are still playing catch-up with Vision and every time there's a problem fixed, new problems are created. I hope that the "higher ups" that seem to be holding this product back, promising features that don't work and generally dragging feet on Vision hear that this customer is NOT satisfied and will be switching to some other product before this year's Vision license expires. I'll keep posting about Vectorworks issues, however... Not going to give up 25 years of sunk cost in that program. At least MVR gives me options. peace aj
  14. After installing SP4 for Vision 2021, I get this on launch: MA3 Net does not work anymore. Anyone else have this problem? peace aj
  • Create New...