Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About symo

  • Rank

Personal Information

  • Location
    New Zealand

Recent Profile Visitors

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

  1. Many thanks @bbudzon & @BrandonSPP for coming back to me. Yes - I actually found that nvidia post and concluded that this was the reason my MBP wasnt allowing Vision to work. In the end - I installed Vision on an Asus laptop and it worked fine. So its looking like a VW2020 and Vision 2020 workflow for me. The only remaining issue for me is not being able to display vertical LX positions in a 2D layout - like I normally would - with the usual 2D labels. Once I find a solution for this (rather than having to show my verts in 3D with 3D labels) - I will be sorted!
  2. Im trying to find a seamless, efficient and reliable workflow between VW & Vision - and havent been able to crack it thus far. Having said that - Ive only just started using Vision - thanks to this becoming available in service select. The reason I work across Win & OSX is that I work in Win PCs at work and a Macbook at home. What I have tried.... VW2020 (Win 10) ->Vision 2020 (Win 10): Using Send To Vsion command. The only combo that has allowed me to successfully export to Vision. However, Im having serious issues with Schematic Views (which seem to be shared by others) as I do a lot of vertical LX positions and I cant seem to easily show my vertical positions in a simple 2D view with lighting labels. Im having to create 3D labels and show vertical trusses & booms in a 3D view to show the required info - too time consuming. I could export my VW2020 file back to VW2019 (for LX plots) but then I would need to rebuild my vertical positions. VW2019 (OSX 10.14) -> Vision 2020 (OSX 10.14): I prefer to work in 2019 as I can use Plot & Model View - not perfect by any stretch but at least I can show both 3D views and LX plots the way I want to. I can do this quickly. I cant use the Send To Vision command and VW cant find Vision 2020. When I try to export to MVR and open this in Vision, the Fixture Mode & Patch info isnt transferring. Do I need to separately values into the GTDF Fixture Mode Window for this to work? The help file mentions having to build GDTF files but VW already knows the fixture mode. Do I need to go to the trouble of building GDTF file via the GDTF website to get this to work? VW2019 (OSX 10.14) -> VW2020 (OSX 10.14) -> Vision 2020 (OSX 10.14): The idea here is that I do most things in VW2019, which means that I can do everything I need in VW, then open in VW2020 to tweak and export to Vision 2020. Everything (Fixture Mode & Patch) seems to export fine to Vision, but Vision crashes when I select a light fixture - every time. It does this after using both Send To Vision & Export To MVR commands. Ive attached the VW 2020 & v3s file for anyone who cares to try it. I would appreciate any wisdom here - cheers in advance. Vision Test File.vwx Vision Test File.v3s
  3. Sorry - visualisation lighting overrides for sheet layer viewports. So I create my SLVP from the design layer then tweak the lights from the SLVP.
  4. Hi Peter - yes sounds perfectly logical but had thought that the sheet layer overrides would take 100% control of these in the SL. But many thanks for responding - much appreciated.
  5. Ive actually found out thru another thread what the problem is - the light needs to be turned on in the design layer in order for shutters and gobos to render properly in the sheet layer!
  6. Well, that did it! Thank you so much. Would buy you a beer if I could. Id hate to think how long that would have taken me to figure-out.
  7. Having an issue where gobos arent rendering correctly in sheet layers. I read somewhere that rendering gobos is more reliable in sheet layers - and I have found this to be true. Heres a render of the problem: Gobo Render Issue V1.pdf The profiles over the tables should show dot gobos in all 9 of them - but they dont show in the render. I used a custom render with all setting set to low. I tried a final quality render - but no change. I have tried swapping-out the symbol, but this hasnt made any difference. Any help with this would be much appreciated. File here: Gobo Render Issue V1.vwx
  8. Having an issue trying to get VW to render light from light symbols that have had shutters inserted so that my stage wash doesn't light the ceiling, etc. The beam shows correctly in wireframe but not always correctly in fast & custom renders. This happens in both the design layers and viewports. I have made sure that the "soft shadows" check box hasnt been selected. I have done this successfully before. Ive tried different symbols but this hasnt fixed the issue My file is 150MB, so thought I would ask for anything obvious before trying to upload it. Cheers
  9. symo

    WIN 10 Meltdown

    Many thanks for that
  10. symo

    WIN 10 Meltdown

    So after a few days of pain, I finally have a stable VW workstation. Summary: It seems that my PC came back from the supplier in a broken state whereby it was missing some basic windows functionality (Microsoft Store). This became apparent when I tried to upgrade to Win Pro and my PC point-blank refused to do so - was missing the store app. After a few hours on the phone to MS support (who were actually very good and quick to call me), I reinstalled win 10 a couple of times and then upgraded to pro Ive managed to install all the right drivers & software and things seem to be running pretty good - PC performing well in benchmarks. The only thing that didnt work is the Aura app for LED control - but I can live without this. Are there any risks in enabling Windows Restore? I only like to restore from my system from Acronis backups if I really must Are there any other win 10 tweaks I should consider - now that Ive upraded to pro?? Cheers for all the help with this - hoping I get a few good months of pain-free rendering.
  11. symo

    WIN 10 Meltdown

    Cheers for that. Might need to do as woody says and upgrade to win 10 pro.
  12. symo

    WIN 10 Meltdown

    Got my PC back today and all seems to be well again. Heres what they said they did: Update MB bios Fixed windows folder which was corrupted by the crashes (but not reinstalled win 10) Updated all win updates Wound the CPU clock back from 4.4ghz to 3.5ghz. This was based on an earlier suggestion but they did this anyway. Im loath to crank it back up now its running OK - but may do a bit further down the track. Its running great - renders might be slightly slower - but I can live with that. They were adamant that there weren't any hardware issues - but seem to think it might have been a windows update. Ive learnt that some apps give false CPU temp readings - I was getting up to around 76° C mid-render with AI Suite. But have been using Ryzen Master which apparently gives much more accurate readings. Final quality renders are taking it up to 61°C max - so within the 68°C max limit. Adding to my woes were issues trying to restore from a "clean" Acronis backup - which ended-up being corrupted. Now that its running well - Ive disabled win updates as I dont want a repeat experience. Im thinking of doing this periodically - so I have more control of this. Is this recommended?
  13. symo

    WIN 10 Meltdown

    Hi Art V Cheers for that. Ive sent my PC back to the supplier - so I really hope they nail it. Will reply with any useful info I get.


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...