Jump to content

MattLXdesign

Member
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

3 Neutral

About MattLXdesign

  • Rank
    Greenhorn

Personal Information

  • Location
    Sydney, Australia

Recent Profile Visitors

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

  1. To add to observed issues with DLVP's lining up - I regularly reference external files while drawing lighting designs. Both venue and set plans are external so I always have the most up to date version in my plan. Previously I just had to make sure the internal origin's lined up, set the user origin to the internal origin and everything works. Now with VW2021 this is no longer the case which has me pulling my hair out. Which I don't have much of. Happy to lose it if it means my DLVP's line up again. Correction - It seems my user origins are drifting when updating the file to 2021. Resetting the user origin the internal origin has fixed the problem and I get to keep some hair.
  2. After some dinner and a beer I have made a discovery which I'm sharing here for anyone else finding the lack of colour information for generic fixtures transferring from Vectrworks to Vision ultimately frustrating. If you edit the fixture, either by pressing the edit button in the OIP or double click the fixture you can edit the colour wheel of that instrument. Unfortunately you can't just type the colour by gel no. but if you have 'Active Document' selected in the colour picker you will see the colour name show up when you hover the mouse over the appropriate colour. This will transfer from Vectorworks to Vision every time. I'm sure that between now and when the theatres open again I can write a script to automate that.
  3. I'll play around with exporting only the updated fixtures. I really only use vectorworks for producing plans for the crew to rig. Right now seems a good time to play around with visualizers, which have never really clicked with me. So I know I'm a harsh critic. Hopefully exporting updated fixtures only will prove far more workable. But I can predict that having to reassign the colour to every fixture when I send from Vectorworks to Vision will be enough to prevent me from using Vision after a couple of plans. I thought it worth leaving a comment. Everything else about is has been very easy and intuitive.
  4. I would like to add a plus one to Jake's request here. It seems crazy to have to manually add the colour to every generic fixture in the rig. And then to have to do it again when you make an update on your plan would be enough to convince me not to use Vision. Which is a shame because I'd really like too
  5. What would bring them into the same ballpark? In my example above I'm only working with ~5m throw. Just tried in a larger venue with a 19deg and ~20m throw. No problems. Work exactly as I would hope. So there must be a minimum throw distance for the "Use Vertical Beam" to work. Still sounds like a bug to me..........
  6. Here's what I get. Top view vs side elevation.
  7. That's odd because I just measured the beam angle from a fixture set to "Use Vertical Beam" which is a 50deg Source 4 and the beam measures as 119.49deg from a section view. From a top plan view the beam measures as 67.42deg with "Use Vertical Beam" toggled on AND off
  8. I am having exactly the same problem. Using the same VW version as mjm. 2019 SP2 Build 463397
  9. Found a work around. Place two Typical Label Legends in the Instrument Summary. One of them will stick
  10. One more thing - I hadn't realised the problem only begins after refreshing the symbol summary, although that absolutely matches my experience. So I created a new instrument summary which restored the typical label legend for me. Except the scale was incorrect. Defaults to 48 rather than 25. Why does the instrument summary tool not default to the same as the active design layer? I could rant about that for hours and will to myself later. Anyway after correcting the scale the Typical Symbol has once again disappeared and this time will not reappear when creating a new instrument summary. Why am I paying so much for yearly upgrades when they do not work??
  11. Much as the title suggests. I've been finding the cable tool extremely confusing as none of the cable and connector type drop down menu's contain any familiar options. The ability to edit or custom create your own connectors would make this tool infinitely more accessible
  12. +1 on this I'm just playing around now with setting up the remote on my tablet so I apologies if my comments are a little off the mark. BUT. I'm seeing a lot of potential that is not being realised. Such as I cannot find any access to selecting tools or symbols on the remote and being able to interact with object info would free up a lot of much needed real estate when using my latop for drawing. Anyway just my two cents on what could be an extra tool which would fast become an indispensable part of using vectorworks on a laptop. Cheers, Matt
  13. A little different in that i'm running VW on linux via wine but i had the same problem on my desktop. I worked around that by installing the native linux version of adobe air then on the VW install disc you'll find the file Vectorworks2010Help.air in the Adobe AIR Help System folder. Open that with the air application installer and you should be away. At least that worked for me. Matt
  14. There were a few things i had to install first. I used winetricks to install gdiplus, dotnet (i installed versions 2 and 3), visual basic runtime (i installed all version winetricks offered), visual basic C++ libraries (once again all versions on offer). I think that was about it. Strangely the help system installed straight up on my laptop but not my desktop. So i installed the native linux version of adobe air and installed VW help that way. It only means i have to launch VW help externally. One other sometimes frustrating thing is copy and paste doesn't always work properly. I can always copy from a native linux ap like say open office into vectorworks but copy and pasting within VW or from VW to office does not always work and it often pastes the last thing i copied from office instead. I'll report this as a bug on the Wine bugzilla when i get the chance. Oh another one for the Wine bugzilla guys is creating or editing text within the drawing area can cause VW to crash. Copying from Office into Vectorworks works around this. Having looked through the wine forums i'm quite confident the wine dev's can fix these problems reasonably soon after i report them. Cheers, Matt

 

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.

×
×
  • Create New...