Jump to content

RickR

Member
  • Posts

    620
  • Joined

  • Last visited

Everything posted by RickR

  1. I do this regularly, but mainly by simply drawing the other side. As a feature it should automate width, alignment and placement changes which require extra work with manual arrows.
  2. Fortunately this is not the case. (I just downloaded a new version to be certain.) I suspect you have confused full show capable output with 'off-line w/vis' mode selected. But many things have changed since that article was written. Any Eos console including Nomad can output several network protocols. Offline w/vis mode is not suitable for performances or client videos due to the copy protection ETC has in place. Every few minutes the output flashes for a few seconds!! This looks horrible but it brief enough to ignore for pre-programming and learning Eos. In fact one can easily use their pre-built vis files, provided free along side of the videos that use the very same files. If you are having trouble, I suggest making sure your computer is on a network. sACN is the default output, but ArtNet is availble. Either one sent out your network port for your switch to send back to Vision.
  3. I just re-found Pat's "Worksheet from PIOs" script. That got the field data I need, I should have recalled that handy thing. I have found some oddities with Linear Array and Mirror nodes. While the array function worked before, it did show some strangeness and doesn't seem to be in the current libraries. Details are noted in the file. It's looking like my 'current' origin is somehow moving around, at least that would be one explanation for the Mirror oddities. Traveler_with_stacking_v2.vwx
  4. Both are zero points on the internal X,Y measurements.
  5. You sent a list of parameter calls for Softgoods objects when I started my biggest project. That PIO has undergone some rework for 2017. Can you send a revised copy? For that matter a list of changed nodes (ongoing version to version) might be useful. A note as to a rework or a minor update would be fantastic. The question to answer is do I need to update a node and if so what's changed? I'll be someone on the development team has such a list even if you don't!
  6. My thoughts too! I've also had issues with objects not showing even though their class is on, and with alignment of nearly identical objects. Bugs abound!
  7. I expected so, it's why I haven't done anything yet!
  8. Time for me to update some of my small projects. I've been limping along with what I did in 2016, so I haven't taken real advantage of the cool rework in 2017. Is there a way to bulk replace nodes existing networks with new versions? Since nodes can be edited in place they aren't truly referenced resources. Importing new versions doesn't change anything. I'm envisioning something like the symbol replacement function, but I can't seem to find a way to do that trick. Right now I'm thinking that rebuilding it from scratch (next to v1.0 for comparison) is the best way to go. Ideas?
  9. There is one for Spotlight, but I find most of the users are inexperienced. I did first hear about SP3 there.
  10. The really odd thing was working several hours in a row without issue, then it all went flooy. Not even changing the monitor arrangement. Seems fine this morning even before rebooting. I did several other things yesterday, rebooting, open other files, exporting via Publish worked (it was just the menu call that crashes). I also opened my browser and posted here. RickR DxDiag 2.txt Oh to Pat's questions: Fonts and symbols is probably all the files really share. One years old, one new. They might have been made from templates that were made from the same one years ago... Most of my text is in Arial but there are oddball ones imported via DWG. But nothing new yesterday.
  11. A good thought but I think it's a system issue as 2 files run badly.
  12. Mondays! Several hours into a project I start getting crashes almost immediately upon restarting. Zooming, exporting DWGs suddenly are crash buttons. It's been 2 projects all day, both have been happy for months. Both do have some years old components (templates, imports, old file conversions) but really it's been smooth sailing. Tech support is now closed but I'm hoping someone is still working. I'm in Pacific coast time so lots of today still to go. Are there any new procedures for general troubleshooting? RickR DxDiag.txt
  13. Looks like sloppy work on the original symbol. You can edit the 3D and check it out.
  14. One of my first thoughts when seeing how Marionette works, that it would be a great flow charting tool. The way the mesh lines connect and stay connected as you move stuff around is ideal. I believe that there are some good electrical tools in Architect, but I've never really investigated. Might be suitable for schematics.
  15. I have often used non Marionette methods. Spotlight has numbering features, but attaching symbol text to a record let's you renumber in a worksheet. Copy & paste!
  16. You might also try changing your quality settings in VW preferences.
  17. There are some reports that it might be a video card issue. That's well beyond my expertise so I suggest calling tech support and see if your card has known issues.
  18. As photometric functions go, I find VW pretty limited. I've spent years doing advanced calcs with programs from older Radiance and Lightscape to the current Dialux and AGI32. They are far more accurate, but since architectural fixtures rarely have zoom functions they don't that either. To be honest I'm not sure how accurate any of the theatrical visualizers are in pure photometrics. I suggest you take your fixture data (like the original image) and use the closest approach you can in each instance. The more data you can get on each fixture type you use the better your approximations will be. Also recognise that there are major factors that can drop fixture brightness, old lamps, dirty fixtures, etc. No need to chase precision without accuracy.
  19. Since nothing in VW lets you change the zoom setting during rendering or photometrics, I just pick the setting I'm most likely to use. I suppose one could have multiple fixtures on many classes and render/calculate them as needed. When I set the beam and field as you suggest it's just to see the range of coverage when showing the beam. I'm not fluent with Vision but I presume it has zoom controls that replace the VW settings when the project is converted. Note that there can't be a universal relationship between zoom and candela. Each fixture uses it's own optics and so they behave differently and have different efficiencies.
  20. One of the issues with the built in tool is that the bounding box of the chair symbol has to be entirely included in the seating area. From what I see here you only require the center or insertion to be included. Ideally it would be the whole object. But it looks beyond my skills! I look forward to the finished tool! Thanks
  21. Well I'd rather you do it than have to do it myself.
  22. I've changed symbol names a few times to work better with worksheets as drawing legends. Really it's like changing the fixture type completely. It's a 3 step process; change the symbol name, change the name used by the instruments affected (in OIP of the spotlight objects), refresh all instruments (spotlight menu command)
  23. Very Good Point! Half a Solution: Two sets of default libraries. One with multiple classes, one with all on None class. Not pretty but easily done. Other half: check boxes for PIO behavior. These would remove some functionality but allow the choice between your way and my way.
  24. If you've updated to 2017 it does 3D legends. Then similar to Plot & Model you can just make a viewport of an elevation and lay that out near the plan view. Plot and Model has proven to be complex and problematic. Another solution I've used is to hand draw the vertical view with simple 2D symbols, then moved the legend components one at a time. It's a tad tedious if you have more than a dozen fixtures but it's very simple to set up and keeps all the data links.
  25. In similar situations I've removed walls to get a better view. Neither wider camera angles or impossible views hold to true photo-realism but careful use will give accurate impressions.
×
×
  • Create New...