P Retondo

  • Content count

  • Joined

  • Last visited

Community Reputation

23 Great

About P Retondo

  • Rank
    1000 Club

Personal Information

  • Occupation
  • Homepage
  1. dc, I take your point that it is logistically much easier to update maybe several hundred instances of a program on cloud servers than many thousands in offices around the world. Plus, that sounds like outstanding response to a bug! All the same, we theoretically have the ability to update our desktops - my internet security program does it automatically every day.
  2. Jim, is it really true that VW2018 will use more than 32 Gb RAM when rendering?
  3. Christiaan, I see your points 6 and 7 as being inherent to a cloud-based system (access from anywhere, easier sharing). Other than that, the rest just speaks to superior software engineering - which I will stipulate the software you like does have, given the high level of your experience. Yes, file management should be made more simple. I'm sure that if file management is better with Onshape, that is due to software, not some personal file management nanny assigned to the project. Updates should be smoother (if NNA could get their engineering together, user control over whether to update would cease to be a necessary thing). The biggest drawbacks in cloud-based are that we lose control of the tools and their management, and that we may be paying more for CAD - if not now, in the future. Good engineering does not come for nothing, and file management, access and server space cannot be free. If the cloud server goes down due to cyber attacks or other problems, all users will be dead in the water. If we are worried about files being pirated, wiped out by hackers, or just lost due to neglect, we will be at the mercy of the corporation to which we have ceded control. That concerns me very much, almost as much as parametric tools starting to dictate a narrow range of design solutions. PS: regarding the point of file security. Correct me if I am wrong, but the project files for a cloud-based CAD system will have to live on the cloud server. My assumption is that the CAD software is loaded on a cloud computer and works with that computer's RAM. Otherwise, every operation and processor request would have to travel over a very small pipeline between your desktop and the cloud. This means your desktop is just operating as a terminal to send commands and receive screen updates. The program is operating in the cloud, the application memory is on RAM on the cloud computer. So every file save is between the cloud computer and the cloud storage server, otherwise we would be waiting forever with every save and that would not work. The only alternative is that the cloud server file is just temporary, requiring that at the beginning and end of work on any CAD file we would have to wait for the entire file to be transferred over the internet. Slow, not really viable. That's why I assume we would have to give up physical custody of our work for this to be practical. BTW, I did check out this scenario for how cloud applications work with AIA Documents tech support, and they confirmed that is exactly how their system operates.
  4. But, Christiaan, is it the cloud or is it software engineering? What is it about being in the cloud that make any software inherently more usable or stable, or whatever? I would argue that better software is better software, regardless of how it is delivered or accessed, and that for my purposes as an architect seeking to have control over the security of my files, my ownership of my files, and my ownership of CAD tools, the cloud is not where I would like to be. The cloud is the place for those who sell time on cloud computers and want to monetize the use of software as a commodity instead of a tool, since we become totally dependent on them and their equipment. In this sense, selling the cloud as a technological solution as opposed to what it really is - a money-making scheme - that is a hype. When you say there is "no pushing in Onshape," I assume that means the document is actually stored on the cloud computer. It has to be for CAD work of any substance, otherwise every save from RAM has to go through the internet connection. That also means - drum roll - that your design documents now live on someone else's computer, subject to whatever insecurities that implies. Hostageware, poor management, shutdowns, going out of business, all outside your control. This is exactly why I no longer use AIA contract document software, all my contracts would have to be in the possession of the AIA and live on their server. Thanks, but no.
  5. I just asked one of my contractors, who is Chinese, about "who is the first to eat the crab." He had never heard of it, so I still don't know what that means!
  6. dc, I think the issue has more to do with engineering standards and corporate practices than it does with how the software is delivered or where it is installed. The cloud is, IMHO, a much-too-hyped magic solution. The big advantage is that you can use your workstation from any internet-connected location the same way computer "terminals" used to be used when we had mainframes. The big disadvantages outweigh that: 1) the user does not control and own the software, totally dependent on the cloud server's security, availability, and you have to pay the rent, and 2) limited bandwidth - which increases your dependence on the cloud server because you have to save files to the server and keep them there instead of on your own computer. We should be very afraid of such a technology model.
  7. Jim, this is not an answer to your question, but I am very interested in experiences with VW2018 which I have paid for but not yet installed because I am afraid of the type of problem you are experiencing!
  8. I've been asking for this forever. Having a script is a good idea, cberg. When I have some free time (i.e., probably never!) I'll look into it. It would be a simple matter of getting the z layer settings from the 2 layers and moving by the difference immediately after pasting in place.
  9. First positive comment I've heard from a veteran user regarding 2018! Could you tease me with just one or two examples?
  10. I have a few, but no more than I have always had. Not a problem with previous versions, so I assume something has changed since the advent of v 2017.
  11. Jim, thanks for that explanation. It goes a long way to know that the engineers are aware of a problem and are working on it.
  12. Hi Jim, to be clear, handling of resources also affects startup delay. I know it's difficult to separate these delays out, but based on the screen hints I am seeing, something on the order of 10-15 seconds to load the resources after activation verification, where the total startup process used to take 15 seconds. v2017. Have you been able to verify this extra processing time with the new resources handling? If not, could you lay this perception to rest? If yes, can you explain why NNA thinks it was advantageous to re-design the resources interface at such a cost?
  13. Hi Jim, with great respect, I see the activation delay and that is a very important thing to fix. But I am talking about issues that are specific to the time it takes for resources to populate, both at startup and when going to the attributes palette. Anything having to do with resources now involves a very noticeable delay. Do you not experience this delay when using v2017 (can't speak to v2018, because even though I have paid for upgrades, we have not installed 2018 due to fear of even greater productivity dings)? Just for example, I click on the attributes palette, click on the fill style button, click on hatches, click on the hatch dropdown list and wait for several seconds while that list populates - it takes so long at first I clicked several times because it didn't seem to be working. Finally get a hatch and apply it - the whole operation taking around 10-12 seconds where it used to take less than 2. PS: You have to test this immediately after startup, because once you have used the attributes palette this way the list has been loaded and persists, reducing the delay
  14. As of v2016, all the resources, crap or not, were loaded on my machine with an SSD in 15 seconds to complete the whole startup cycle. As of v2017, with the new look and handling of resources, time has ballooned for startup and lots of other operations - such as, just assigning a hatch to an object. It is really not acceptable that we pay for poorer performance with supposedly improved software. Can someone from NNA explain why this has happened, and if there is some benefit we should be getting from all these slowdowns?
  15. Christiaan, I like removing the wall lines and windows spanning stories, but thinking about a wireframe 3d view of the whole building gives me a queasy feeling! I would think that writing the code to eliminate hard lines between walls that butt each other (I assume hidden line view is the issue) could be done. If you "corner join" two colinear walls, you can already eliminate that vertical line, so more of the same? I think windows could be layer-aware in the same way stairs are - granted, that idea is a bit cumbersome, but being able to view the building layer-by-layer seems a reasonable tradeoff.