Jump to content

ericjhberg

Member
  • Posts

    581
  • Joined

  • Last visited

Everything posted by ericjhberg

  1. We have been trying to use the new Irrigation tools in VW2017, but are having some extreme difficulties. On top of the speed issues associated with a network recalculating after every adjustment, we have recently been experiencing repeated crashes while performing what should be basic commands. I have uploaded a screenshot video that shows the workflow and the associated crashes. It seems to happen everytime an object is connected to a pipe (i.e. valve, pipe connection, outlet, etc.) Any help would be greatly appreciated. Thanks. http://screencast-o-matic.com/watch/cDlr0QQtKK
  2. We have been experience a repeated crash in VW2017 when editing callouts and keynote legends using a database. Many of these problems are happening in files that started in VW2016 and have since moved over. The problem happens when editing text in the database, just prior to updating a keynote legend. I have uploaded a screenshare video that shows a couple of crashes related to this problem. I aplogize for the poor quality, but you still should be able to follow the workflow. It should be noted that we have been managing callouts in this fashion for some time and have only had problems in VW2017!
  3. We have been playing around with the new fence/railing tool and like that you can save as symbols to a custom location. It just so happens that custom location is only the USER folder. This is fine for personal storage, but in a large office, we need the ability to link this tool to a WORKGROUP folder as well. Of course, with the resource manager, custom symbols can be easily located in either location, but in the tool itself, it seems that the custom profiles are only loaded from a USER folder and not from a mirrored location in a WORKGROUP folder.
  4. I went back to 2016, created the texture, and then imported into a 2017 file. It came in and once it was there, I could edit it. But now the editor looks like this...
  5. It appears that the export options for COLLADA files increased in VW2017; however I cannot seem to get a file to actually export. I have tried multiple options in many different files. I have attached one here for reference. Any ideas, workarounds, or fixes? Senecio.vwx
  6. When trying to add a renderworks texture from a custom image or edit an existing texture from the resource manager in VW2017, nothing happens. I can't get to the normal dialog box that controls textures. Ideas?
  7. So...I have only just begun doing 3D modeling in 2017 and we are encountering a weird occurrence where the renderworks engine occasionally disappears. When attempting to apply textures to a class's properties or manually setting textures in the OIP, any texture options simply aren't present. It is as if the program doesn't recognize the rendorworks engine as being present. We never had this problem before when renderworks was a separate license, but now that renderworks is a standard inclusion in the software, this problem seems to be happening occassionally. I have found two fixes so far. completely closing the program/file and reopening...hoping that the issue is resolved. textures still appear in the resource manager? editing an existing texture seems to suddenly kick the engine in and apply it. I still have to reapply textures to existing objects though. Here are two screenshots that show the issue.
  8. Vlado, Sorry it has taken so long to get back to you on this. I have simplified a file with one POC and several stations. The issue here is still that we can't rotate anything. Everything, once connected to an irrigation network, maintains a true north orientation despite attempts to rotate. The "ROTATION" angle appears to change in the OIP, but the graphics do not respond. Of course this is okay when your model is oriented to true north, but we often have to rotate viewports and such to fit plans on sheets. This is also true of TAG/LABEL objects, which is perhaps more important since these are what appears directly on the plans and needs to be read horizontally if possible on any sheet. One thought is perhaps, to avoid the process of rotating everything after placing the components, perhaps the symbols could automatically orient to the angle of the incoming pipe. This could then be modified if occurances needed to, but it would be a pretty uniform starting point. In the file you will find a couple of "IDEAL" layers that have been exploded to show how we would ideally like to manipulate symbols. I have also recorded a screenshot video at the following link. It shows our ideal and the process of trying to rotate. http://screencast-o-matic.com/u/h0tR/IrrigationRotation Irrigation_Test_File.vwx
  9. Thanks for sharing. I understand your methodology, but the concept frustrates me a little. Layer management has become a huge issue for our office going forward. I would love if they would initiate a hierarchical or folder based layer system for both design layers and sheet layers. Something similar to what is already accomplished by the hyphen (-) in class naming. This would allow layers of similar infomation to be grouped together visually and keep the list from getting too extensive to manage. Some of our projects include over 50 design layers and sheet layers that are too cumbersome to navigate through now. The need for this becomes even more prescient when facing the ideal of project sharing...one file with everything in it! Almost too many layers to imagine!
  10. When using the new irrigation tools we are trying to determine the best way to share ONE master catalog. We are a multiple station office and need to be all sharing the same resources. The current 2017 installation puts the default catalog on the local C: drive; therefore, every computer has a locally different (albeit the same content) starting catalog. This catalog is extremely extensive, but does not contain ALL of the equipment necessary that we use on a daily basis. Adding catalog data is very straight forward, but the problem I noticed is when a workgroup individual user needs to add equipment to the catalog. This information is stored in separate .txt files in the user folder, but stored separately from any working folder setup. This means that no one else can access the information created by that user without going to the effort of moving and merging that data with the data in the workgroup library. We have a working library that everyone shares, is there a way to move the Master/Default content to that location and then when ANY user needs to add equipment, they add it to the workgroup location and not their individual user folder? Otherwise it seems we have to go through what could be a troubling copy and paste methodology to store the new catalog information. If this functionality doesn't exist, consider this a wishlist request that should be addressed ASAP to allow for larger offices to control the workflow of sometimes complex irrigation catalog information collectively.
  11. Sometimes you have to use the Remove Gaps button twice. Once to move all the gaps (NA) to the bottom of the list and another to remove them from the list.
  12. Ben, In order to solve this issue, we have created custom linetypes that contain square polygons. They can be WORLD-based and scaled to any real-world dimension you want. I have attached a couple of files (BOX LINETYPE_v2017.vwx, BOX LINETYPE_v2016.vwx) with an example linetype. You can edit the linetype in the Resource Browser/Manager and edit the Geometry of the line. This has been our work around to square line ends. The issue with this is that they don't appear when a class or layer is in GRAY state. The class must be active. You could create gray polygons inside the line type, but not gray the class. Also. it can get a little wonky for complex linework, so I would only recommend it on long, staight or broad arc lines. This is not a solution for the wishlist request of square line ends, but a work around in the meantime.
  13. I'm not sure if there is a way to link marionette to the new viewport visualization options?
  14. Thanks Kevin, that makes sense. I still don't think I was able to find the post regarding my question through the forum search though. That being said, I did figure out my answer for rounding up...just add 0.5 to the math before rounding and it will round up all the time. That being said I was looking for a ROUNDUP formula similar to the one in Excel. It doesn't exist but the adding 0.5 method is a work around. As for the search. I have found that google provided better search results in the old forum as compared to the forum search. I haven't used the search that much in the new forum, but when searching this particular question, it didn't return the results as well as google did (granted to the old forum posts). I guess it will just take time for the new forum posts to outrank the results in google search. I did find this morning that Google search did provide links to forum. websites now versus the old techboard. forums. You just have to take notice of the links. Thanks again!
  15. That's too bad. There is a lot of questions that will have to be re-asked I guess then.
  16. I am noticing that many of the old forum posts are no longer available. I often will run a google search for help articles relating to topics and find several posted forum results pertaining to my issue, only to find that the articles are still linked through the old forum and I can no longer access them. Since many of my questions have probably been answered at some point, it would be great to access all that information somehow. The following is a search that yielded a post with the direct question I was looking to answer, but I can't see the answers! https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=round up in vectorworks worksheet formula
  17. Looks awesome Stephen. Thanks for sharing. I love all the details!
  18. I agree with Robert, it has taken us a long time to get our standards more dialed in. They are never complete but we have gotten better at creating templates and standard classes to keep things like lineweights, fills, and hatches consistent. We are always tweaking slightly for every project, but it has helped tremendously to have a consistent starting point.
  19. Ben, I am happy to share a little of what we do here. The following are select screenshots from a park project we are completing. Of course, these are just screenshots. I can provide some better quality PDFs or other examples by request.
  20. YES!!! This is the logical next step that allows for more detailed graphical spatial analysis! My example is map data. I have parcels complete with population data. Dividing population by area gives population density. A couple of other recent posts on this topic
  21. I would like to add to this request. Yes, DROP SHADOW'S were added to V2017; however, a drop shadow is nothing more than a 2-dimensional offset of a shape and true shadows are much more complex. Consider a light pole. In top plan, the shape of the pole is a circle, but its shadow is more like a line and depends entirely on sun angle. Currently, the only way to do this is through a rendered view in TOP. The new drop shadow addition is a step in the right direction, but I don't think the shadow request should be considered completely fixed at this point. Someday...and I know its a ways off...I imagine an interface that removes the different between top/plan and 3d views but still allows for an orthagonal top/plan view for documentation purposes. Essentially the split between 2d and 3d disappears without sacrificing documentation abilities or realistic rendering capabilities.
  22. I've always tried to match RGB values because I too don't think VW is CMYK or HSV compatible. That being said, I have even noticed that after I enter a precise RGB value, the result will often skew slightly in one of the ranges by a value or two. It's never enough for me to be concerned, but I wish VW had a better color management, picker system. It would be awesome to have a color picker as part of the tool set. One that could match from both inside VW or from other open applications.
×
×
  • Create New...