Jump to content

P Retondo

  • Posts

  • Joined

  • Last visited

Everything posted by P Retondo

  1. Robert and wezel, thanks - got it! One final question. Now that I can see my doors in order, I find that doors which are incorporated into a symbol have tags on the drawing, but they don't show up in the schedule. The criteria argument for the database is: =DATABASE(((R IN ['Door']) & (Door.OnSched=TRUE))) How do I edit this to include door objects with ID tags that are part of a symbol in a wall? My workaround is to copy the door PIO instance to another layer.
  2. My window schedule has automatically sorted the windows based on ID label number. My door schedule seems to be randomly sorted - is there any way to cause it to sort on the ID label?
  3. In the Window PIO there is a field for "Sash operation" that is set to "Custom" when we have a multiple-unit window. That designation is particularly unhelpful when we generate a window schedule. It would be better if it could be set, for example, to "Casement/Casement". I think it might be best to have a separate field that could be edited, and that would be the source of the data for the schedule (I do that now as a workaround, and use a user data field). This field would be automatically filled with the "Operation" text string, but could be edited without changing the actual window geometry. I would distinguish this field from the one that sets the window geometry by calling the latter "Type."
  4. I find that one of the biggest drawbacks to the new Viewport capability is that filesize, if the Viewport image is cached, becomes incredibly large. That in itself would not be an issue if it weren't for the fact that intermediate "saves" require writing the whole file. I have a very moderate project that has a 350MB filesize and takes over a minute to save on a relatively fast computer. With a database structure, saves can easily be made incremental. Only objects that are changed are saved. In fact, for many SQL-based accounting programs saves are almost instantaneous and automatic. I just think the reasons to go to a database file management system are inexorably compelling. I'm not sure how ArchiCAD is structured (anyone know?), but in a typical database system the file or files are accessed by the "master" process, and can have inscrutable and irrelevant actual filenames. The master process catalogs all objects, and handles save and other management requests from workstations on an object-by-object basis (in the case of accounting and other typical database systems, these objects are records).
  5. Say what you will, I find that Petri is both entertaining and informative. That he manages to insult almost everyone in the process - well, it's the other side of the coin. I would welcome, though, a return to substance on his part. When he's correct in his analysis, the humor is devastatingly funny. On the other hand, hurling an insult in the process of missing the mark factually or intellectually falls a bit flat on a tech support board.
  6. Here's the primer on converting 3d views to elevation drawings: Create elevations by Peter Cipes
  7. We were discussing this issue recently in the context of what ArchiCAD does. I talked to a friend of my who is an SQL programmer, and he verified that the file structure of such a database is actually hidden behind the scenes, and that the user typically interacts with software running on the server to coordinate changes to records so that users don't write over each other. So while this is possible to do, it requires another software level and changes the nature of the file format and structure. I don't think VW will make it to the future in the big leagues if they don't bite the bullet and work towards this capability.
  8. Given the uncertainty about exactly what brand of window and door we will end up with, I always dimension doors and windows to centerline, and provide a schedule that gives the (at least hoped-for) unit dimensions. Here in the US residential / small commercial market, the contractor always has a "better idea" (i.e., more convenient, more familiar, more profitable for the contractor - spoken as a former contractor). However, even if we had certainty about unit sizes, I would still dimension to the center of the unit and refer the contractor to the window / door schedules for the actual frame sizes. Contractors commonly want to control their own shim space tolerances.
  9. Matthew, class setting is beside the point. When the program renders the degree of darkening differently between one transparent 3d surface and multiple surfaces, this problem will arise because the number of transparent surfaces in different PIO instances varies.
  10. I use styles to define the basic geometry of the wall type, and classes to distinguish between new and existing. Duplicate an existing style in the resources browser to create something new, and edit the components.
  11. I'd like the resource browser to work more like a normal file browser - i.e., beside having the long-ago requested "Back" and "Up one level" buttons, and collapsible folders (including the main file folder), I'd like to be able to drag a resource from one folder to another, and to copy and paste using and . As it is now, I have to make my destination file active in the VW draw window, go into the resource file's folder, "import" the desired resource, then go back to my destination file's resource browser, find the imported resource, and move it to the folder I want it to be in. The navigation overhead could be considerably streamlined! And is this a good time to repeat again what a pain it is that every time I switch from one .mcd file to another, find a resource and click on it, the resource browser jumps back to the top of the list instead of highlighting the selected file?
  12. What is the advantage of a hybrid group? As opposed to a symbol.
  13. Check your Task Manager, and you will see that except for RenderWorks rendering VW uses only about 25% of the processor (if you have a quad core or quad emulation). 64 bit technology has a 64 channel bus, so you have the potential for greater computing speed. But it's up to programmers to find ways of using that potential. I don't think that "64 bit precision" is going to have the kind of traction that "32 bit precision" had a few years back, so the question is, can they find a way of using the greater bandwidth? I suspect they are on top of it, but I don't know enough to know what or how.
  14. Actually, the best thing about the suggestion is enabling all the processors to work at once. 64 bit opens twice as many data channels for each calculation, so theoretically it should perform faster. I believe there are ways of using that potential for things other than increased precision. But a lot of code has to be written before that could happen, so in the short term I'm not sure we're going to see any tangible results from 64 bit.
  15. Pete, I haven't run into that problem, and it sounds like something is wacky. With the new window settings you can assign a class to each of the parts. I'd try that, and give each a texture. Window Settings -> View -> Special Classes. Or it could be that you need to give the window a fill - although a window without a fill usually causes OpenGL to render it as a wireframe. Be forewarned that WinDoor uses a single 3d poly for glazing, and VW has multiple surfaces, so darkening with a smoked glass, etc., will be different.
  16. I'd like to see the "Update all Viewports" command fixed. Mine fails every time: "aborted due to lack of memory." The command should sequentially go through all viewports, update each one and FREE ALL MEMORY associated with the update before moving on to the next viewport. I can update my viewports one at a time, but doing so is quite time consuming. I'd like to issue a command and walk away to do something else, and come back an hour later to have everything completed.
  17. I'd like to be able to toggle the display of wall cavities while working in viewport annotation space.
  18. Users have reported both these things in the past as problems. The sill thing in particular is a problem, since it shows up in Section Viewports as a garbled set of lines.
  19. Donald, if I do a T join (uncapped mode) and remove the wall that butts into the other wall, there is a gap in the wall line where the joint existed that can only be removed using the "Remove Wall Breaks" tool. You must be doing something differently. If you do a T join in capped mode, then attempt to do a cavity join in uncapped mode, you will observe something like the effect you describe. Try the different operations, and remove the "butting" wall to see what effect you've had on the crossing wall.
  20. D, I have the same basic software as you, and haven't experienced workspace corruption in a long time. A couple of things to look at: version of Quicktime (workspaces are a .qtr file)and custom or 3rd party tools you have added.
  21. WinDoor doors have a single 3d poly representing glass. VW window PIOs have two 3d polys. VW doors with leaf type "glass" have four 3d polys, two of which are superimposed. VW doors with leaf type "panel" where the interior and exterior panels are assigned to a glazing class have two extrusions (verified by exploding objects and checking the assigned classes).
  22. Katie, he's referring to that red loop in the drawing below. The red bridge line and the green rectangle both belong to the same class, shown in a viewport where the red class color is set to override with green. As you can see, the override doesn't "take" with the bridge line object. Christiaan, I suspect this may have to do with the fact that the bridge line works with a white line that covers the line that "bridges." This white line must remain white for the tool to work, so it might be complicated to implement class override with this object. Or it might just be a bug.
  23. Windows, and the different types of doors handle glazing differently in VW. One of my wishes is to have all these things standardized! Some objects have a pair of planes for glazing, some have a single plane. Some objects set the glazing opacity via class, some via a dropdown list. To get things to be consistent, if you see a dropdown list choose "by class." Set the class name by hand - you have to enter it exactly (pretend you are a programmer). Then you can use class attributes to control how glazing looks. You still won't be able to solve the problem of some glazing being a double layer. Play with it and you can get acceptable, but by no means perfect results.
  24. Arlene, as Islandmon suggests you might have set class overrides inadvertently, or, alternatively, your viewport may have been given different lineweight and arrowhead scale factors. Check under "Advanced Properties" via the OIP and look at the various scales. These attributes can be transferred from viewport to viewport using the eydropper tool.
  25. Sorry, typo. How difficult it is to move text depends on the dimension standard. Some, for some reason, are more tame than others. Thanks for the tip on using to constrain. But, frankly, with the current implementation this should not be necessary. To move the dimension lines, one clicks on the lines to get the resize cursor. To move the text, one clicks on the text. These are handled differently, and unless we are able to move the text relative to the dimension lines in both directions, movement should be automatically constrained without using the shift key.
  • Create New...