Jump to content

bbudzon

Vectorworks, Inc Employee
  • Content Count

    161
  • Joined

  • Last visited

Community Reputation

44 Great

1 Follower

About bbudzon

  • Rank
    Journeyman

Personal Information

  • Location
    United States

Recent Profile Visitors

648 profile views
  1. @Brickyoyo Are you able to verify this bug with other fixture make/models? Can you please upload your VWX? What version of VW and Vision are you running (include Service Pack details in the version)? Thanks! Brandon
  2. bbudzon

    Running Video in Vision

    I'm just a lowly Vision software engineer so I may need @BrandonSPP or another industry/VW expert to chime in/back me up here 😛 That being said, I can try to help with the capture device stuff as much as I can. Use the "Select Video Source" dialog in VW to assign video files to screens for Vision. If you wish to use a capture card for live input in Vision, you can assign a name/number to designate a unique video source from VW. Once in Vision (assuming we've properly detected your capture card), you will be prompted to select a live video source for the "live input texture" you assigned on the VW side. These sources can be cropped inside of Vision if you so choose. Please refer to this tech bulletin as it has the most amount of detail in it: No you do not. Screens playback cannot currently be controlled from within Vision. If you are using a capture card with Vision, please use the output device for media playback control. I'm not quite sure how to do this on the VW side of things as I primarily work on developing the Vision product line. I'll work on getting someone internally to work on drafting a response to this part or to reach out to you directly.
  3. bbudzon

    Video Capture Cards in Vision

    All really good info! It's hard to say what's going on here though... 😞 Why don't we try to work together on getting a list of hardware with known issues. I'll pass this along to upper management so they can look into purchasing this equipment for internal testing. On another note, do you guys have any additional hardware you may be able to test with? Even if it is just a web cam or something like that?? Truly, any UVC device should do for testing. I just want to confirm that this problem you are experiencing is specific to the hardware.
  4. Very interesting!! Thank you so much for the info!
  5. I did not know about Color Temperature crashing! We'll investigate that and hopefully have it fixed soon. In theory, it should never be needed but it is there for precisely this reason! Very sorry, again, and we'll look into getting the crash resolved. On a different note, I looked at a "James Thomas 8-light Molefay" and it's color temperature is set to 3000K. On the other hand, a "Generic Par 64" has a color temperature of 3200K. I'll have to pull @Mark Eli in on this one as he would be the one to correct the default color temperature for these fixtures. Edit: Do these values line up with what you are seeing in the Properties Palette for the fixtures you are using? I know that changing the value in the Properties Palette crashes Vision, but I'd just like to know what you are seeing in the Properties Window for the color temperature of your molefay and your par64.
  6. bbudzon

    Hog 4 Connection

    I'm sorry @nakedeye, MANet and HoggNet are only supported on PC at this moment. HoggNet we may be able to get working on MAC OS, but MANet is restricted to PC by GrandMA themselves.
  7. bbudzon

    Missing textures

    This bug should be resolved with Vision 2019 SP2. The issue was that we thought the file was temporary and so we cleaned it up when we shouldn't have. If you are running SP2 and still experiencing this issue, please provide the files you are working with a steps to reproduce the issue, if at all possible. This will help us resolve the issue as quickly as we can.
  8. bbudzon

    Source 4 Shutters in Vision

    I believe this is a bug that I've already fixed for SP3. Keep an eye out 😉
  9. bbudzon

    Vision Questions

    Hello @zeroInf! I'll do my best to answer your questions. The lens is sticking out of the fixture a little bit for historical reasons. Vision has never modeled fixtures "hollow" with a light inside. They've always been "solid" with a lens "where light should come out". Due to the way this is calculated, sometimes this results in the lens floating a little bit. In our experience, this usually goes unnoticed, but I will definitely pass this information along to the higher ups so they are more aware of the issue. LJ nailed the "Enabled Shadows" option. This will decrease performance but allow shadows to be cast and for light to "hit" a wall. I'd have to check with our content team to see why this fixture wasn't provided a "lightmap" (which is the way in which we "fuzz" surface lights to be more wash-like and less spot-like). LJ also nailed the bloom stuff. I'd actually recommend using pretty low settings here. Sometimes I'll use 1/1/1 for the three values. I usually end up bumping up the Bloom Lens Strength (to say, 5 or 10, maybe more based on taste) and lowering the Bloom Strength (to say, 0.5 or 0.1 even, again to taste). If you don't like this feature at all you can set Bloom Strength to 0 and it will disable it (in theory you'll get slightly better performance as well). The software console you're referring to in Vision was intended to simulate a stage hand. Lights that do not have pan/tilt dmx parameters must still be able to be focused in Vision. This is what the built-in software console is for. If you need to focus movers, please use one of the supported DMX Providers such as sACN or Artnet. Point and line tools are pretty worthless as they represent 1D and 2D geometry. Vision (and most previsualizers) only care about 3D geometry. The workflow that is recommended here at VW is to use VW to do your modeling and Vision to do your previsualization. LJ also nailed the XForm's setting 😉 And while I will pass along the information about controlling smoke machines and multiple cameras, I can already help you with the toolbar size! If you right click the toolbar, you'll get a context menu where you can set whether or not you want tool text beside/below the tool or not shown at all. You can also pick whether or not you want gray scale tool icons. Lastly and arguably most importantly, you can select the tool icon size from this context menu! Hope that helps!
  10. bbudzon

    Video Capture Cards in Vision

    Thank you very much! I know this doesn't really help the situation, but I wanted you to know that the software is not limiting things to the best of my knowledge. Here is my 2015 MBP webcam resolution in Vision and in Quicktime; both are 720p. That being said, I'm concerned that maybe your hardware is hitting an edge case that we didn't account for. I'd like to investigate this further as it is unexpected behavior. I'll talk with upper management about obtaining one of these "Ezcap 265/C" devices for internal testing.
  11. bbudzon

    Video Capture Cards in Vision

    1. Ahhh, hahahaha. That is pretty clever! There is no other way to tell unless you have access to the code. I just never thought of checking the resolution in the crop dialog before! 2. How are you opening your webcam/capturecard in QuickTime? I wanted to try this out on my end as well and am not finding very good information online.
  12. bbudzon

    Video Capture Cards in Vision

    Two quick questions: 1. Where are you locating the texture resolution in Vision? I just wanted to show you how things look on my end so you can see that it is not limited by the software. 2. Can you confirm that this stream can go above 640x480 in another application such as Skype?
  13. bbudzon

    Vision Running slow

    @thelightingguy I'm not sure if you were working with our tech support already or not, but I did hear about a customer who was having this issue (it just may have been you! hahaah). I believe they worked around the issue by switching DMX Providers?? (I have no idea why this would ever fix it, but it did seem to work around the issue for the time being.) One piece of information that I didn't receive was that it seems you are able to reproduce this in Vision 2019 SP1 but not in Vision 2019 SP0? Is that true? If so, it drastically helps us narrow down where the problem may be. FWIW, as well, I would recommend updating to Vision 2019 SP2 as it fixed a performance issue with SP1 involving multiple selections.
  14. bbudzon

    Video Capture Cards in Vision

    @Gaspar Potocnik I'm glad you were able to successfully get live input into Vision! About the 640x480 thing; you will need to make sure the device outputting content is configured for 1080p as well as the device inputting content. As far as I know, we don't limit the resolution of live video content. The webcam on my MBP streams 720p content into Vision without issue (720p=1280x720, which is a higher resolution than 640x480). So, it would seem there is no limit on this content in Vision or the capture library we are using. That being said, and this may sound weird but I'm promise I'm not trying to be rude!, perhaps we should figure out if 1080p content is actually needed. Or from another point of view, what would be the benefit of feeding HD content into Vision versus lower definition content? Think of it this way, feeding 4K content into a 1080p television does no good. It will simply spit out a 1080p image and the human eye will be able to tell no difference. Bringing this into the Vision world, let's say you have a 1080p monitor. This means you have 1920x1080 physical pixels on your monitor. Odds are, that, the television is not taking up half (or even a quarter) of your Vision Render Viewport on your monitor. If I had to guess at an average case scnario, I would say televisions usually make up ~10% of the pixels that are rendered. What this means is that your television in Vision is likely using less than ~320x200 pixels in the render viewport. This is where feeding 1080p content does not increase quality but decreases performance (even if only slightly). phew 😛 So, while it may seem like feeding 1080p/4K content into Vision would result in a higher quality, more times than not it won't. I think 640x480 is a sweet spot for quality/performance, but to be completely honest you could probably even go lower (320x240 would probably still look pretty darn good and obviously takes a quarter the amount of time to process). Hopefully that answers all of your questions and hopefully it is more clear why it may not be the worst thing in the world if you're getting non-1080p content.
  15. bbudzon

    Keyboard shortcuts

    @DBLD I spent a decent amount of time in the 2018 release getting the shortcuts and mouse movements to line up. For example, spacebar boomerang-activates the pan tool in VW and Vision. Middle click also activates the orbit tool in both VW and Vision. I believe we are both using the same key for toggle multiple viewports as well (even though Vision can only do 1 or 4 currently). Obviously things like Undo/Redo/Cut/Copy/Paste should be the same in both programs as well. If there are any shortcuts in particular you find are inconsistent, please open a JIRA ticket and we will work on getting those issues resolved!

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×