Jump to content

ajpen

Member
  • Posts

    53
  • Joined

  • Last visited

Reputation

14 Good

Personal Information

  • Occupation
    Theatrical Lighting & Set Design
  • Hobbies
    Skydiving
  • Location
    Canada

Recent Profile Visitors

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

  1. 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
  2. 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
  3. After installing SP4 for Vision 2021, I get this on launch: MA3 Net does not work anymore. Anyone else have this problem? peace aj
  4. @bbudzon@Hans-Olav@mjm@jeff prince Looks like that fix made the cut! My crowd figures now look like this after MVR export with no further action required: Thanks!!!!!! peace aj
  5. Hi Y'all... Pour yourself a coffee and tuck in; this is a long one! I'm having trouble mapping an NDI stream to various LED tiles placed on stage in set carts. The set looks like the following screenshot. All of the display surfaces are LED Screen plugin objects with dimensions and pixels set correctly in the OIP as indicated: The image on the LED screens is set in "Edit Array Image" where a custom texture is selected. Notice that the Scale is set to 50% to get the image to display correctly (the illusion is a stack of TVs with different images). The image used for the texture is only two TVs wide, so this makes sense as applied to the still image in VWX. Changing this scale, however, has no effect on the eventual video mapping problem that we shall see in Vision. I tried exporting MVRs with all of the Scale adjustments in this menu set to 100% and had the same results that are illustrated below. I also wonder what the "Capture Source Name" and "Capture Source Number" are in the "Select Vision Video Source" dialog. These names do not correspond to the names that Vision ends up asking for, and you could put Fred or Ethel in the "Capture Source Name" field and you never see those names come up again throughout the process: But let's not get distracted... OK, so now we move over to Vision, after exporting the LED tiles in their own MVR. The set carts that they travel in get exported as a separate MVR to keep things organized. These two MVRs plus my Amphitheatre MVR merge together in to this model: Let's begin by selecting our first LED array (in this case the 4 tile square array top center) and choosing Assign Video Input: We assign the video input a name: The video input is fed via NDI from a MacBook Pro running Resolume Arena. The NDI monitor on the Vision PC shows a smooth, steady video image in real time: We find the 1920x1080 NDI input that is being scaled by 1/3 to give us a raster of 640x360 for use in Vision. So let's crop the NDI stream! I scaled my 1080 template down to 640X360 in Photoshop to determine the exact corners of every crop and wrote them down (analog, in a notebook with a pencil) because the cropping tool in Vision is rudimentary at best. You can't zoom in on it, there's no grid or snap guide... best to use the tools in Photoshop and write down the pixels. So we get our square crop for our square video surface: And we do it for each of the LED screens in the model: During this process, plan to spend a lot of time looking at this screen, waiting for Vision to "see" the NDI input that it "saw" just perfectly moments ago: Eventually we have created 13 separate crops of the NDI raster and mapped them to our LED screens. And here is the confusing result: Note the different scaling of the crops! Nothing seems to work out right, except the SR High and SL High set carts! The 2wide x 4high carts are the only ones that display the crop faithfully. The Ctr Top crop is perfectly square, mapped to a perfectly square screen. It ends up stretched vertically. Ditto the Ctr Bottom... that one is stretched vertically and doubled. The math certianly does not work for the downstage 3wide x 1high boxes. Playing with the texture scaling and offset in Vision does not help... You can't fix an asymetrical scale as is occuring here. If we use Vectorworks to create an LED screen and send it to Vision, and Vision has the ability to crop an incoming NDI stream, why doesn't this just work? I did try sending the crops from Resolume as separate NDI streams but Vision could not see them as separate. Any help would be appreciated. Getting this model to work will greatly increase the chances that it will be useful to me before we get to rehearsals. Thanks peace aj peace aj
  6. @klinzey Thanks again for creating this post! I have been constantly referring to this post as I continue to refine the MVR workflow between Vectorworks and Vision. I believe that I may have found an error on the MVR export. Specifically I have been working with Image Props using some stock characters. It seems that the "main" image texture steals the "Transparency" image upon MVR export. All shaders set to "Image": I still don't know why the preview looks transparent. Just to verify, here is the Image in the Color Shader: Reflectivity, Transparency and Bump: And here's the result in Vision: Here's what the unzipped .MVR file looks like: As you can see, Greg Front.png (for example) is the same image as Greg FontMask.png If you go in to the textures/scene folder that is generated when you save the Vision scene and duplicate Greg FrontReflectivity and rename it to Greg Front.png, then relaunch and load that scene, you get happy results: So I think that this is a verifiable bug, and perhaps an easy fix? The workaround is quite tedious. It's also a bit tedious that Vision has to create a separate folder for textures. One of the things that I love about Vectorworks is the fact that it imports your images and saves them within the Vectorworks file so you don't have to manage your textures outside of the application. Perhaps there's a way to package this info in the .v3s file and give us a simple Resource Browser functionality within Vision? I hope someone's listening here. I put a lot of time in to figuring this out... peace aj
  7. @bbudzon I was really going to throw this gaming laptop in the street until... Vision became unresponsive for so long that I force quit the app. On relaunch, I took the advice to "reset all defaults and run in Safe Mode" That helped considerably. Damn! I have seen this dialog before, but would plow through without going "Safe" just to keep my window layouts, etc. What exactly is "Safe Mode" then? Is it something I have to turn off, or is it just some misleading vernacular? As in... does the resetting of defaults then start you off "Safe" so you can go screw it up again by messing with texture and haze settings? Is there a way to accomplish this without forcing the app to quit to get the dialog on relaunch? I couldn't find such a function in the Vision app. Putting some settings back to the way I want them is a small price to pay... when this happens again I'll be sure to reset and safe mode the hell out of it. Regarding the different handling of VWX vs. Vision geometry... It has been a habit now for some time to convert what I can to either Mesh or Generic Solids for export. However, is this simply handled in the .MVR export process anyway? There don't seem to be any controls for polygon reduction on MVR export, but VWX Extrudes, for example, must be getting converted to end up in the MVR package for other applications to use? Thanks again peace aj
  8. I'm trying to understand why Vectorworks can save a very complicated file in seconds, and a Vision model built from the very same information can take several minutes to save? I know my Vision model is getting "complicated" but it's really not that huge. About 12 universes of fixtures, some moving trusses, etc. I'm very conscious of the polygon count vs. model responsiveness ratio, but the model performs quite well. When just saving the file, however, it means a coffee break. Seriously, it's taking 3-5 minutes to save the model. Any ideas?? Thanks! peace aj
  9. @JustinVH Where would I go to reach out as you suggest? I have been told to post things here because you guys are always reading the forums. Interestingly enough, cutting and pasting the geometry right back where it was brought it back properly in the destination file in which I was trying to use the symbol, but the same workaround did not work in the source Ampeg file. Weird. Thanks for responding... perhaps I could send tech support a link to this thread so I don't have to type all that out again?🙂 peace aj
  10. Here's a very interesting problem, which I can describe with screenshots. Some 3D geometry becomes invisible upon either using or editing certain symbols in the Vectorworks Library File Speakers Ampeg.vwx that comes in the standard Vectorworks Library. Here's a sample speaker symbol as it appears in the Resource Manager when you first browse or open this file: If you either Edit 3d Component from the Resource Manager or add the symbol to a Design Layer, the geometry appears properly in Wireframe: But when you switch to OpenGL mode, much of the 3D geometry is invisible!! If you hover over the Generic Solid that makes up the back part of this speaker, it is visible as a selection: This happens with several of the symbols in the file. It also happens in other render modes besides OpenGL. Importing the symbol to a new file does not help. Copy/pasting the symbol in to a new file does not help. This happens in the unmodified version of the Vectorworks Library file, whether you open the file or just try to import the symbol in to a new file from the Resource Manager. I opened other similar Vectorworks Library files at random and could not find the same problem. A copy of this file is attached as it was downloaded from the Vectorworks Library, from which these screenshots were generated. Can anyone else confirm this problem or provide any insight as to what would make this happen? Thanks! peace aj Speakers Ampeg.vwx
  11. Here's a weird one... Out of nowhere (which usually means I hit an errant shortcut key without knowing it, toggling some obscure option)... When changing to a standard 3D view like Front or Right Isometric, all of my geometry disappears... and one or both of the ruler bars go yellow! Nothing is deleted, but everything disappears. Selecting Top/Plan or Top brings it back, but using the Flyover tool makes everything disappear again. Exiting and restarting the program does not fix this. And of course, the problem comes and goes. I thought it had fixed itself for a moment, then it re-appeared. I was able to cycle through several views in 3D for a moment, then this started happening again. The ruler bar doesn't always go yellow, but sometimes the numbers just disappear. Any ideas as to how this happens? Screenshot of yellow ruler bar attached. Thanks for any help, peace aj
  12. Has anyone tried to replicate the problem with these files? As soon as I could reproduce the bug reliably, it all went silent in this thread... peace aj
  13. @Pat Stanford The problem reappeared after re-loading the default Spotlight workspace and changing only those specific shortcuts to create a new workspace. This was the only change that was made; other than that it is essentially the default Spotlight workspace. I had abandoned the old workspace that was a result of migration. Once the problem reappears, switching back to a default workspace does not fix it without a restart. The new workspace (with just the shortcuts changed) works... for a bit, then the problem reappears. This happens in a document with just one slightly rotated extrude for testing purposes, using the faces as working planes for this tool to select. The problem seems to occur when one of the shortcuts is used to change the view. Changing views with the drop-down menu is fine. Plane tool works fine if views are changed this way. Double-clicking the Plane tool reverts Working Plane to Layer Plane as advertised. Then if the view is changed using one of the shortcuts, the Working Plane gets stuck on the next selection and the tool stops working. Attached are the simple VWX file and the new workspace with just the keyboard shortcuts added. I was able to replicate this problem as described on a different computer using these two files. On the new computer, it took a few view changes via shortcut before the problem happened, but it still did. Again, this workspace is based of the latest Spotlight workspace with just those 9 keyboard shortcuts added. Ctrl-Shift-Alt UIOJKLM<> are the shortcuts for the views laid out like a numeric keypad. If anyone else can replicate this using these files then i'm not losing my grip... i hope that's the case!! peace aj just a cube.vwx PlaneToolProblem.vww
×
×
  • Create New...