Jump to content

BandA

Member
  • Posts

    79
  • Joined

  • Last visited

Reputation

0 Neutral

Personal Information

  • Occupation
    Architect
  • Homepage
    www.badgerandassociates.com
  • Location
    Manchester, VT
  1. I have created a site model recently, but for some reason, I can't get the cut and fill volumes to display anything but 0.000000 CU Yd. I have created several site models and have always been able to confirm these in the past. Any ideas??? Could the area of the site model be too big? 366224.041 sq ft Settings: 2D Display Proposed + Existing 2D Style 2D Contour 3D Display Proposed Only 3D Style 3D Contour Area Display Type Volume Display Type Cu Yd
  2. Thanks Andrew. I did send the file already, so hopefully it will help. For what it's worth, most rendering modes seems to have trouble to a certain extent, but the one that had the most problem was Hidden Line. This is especially the case when cutting Section Viewports.
  3. i was not aware of such tools. i will ask tech support
  4. i'll send the info in a sec. what if my sample file is large (~150 mg)? do you have a server i can upload to? i can't really attach that to a email.
  5. though, to keep adding to my rambling thoughts, i've also noticed that vw2008 takes up a LOT of memory in leopard. anyone else found the same?
  6. it appears that the only rendering mode i could find this in is 'hidden line'. this is a fairly crucial part of my work flow and i am dead in the water without hidden line viewports. has anyone had the same problems? has nna found these problems as well?
  7. I am on os 10.5 and vw2008 sp1 and i am finding that while rendering a relatively simple viewport in hidden line rendering (one which rendered in 12.5.2 and vw2008 on os 10.4.10 ok) the active memory usage shoots through the roof (up toward 2 gig) and then vw punts me out of the application saying 'insufficient memory to complete task' or something similar. i am also finding that the longer i use vw2008 sp1 during a given session, the amount of active memory usage inches up toward 2 gig which never happened in os 10.4.10. i am on a macbook pro, 2.33 c2d, 3g ram, osx 10.5 anyone else had similar experiences?
  8. katie? has anyone had any issues with section viewports?
  9. i am trying to update my section viewports in 2008 and i am getting really buggy results. Occassionally some items in the section viewport will disappear when i update. for instance, MOST of the building is there in a given section viewport and when i make visible a class that holds a lot of 3d balusters, it seems like a third of the building disappears when i update the viewport (random walls, windows, floors, roofs, etc, etc). this is not an issue of misused classes. i have checked a bunch of times. if anything, parts of the drawing disappear when i make a few more classes visible in the section viewport, without making any other classes invisible. i am on a macbook pro. osx 10.4.10. 3 gig ram, 2.33 c2d. anyone else had similar problems?
  10. BandA

    3d plants

    bump. anyone? i watched an old v11 or v12 video and they showed an area in the plant tool info window that allowed you to specify the 3d symbol used for the plant. has this gone away?
  11. BandA

    3d plants

    this might be a stupid question since i am new to landmark, but how does one go about getting the 3d part of the plant plug-in object to show? i really don't want to use image props. i don't like them very much. thanks
  12. i gather you've already tried this based on your response, but i tried using a default workspace and i got the same results. if i use a floating data bar, i can access the data with the tab key (and also the numbers above the keyboard, which is inconvenient in my case), but if i use the fixed data bar or the data bar on the tool bar, i cannot access the data with the tab key like we used to be able to. for reference, i am talking about accessing the data bar without using a tool (ie, in the middle of drawing a polygon or a wall). thanks katie
  13. i am using a custom workspace. i configured the mode buttons to be accessed by 1,2,3 and 4 above the keyboard. i work on a laptop so i have no numeric keypad (essentially). i can change my workspace, but they keyboard shortcuts i picked for each key were done so for a reason: they significantly speed up my workflow. i found that if i can get around the numeric entry problem by keeping the data on the fixed bar, but then i noticed another change: you cannot press tab to access the data bar when a tool is neither selected or activated (ie, starting to draw a wall). was this change done purposefully? i liked to use that feature in 12.5 because i could navigate to a certain part of the drawing that i wanted to use as a reference point (say, for its x coordinate), tab to the x cell, and press enter to lock that coordinate in. now i can start a wall at that x coordinate for example. i know i can use floating edges, but i preferred the old method better because it was a little more foolproof. has this feature indeed gone away? i think the floating data bar is a good idea, but it would be great if the only way to access the values in it were to press tab (like the way the old version of vw worked).
  14. I have been trying to configure the new floating data bar to work like the old system, but I cannot do it. here's my problem: i use the number keys to change the mode bar (or at least what was previously called the mode bar) and the 'do not use numeric keypad entry for instant data bar activation' option does not seem to work, causing me to enter '1' or '2' in the floating data bar when i intend just switch modes. for example, i start drawing a wall and i want to change the reference point for it's insertion so i press the number one a few times and it enters this into the floating data bar. the option to not use instant numeric activation of the floating data bar doesn't seem to work for me. has anyone else experienced this problem?
  15. it seems like the camera view can be imported to a certain extent, but not the lights. this is a house i am doing. when i exported a dxf and tried to pull that into the program, the program didn't seem to like it very much and wouldn't open it. the .3ds file is close so that was why i was trying to work with it.
×
×
  • Create New...