Jump to content

bbudzon

Vectorworks, Inc Employee
  • Posts

    662
  • Joined

  • Last visited

Reputation

207 Spectacular

4 Followers

Personal Information

  • Location
    United States

Recent Profile Visitors

5,278 profile views
  1. Oh interesting!! I'm glad you found a work around. If you could post a VWX that demonstrates the issue with schematic views, that would be much appreciated!
  2. If ESC file is also not working for you, I would suggest posting your VWX here for us to investigate. In the meantime, you can focus them inside of Vision itself. I find the arrow key workflow to be the easiest. Just make sure the "focus" is in the view pane so that the arrow keys aren't navigating the Properties / Scene Graph Palettes. https://app-help.vectorworks.net/2024/Vision/2024_Vision/Vision/Focusing_conventional_lighting_devices.htm
  3. If you are using Send to Vision, it is likely using the MVR file format in the backend. I'd have to look at the code, but either Vision doesn't support focus points with MVR or there is bug in Vision causing it not to work. One workaround could be to use the ESC file format to export your lighting devices. You can also use ESC for your geometry, but the geometry will look better in Vision if you use MVR.
  4. I'm glad I was able to help! To answer your other question, only Vision Unlimited has more than 1 NDI Stream. So, I bet that is the issue you are running into. You could reach out to our sales team if you'd like to upgrade. You may be able to get away with combining two videos on the media server side into a single NDI stream and cropping it back into two videos in Vision. But, it will degrade the stream quality and is generally not as easy to work with.
  5. I believe they are kind of mixed in with the VW requirements since they are very similar. Vision requires a little bit higher end of a graphics card. Check the link below and search for "Vision" to see specifics.
  6. I don't remember what version we removed the remap from the Spotlight prefs. But, it is now hard coded. Here is a link to the help article which shows the new hard coded mapping: https://app-help.vectorworks.net/2024/eng/VW2024_Guide/LightingDesign1/Visualizer_data_mapping.htm
  7. I will sometimes see this if you accidentally have one or more objects in your VWX that are VERY far from the main scene. Vision tries to fit the entire bounding box of the scene in view when first opening an ESC/MVR from VW. Two things you can try: 1. See if you can hunt down any objects that may be far from the rest of your scene. Either delete them or try to leverage visibilities to stop them from exporting. 2. More of a workaround, but you can select an individual item in the Scene Graph Palette (such as a lighting pipe) and then use the Fit To Objects tool in the toolbar. This will zoom you in to that object. From there, you can likely navigate to a view you like and save the Vision file. Since the camera position saves with the VSN, you shouldn't have this issue when re-opening the file.
  8. Ok! That is good as Send to Vision should use MVR behind the scenes. I mostly wanted to make sure you weren't using ESC as it is a much older format and more prone to breaking as time goes on. That being said, you could try exporting an ESC as a workaround so long as you are not using GDTF. Could you post/dm your VWX for us to investigate? Thanks!!
  9. I'm just curious, are you using the Export ESC or Export MVR menu command? Or, perhaps, you are using Send to Vision? As far as I'm aware, this was working for all of the listed menu commands. But, if one of them broke recently, knowing which one you are struggling with will help us figure out what is going on more easily. Thanks!
  10. Are shadows working for regular lighting devices? I'd want to see lighting device shadows first to ensure your settings are correct before trying to debug projectors specifically.
  11. So, the reason you can only get one NDI stream working at a time is because your license is for Vision Plus. This allows for up to 4 universes of DMX and so only 1 NDI stream is unlocked. When your license gives you unlimited DMX universes, then you will get unlimited NDI streams.
  12. Can you post a screenshot of your "About Vision" dialog? This will give us information such as the build number and licensing information, and may help us answer your question.
  13. I just want to make sure you understand that everything should be set up in VW such that no work is needed in Vision. If you set up VW properly, all you need to do with Vision is open the MVR. So, I am assuming that you are not asking about inserting textures in Vision as that is a step which should not be required. If you are asking how to insert a texture in the VW application, there are probably dozens of ways to do so. I would highly recommend you checkout the help articles, vectorworks university, and/or training videos. I tried to find the "birds eye view" of textures in the VW Help. This should get you started and hopefully allow you the freedom to explore the VW Help to determine which technique you find easiest or most suitable to your workflow. https://app-help.vectorworks.net/2024/eng/VW2024_Guide/Textures/Creating_textures.htm EDIT: This link *may* be more helpful as I think it covers the application of textures and the various ways it can be done. https://app-help.vectorworks.net/2024/eng/VW2024_Guide/Textures/Applying_and_mapping_textures.htm
  14. It is important to "prep" the VWX properly before exporting an MVR for Vision. Video in particular can require steps you may not be performing. All that Vision does is replace the pixels of the RW Texture applied in VW with pixels from the video. So, the first thing is making sure you have a RW Texture assigned to the object which will playback video. One thing that I find very helpful is the built-in ColorBar RW Textures, as these come in various aspect ratios. So, if the video you are going to playback in Vision is 4x3 apply the 4x3 ColorBars RW Texture to the object. If the video you are going to playback in Vision is 16x9, apply the 16x9 ColorBars RW Texture to the object. While you are in VW, you can "imagine" the video replacing the RW Texture. So, make sure the RW Texture in VW is scaled and offset the way you'd like. Once all of this is done, you should be able to export the MVR to Vision. And, once in Vision, you should see that the video frames from your source are replacing the RW ColorBar Texture. This should give you the result you're trying to achieve.
  15. The setting you are looking for is Surface Light Quality. Normally, an NDI stream is played back as a texture on geometry using UVs. In this case, there is no beam or cast light. And so, selecting High Bandwidth will be immediately noticable. However, when an NDI stream is being cast as light out of a projector, there are other performance implications to consider. So, selecting High Bandwidth may not be enough to project a crisp clean image. I would suggest trying to stick with Low Bandwidth and setting your Surface Light Quality to High. If this doesn't work, try bumping up to High Bandwidth. If this still doesn't work, you can increase the Surface Light Quality to Very High but this will use significantly more VRAM. I hope this helps!
×
×
  • Create New...