Jump to content

Haydenovative

Member
  • Posts

    207
  • Joined

  • Last visited

Everything posted by Haydenovative

  1. Hey Gang, More venting than anything but if someone has a workaround that would be great. So I build a venue, I place the production elements and I hang a few lighting fixtures. I'm not really interested in focussing them and turning them on, I just want them there because they will be there on the day, but I'd like to continue working on the show in open GL or taking renders of the show without the lighting fixtures on and alas I'm in the dark. As soon as I add one light to a drawing I lose all global lighting even when the light is switched off. Is there a way I can retain "Normal" lighting conditions after placing a lighting device without deleting or turning off the layer with lights on it? I have in the past duplicated the lighting layer, selected them all and converted to 3D polys and turned of the "Actual" Lighting layer so I can do renders with the lights hanging in the ceiling but with global lighting on, it seems its a whole can of worms once you add lights as you have to adequately light the entire space with house lights etc. and render times go through the roof. Any ideas? Thanks a million!
  2. Hey Gang, I'm not even quite sure where to begin. I work in entertainments so perhaps this doesn't apply to everyone. My issue is around viewports on sheet layers and the export of those images. Can I start by asking if someone can confirm my theory: a 300dpi viewport on an A3 sized sheet layer (Assuming the image is scaled to fill the page) will have 4 times as many dots (Pixels) as a 300dpi viewport on an A4 sized sheet layer because there is 4 times the area to cover? So my confusion is really around the correlation between sheet layer size (in mm or Inches) and the dpi of the viewport. I've arrived at this issue because I have A4 landscape sized sheet layers and I've created 16:9 viewports from renderworks cameras. Should I adjust the size of my sheets to be in 16:9 ratio as well so as I am not exporting white sheet when I export image files? On the matter od exporting image files, I've found enormous discrepancies in quality between exporting the whole page VS exporting just the viewport via the marquee tool. Isn't dpi dpi no matter how its attacked? Why isn't there an export viewport option within the export image file window, if the viewport doesn't completely fill the page every export option apart from Marquee will export the white section around the image. Odd. So what I would like is to find a best practice for our whole company, to make the best quality image with the smallest file size. Exporting renders in PDF form is unreasonably large. Thank you so so much for taking a look at this, I look forward to hearing from others who've been in this boat.
  3. Hi Bruce, This is not something I can reproduce, perhaps its a mac issue? Im on windows. Does it happen with every drawing? Could you get a blank document to replicate it and post that, Ill give it a crack here.
  4. Hey Team, Just a follow up on this since November. We have not yet seen a fix for this and its still a significant headache for our office. We are still having to edit the registration on each machine when we wish to use a dongle other than that of the dongle used during the installation process. Thankyou to OzCAD for submitting this, we eagerly await a fix.
  5. Hey Guys, Just a quick update and for anyone else who has this problem. The issue is a corrupt workspace file. Everything else seems to be in working order, but tis is unresolvable without rebuilding our custom workspace from scratch. Backup often! Thanks heaps!
  6. Hey Guys, Bit of an update. Ive spoken to our distributor and discovered that unified view has something to do with all of this. When its on I get the disappearing act, off they work the way Id expect them....still odd. HTH Update: This is what I have Received from OzCAD "Hi Hayden, There are a few things that influence this. For 2D loci, if you have Unified View checked in the View menu, then they will only appear in a Top/Plan view because they are considered 2D objects. 3D loci visibility can be controlled via the Display tab in Vectorworks Preferences. But I think there could be a little bug here because the behaviour in 2015 is a bit different to 2014. I will report it and see what they say" "Just confirming this is a bug. Hopefully it will be fixed for SP3."
  7. You Guys are legends, thank you all so much! I still seem to have the problem though. Ive placed the 2D loci on the design layer, in layer plane. Ive got show screen objects ticked, its solid, its black, its layers and classes are on I can see it and move it in top/plan but as soon as I go to ANY 3D views its gone, again, if I hover over it or select it I can see the highlighted Loci but theres no black lines. I open a new drawing, go to front view, place a loci and it doesn't appear, again hovering or selecting it works, but its not actually there. I don't believe Ive played with any setting beyond the defaults. 3D Loci are the same. Visible in top/plan but disappear in any 3D view, again it highlights. hmmmmmm
  8. Hey Gang, I feel like I'm having a very amateur moment here, and its perhaps that I haven't used Loci since upgrading to 2015 so maybe there's something there. I cant see 2d loci in any view other than top/plan and no 3d loci at all after placing them. If I hover over where I know they are they highlight but they don't stay. I've checked that the layer and class is correct. I don't see any other forum threads discussing this so perhaps its me. Can anyone shed any light on this one? Thanks a million!
  9. Hey Gang, I've noticed an odd anomaly and Id like to see if anyone else is experiencing it and may know a fix. I have tried to open the visualisation palette through Window>Palettes>Visualisation and I get the OIP palette pop up. Upon further investigation I've discovered toggling resource browser on and off I get Working planes palette, navigation now = Resource browser. So currently I cant bring up the visualisation palette at all. Very odd, any help? Thanks team!
  10. That's a very reasonable answer! Im actually glad it wasn't something I had completely overlooked. This is the way it will live now. Thanks a million Mr Dunning!
  11. Hey Gang, I've got a noodle scratcher. I'm trying to add a Dortron Theatre bar to our library and unlike most lights where the loci would be at 0,0 this pivots oddly off axis. I've attached a quick picture and the working file to see if anyone wants to attempt to make this work like a hung light. I'm stumped, I'm interested to see how you will get there. Thanks gang!
  12. I have had similar issues with walls in every version since 2010. One that really got me was if the whole drawing had been scaled at any point the OIP height and actual height would differ greatly. The only solution I've found is to copy the problematic walls onto a blank document and back again. Odd, but I hope this helps.
  13. I have an odd one when using the select similar tool with the Other > Size option only selected as my preferences. If one of the symbols or items I'm wanting to grab is rotated in top plan view its no longer regarded as being the same size. I.e. If squares are what I'm grabbing and one of them is rotated 45° to look like a diamond, when I use select similar its no longer the same size in its eyes. This is quite unhelpful. Thanks guys!
  14. Id second this, Replcae would be great, we often get updated versions of the same base pdf from clients and we have scaled it etc to fit the elements we have added in 3D. If we could replace and have the pdf retain its scale etc this would be very helpful for us. Thanks!
  15. Hi Again Team, I have made a discovery, and like most things any new answer comes with questions. The answer to the original puzzle is that the serial number used to install vectorworks 2015 must be the serial of the dongle you are using. If you later swap dongles the new dongle will not be recognised at all, the serial number needs to be changed within the registry to the serial for that dongle. A hassle indeed but I hope this helps someone else.
  16. Thanks so much Jim! Looking forward to the outcome! You're the best!
  17. Thanks Jim, We have 'B' Licenced Dongles and at the moment it seems that they aren't working as they should. I know I've explained before but, during the installation process it asks for your serial number. If after installation the dongle is swapped with another 'B' Licence dongle the computer simply says it cant recognise a dongle and shuts down. In previous versions you would be prompted to enter the serial for the current dongle and off you'd go. This is causing enormous headaches for us here. Currently in order to use a dongle other than the one used to install the software you must enter RegEdit and change the serial within the registration.
  18. I'm intrigued Jim, Our computers are all connected over the network, but it has been my understanding that the dongles work as a key on each machine. Tis allows us to own four licences and spread them across the five of us here as well as allow them to use these on their laptops. This has worked for us well up until now but for this new issue. where we now cant move a dongle from one computer to another without editing the registry to change the serial number applicable for that machine. Please fill me in on how this server style connection might work, that could save a lot of time. Thanks so much Jim!
  19. Hey Guys, So with every answer comes a new question. We now have the issue where 5 of us share 4 dongles. The dongle used to install the program must be the one it runs with everytime. Whereas in the past if I grabbed another dongle on opening Vectorworks I was asked to enter the correct serial number and then Voila! With 2015 that has changed which lead to our original issue of the dongle not being recognised. I’ve now installed it for everyone and out current workaround is changing the regedit and re-typing the serial for the dongle were using that time. This is horrible and tedious and time consuming. I would love a fix that allows us to use the dongles the way they were intended.
  20. This is post SP1 update. Please remember we are running the OzCAD versions. I had already downloaded the libraries so that's not the issue, I have copied them across to several machines rather than re-downloading for each install, I was merely using the package manager to confirm that the libraries were in place and recognised. No biggy. Ill post any findings.
  21. Hi Guys, I have just installed Vectorworks 2015 and when I start the package manager I get an error message stating: Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately Index was outside bounds of array It then has a dialogue box stating See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IndexOutOfRangeException: Index was outside the bounds of the array. at Downloader.MainForm.SerialStringToProductFlagString(String serial) at Downloader.MainForm.MainForm_Show(Object sender, EventArgs e) at System.Windows.Forms.Form.OnShown(EventArgs e) at System.Windows.Forms.Form.CallShownEvent() at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- VectorworksPackageManager Assembly Version: 20.0.1.0 Win32 Version: 20.0.1.237820 CodeBase: file:///C:/Program%20Files/Vectorworks2015/PackageManager/VectorworksPackageManager.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Management Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- IronPython Assembly Version: 2.7.0.40 Win32 Version: 2.7.4.1000 CodeBase: file:///C:/Program%20Files/Vectorworks2015/PackageManager/IronPython.DLL ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.Scripting Assembly Version: 1.1.0.20 Win32 Version: 1.1.0.21 CodeBase: file:///C:/Program%20Files/Vectorworks2015/PackageManager/Microsoft.Scripting.DLL ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- Microsoft.CSharp Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll ---------------------------------------- Microsoft.Dynamic Assembly Version: 1.1.0.20 Win32 Version: 1.1.0.21 CodeBase: file:///C:/Program%20Files/Vectorworks2015/PackageManager/Microsoft.Dynamic.DLL ---------------------------------------- IronPython.Modules Assembly Version: 2.7.0.40 Win32 Version: 2.7.4.1000 CodeBase: file:///C:/Program%20Files/Vectorworks2015/PackageManager/IronPython.Modules.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Dynamic Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll ---------------------------------------- Anonymously Hosted DynamicMethods Assembly Assembly Version: 0.0.0.0 Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll ---------------------------------------- Snippets.scripting Assembly Version: 0.0.0.0 Win32 Version: 1.1.0.21 CodeBase: file:///C:/Program%20Files/Vectorworks2015/PackageManager/Microsoft.Dynamic.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. Any help?
  22. Victory! Ok, I now know the issue. In the 2012-2014 versions of Vectorworks you can install with any active licence number and once the program opens for the first time if the serial number doesn’t match the dongle it prompts you to enter the correct serial number for the dongle currently inserted (We have four dongles and they often circulate the office) I had installed this Vectorworks 2015 using one 2015 licence and had a different dongle in when it opened, rather than prompt me to type the correct serial for this dongle it simply didn’t recognise it at all, after updating the registration through Regedit.exe > HKEY_CURRENT_USER > Software > Nemetschek > Vectorworks 20 > Registration and correcting this I can now open it. This is a very small change, but inconsistent with previous versions. I hope this saves someone from the headache. Thank you Jim!
  23. Has anyone got a good work flow for achieving this, Ill tell you why I need it. I am drawing venue that sits in front of the Sydney Harbour Bridge and the Opera House, Id love to have as close to the real view out of the windows when it comes time to export Quicktime VR Panoramas. I've seen an external wall built around the perimeter and photos put of the four walls and it looks terrible, an HDRI with the image in it would be fantastic, any help would be muchly appreciated.
  24. I have to agree with ChadL We always export renders or images as image files, anything 2D we export as PDF, then we assemble them in acrobat for a much nicer file size. HTH
  25. Hi John, I've had a little play, the only sort of solution I have (And I hope it points you in the right direction) is in the spotlight > Architectural > Create Wall Projection If you draw a triangle of the wall you want on top of an area of wall, select both and create the projection it can create a wall with a feature that in 2D at least looks correct. I would imagine an architect would have more to say on this. HTH
×
×
  • Create New...