Search the Community

Showing results for tags 'camera'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • Teaser Tuesdays
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment and Previsualization
    • Vision
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design
    • Terms of Service and Community Guidelines

Calendars

  • Community Calendar

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes

Found 9 results

  1. I wanted to check in to see if there has been any progress on the Video Capture bug I raised a month or so ago. I have another pair of projects at a moderate scale and I would prefer to use Vision for my projector layouts. What's the status of the camera inputs?
  2. Hi everyone Im getting an odd result with the camera match option. For the Camera Match object I have a photo with a nice and clear perspective view, making it very easy to manage and arrange the control lines (R1 R2 L1 L2 V1...). I'm uploading some pics and the VW file of the columns I want to add to a long corridor. Pic1 - the columns im trying to add Pic2- the Match opbject picture with the arranged control lines Pic3- the desired result Pic4- Camera Match result. Sometimes I get a message that the control lines are reversed, Im not sure why. any thoughts? thanks joey VW 2017 SP3 columna.vwx
  3. Attached are two screen captures. The first, a wireframe of my current camera view with my fixtures in newly laid out positions. The second, my same camera view, rendered using a custom renderworks artistic style, displaying my fixtures in their OLD positions.. Can anyone advise on why the render does not reflect what is drawn and shown in the wireframe camera view?
  4. What is the easiest way to update a camera after changing the camera values. Example : If you set a camera and you change the height of the camera and the camera look to height. The camera's current view does not update after the new setting are entered. There is no update camera button in the object info palette. So I was wondering if there is a future plan of adding an camera update button in the object info palette. I have figured out you can de-activate and the re activate the camera in the object info palette. Am I missing something here? Maybe something for future update! I dunno!
  5. Hi, I was wondering if there is a way of stopping the camera from clipping through the 3D model I've started on? I feel like it hasn't been a problem before, so I'm not sure if I've managed to change a setting, or if it's always been like this and I've just used the camera in closeups before. Attached is a PDF of a camera view, where it clips through and shows the floor underneath. Group Site English Key.pdf
  6. We use Vectorworks quite heavily in the office for 2D drawing, but are just really starting to get to grips with Landmark / Renderworks, and while I am loving it so far I'm not quite sure of the full extent of it's capabilities. I am looking to do some visualisations for a wind farm planning application, for which the levels of accuracy required by technical guidance for visualisation (published by SNH) is quite precise, and I'm not sure if it's something that can be achieved in Vectorworks or if I need to look at bespoke wind energy software (such as Resoft Windfarm / WindPro etc.) I need to be able to match a wireframe view of OS terrain information (for an area of up to 80km of Terrain50 contour shapefiles or DTM grid) with a panorama photograph, to an exact bearing direction and field of view. The wireframe needs to match the cylindrical projection of the panorama photograph (- i.e. NOT be in standard equirectangular / planar perspective as per a single standard photograph,) and the model will also need to account for the curvature of the earth and atmospheric refraction. My current feeling is this is beyond the realms of Vectorworks capability at present, (much as I would love this not to be the case!!) but I would appreciate the thoughts of users with more experience and expertise!!
  7. Cameras are still not working for me in 2017. Can we recap that issue a bit from scratch to get information and find solutions ? I try to sum up. Cameras worked for me fairly well in VW 2014-2015 : They worked fine even on Layers assigned to Story Heights. I could do Screenshots nearly full view window, by using "crop frame" Just 2 Problems occurred for me : 1. Sometimes, geometry far behind (!) the camera had the potential that a camera view showed no more lights when rendering, until that geometry was set to invisible. 2. If a Z-value was assigned to camera (in OIP), like I tried in a Staircase, the camera tend to shift its position arbitrarily. A known Bug. VW 2016 : Cameras got some new features. We can create, save and assign all features to Cameras. Maybe no problems if assigned to Viewports (?) But we can't securely switch between these in drawing Window. In that case at one time : 1. Cameras lost their Positions always, no matter if there was a Z-value assigned, a Story height or not. New XYZ locations values where for either selective or all Axes : nearly infinite like 1,00000000ß0000e200, origin 0,0,0 or the XYZ of another camera. 2. Camera and Target height for me sometimes change from mostly 1,60 m to 1,599999 or even more deviate values. 3. Camera Aspect Ratio Borders (the blue corners) only use a small part of the view Window of my monitor (about a third of the width) so no more sufficient resolution for screenshots. I think one or all following points came with different following releases of Service Packs 4. Activation Icons in Camera Lister at one point won't disappear again, the whole de/activation process was killed from that point, even in OIP or Camera Settings, until VW restart. Over time more and more Cameras will reach that state. 5. Cameras started to arbitrarily activate the old "crop view" in file settings, which is totally unwanted for standard 3D Views which will be effected too. 6. Cameras started to switch to a Top Plan orthogonal View inside that old "view crop" when activated for the first time. An UNDO brought the original Camera back some times and old "view crop" was deactivated again. 7. And last behavior change I noted, Cameras behaved like Saved Views and allways changed Layer Visibility by making their own Layer the Active Layer. Trying to switch back to the former Active Layer made them go nuts. VW 2017 : I did not test so much so far. For 2016 files converted using cameras already : 1. Cameras lost sometime their Position when only activated. 2. Cameras show even smaller area with blue corners when activated for the first time, while the perspective looks reasonable though. After switching between Camers the blue corners switch back to Camera Aspect Ratio in a ⅓ of View Window only size as usual for me. 3. Cameras active switch to a Top Plan orthogonal Perspective in View Window when I only activate the visibility of their Class to be able to edit. 4. Crop Frame Scale Editing inlfuences blue corners first, when switching back to 100% it has changed Focal Length (!?) That makes it a little difficult to convert running Projects into VW 2017 if I relay on the old Cameras: (Same for Reflectance Channel Changes) Creating Cameras in an empty File without using any File Templates works so far in first tests for me. But I have not yet changed any of the cameras settings or moer than one Camera at one time that I would usually need to do.
  8. I'd love to see Syphon/Spout integration for ESP Vision. The ability to share an OpenGL context from a processing sketch or other application into vision would make the workflow much easier for multi-projector preprogramming. Spout can be found here and has fairly wide support on the Windows operating system: https://github.com/leadedge/Spout2 Syphon is native in OSX and really we just need a hook to pull in the Syphon context in OSX. Is this a possibility?
  9. It would really be handy to have access to the camera effects in the viewport OIP if our camera is linked to a viewport. Currently if we want to increase/or decrease shutter speed or experiment with any of the other settings we have to edit the camera, make the change and then exit. It would really improve the workflow especially when we are doing this several times in a row as we tweek the lighting and effects trying to find the settings that are just right.