Jump to content

Tom Klaber

Member
  • Posts

    2,005
  • Joined

  • Last visited

Everything posted by Tom Klaber

  1. Artlantis 4.1 gives the option to use the Maxwell rendering engine. Is this a workable arrangement to get VW models rendered in Maxwell? Can you use any Maxwell texture with this arrangement? I have been craving for years a way to render my models using Maxwell, which in my opinion is the superior engine. This seems like a costly route. Has anybody tired this?
  2. I have. They have been good to me in the past. Because others in the office are having problems with other files, I thought it was a broader problem, but my crash rate is even higher than theirs. When I have a second I will see. I suspect it has something to do with the conversions from 2012 to 2013.
  3. Kizza, my install has not affected the performance of 2012. Because they run as separate programs, I do not think you need worry about 2013 infecting 2012 with its glitches. I would like to say that I am unlucky or that it is a local problem, but it is happening to other members of my office. It could be we are sharing a configuration that is causing the problem. We are all running 10.6.8 - we have not updated to Mountain Lion. I have found that even simply in 2D I get crashes for "no reason" - to say that they do not follow any action, but simply occur while navigating around a document or clicking back to a document. I have moved rendering back to 2012 for the time being.
  4. Good. They need one - that and a brand manager. Where do you see that job posting?
  5. You are right. It seems to be a lack of vision on where the software needs to go. All of the new features seem a little piecemeal, as if every programer is given a 300 day task of creating a new whatever button with no big picture goals. You can even see it in the VW branding which is terrible. They introduced an new ugly icon which has nothing to do with anything. Not that the gaseous balls had anything to do with anything, but they at least related to swishes on the box - which are weak in and of themselves. There seems to be nobody at the top steering the ship.
  6. Sorry, not a native Mac guy - I am running 10.6.8 I restarted. Issues are being experienced by others in the office. It is a 3D model that was converted from VW2012 to VW2013. I have moved the file back to 2012 and it has been OK. I have not crashed since I have been simply drafting.
  7. You are a wise man. I have learned my lesson. Now I wonder if it is too late to roll back to 2012.
  8. Other people in the office are experiencing it too. Seems especially fragile when rendering and trying to do anything else. This is beta BS. Not acceptable for a major release.
  9. I am crashing CONSTANTLY. Anytime I am rendering and try to do anything else, it crashes. Not acceptable.
  10. I am crashing at an ungodly rate. 2 an hour to once every 15 min. Really regretting the upgrade. I understand that this is a complicated program, but I feel as if it should be more stable.
  11. Yeah. It would work for some things but not all - and therefor does not work at all. Its great idea to have tags synced to viewports, but scary to think that your tags will simply disappear if you move the viewport, I could see that causing serious potential problems.
  12. How can I cut them without creating a second detail viewport? To explain the situation - if I want to show window details - I need to show the header and sill and maybe the center mullion at say 3". I wouldn't show the whole window but break down the detail into those three parts so they fit on a page. Though my detail callout on the main section would circle the whole window, this would be labeled as 1 detail, not 3. As far as I know, you can not do that with the detail viewport. If I am wrong - this is a whole new ball game.
  13. Hm. Its true that if you can not cut the detail, it becomes mostly useless. At least half of my details have to be cut to fit. This seems like a good first step that falls way short of being useful... maybe in 3 or 4 versions.
  14. That is good to know, unfortunately, drafting is more RAM intensive (I like to keep 12 files open at once) and renderings is more processer intensive. This has long been an issue and we must assume that VWs is frantically pouring all of its resources into fixing this flaw.
  15. Because VWs is a 32 bit program, it is not entirely clear that adding more RAM will do you any good.
  16. I am playing around with the new detail viewport tool and I do not see the point. I was very excited about this pre-launch but it does not seem to do what I want or anything particularly useful. I like that it auto generats a tag, but I thought the point of that was the tag would auto coordinate with the detail viewport. It does at first, but if you move the viewport to a new sheet layer then the tag disappears. If all I am getting is a tag, then it does not really accomplish anything. Anybody finding legitimate use for it?
  17. Thanks, I know. I phased my post poorly. My wonder is: is this function enough to warent the time needed to set it up and maintain it. I am going to test on the next project. Thanks for the template!
  18. It is a two edged sword. I find the walls to be more annoying. So rarely when I move a single wall do I want ALL walls associated with it to move too. I think this feature is an example of more being less. On occasion, in SD, I would want to freely play around with a layout and not have to rejoin all walls, but when I am fine tuning a wall I do not want it pushing and pulling everything in site.
  19. There seems to be a problem with the Set View command. The resulting view's camera position is off. You seem to be "standing" behind the spot you should be. The distance back seems to be proportional to the line of sight. Frustrating.
  20. My colleague, who now has logged more hours than me in VW13, says he is seeing noticeably faster rendering times.
  21. Its true, I get calls asking for Square Footages, and I always have to jump into the file and draw a polygon. If we had spaces feeding that info to a schedule, it could be save some frustrations.
  22. If that is it, then that is it. I was hoping they were more powerful than they first seemed. The senior associate here simply uses rectangles for that. I have been trying to get him to use spaces instead, but I have been unable to convince him why they are all that much better.
  23. Absolutely nothing as far as I can tell, but I am sure I am wrong since it has its own dedicated pallet. In practice, what are they used for? I have only used them once to create a table that showed square footage by room and floor. I have tried to use it for a room finish schedule, but it just does not work. Every space assumes you only have a N, E, S, and W wall. Feature walls, or rooms that are not square, can not be scheduled using this tool. I have this sneaking suspicion that there is a whole world I a missing out on. What do you use this tool for?
  24. You are right, there are a few new tools - some of which will make work much faster, better, but this is not what I would call a major or bench mark release. Small tweaks like adding tilt turn to the window tool are nice, but should not be included in New Features of the program. For me the biggest thing, and it is not on your list is the background rendering. That is the type of significant change that is going to seriously effect workflow. If hidden line being faster or the space tool being improved is being called a new feature of the release, you know you are in an off year. 2014 Give Me: 64Bits Overhauled Usable Stair Tool Live Sections Revit Object Import Door and Window Type and Variations 2D Hatches on 3D Objects Overhauled Worksheets Electrical Tools Maxwell Plugin
×
×
  • Create New...