Jump to content

gScott

Member
  • Posts

    276
  • Joined

  • Last visited

Everything posted by gScott

  1. christiaan building regs are fine, there are many ways of achieving compliance balancing regulations, material requirements, costs + not least, aesthetic design; it's called architecture i am not attacking you, it is, in my opinion, just one fugly railing, particularly the totally random relationship of the verticals to the treads but i suppose, on reflection, we shouldn't let software start having aesthetic parameters, click here for: gorgeous, banal, fugly. el cheapo, just affordable, insane
  2. unfortunately, you can't duplicate section lines, but you can duplicate sections... 1 keep a small viewport plan on the sections sheet to use as the section line key plan, which saves having to dive back to the design layer to adjust section lines 2 set up a section + tweak all the properties, add the key plan viewport to its 'section line instances' 3 duplicate the section viewport on the same sheet, change its name in data tab of the object info palette, add the key plan viewport to its 'section line instances' 4 edit the annotations of the key plan, the new section line will be lying on top of the old section line, identify it by its name from step 3 above, move it/reshape it, exit annotations 5 update new section, rinse + repeat... this works fine in VW12.5.x but should work in a similar manner on new versions...
  3. if it can, it shouldn't be allowed to, makes my eyes hurt sorry
  4. bcd's suggestion to make a temporary duplicate of the DTM, then 'convert to group' or 'convert to mesh' + then 'fit walls to roof' is how i do it. fast + dirty but you have to remember not to copy walls that you have already sent to the DTM, as the undersides will be out of whack, particularly if you rotate or stretch them, all looks fine in plan, but section VPs reveal the horrible truth...
  5. petri she might ask the questions in a different way and might elicit different answers from people normally weary/wary of the poisoned kool-aid well
  6. david it generally makes sense for the "use at creation" setting to be ON so that viewports can be altered as above, and for greater speed of drawing if you are rigorous in your use of classes. e.g. in my case: structure-existing = thick black pen + grey hatch structure-brick = thick black pen + red hatch structure-conc = thick black pen + green hatch structure-demolished = medium dashed red pen + no fill etc etc the weirdness here is that windoor has graphic styles of its own that can get confused with the normal class styles. the only class that i set OFF for "use at creation" is windoor's 2D objects/swing class so that windoor can set the swing to be different to the door + jambs
  7. if the viewport class over-ride grey colours are not working it is most likely that those objects are not drawn using the class style for pen colour. alternatively if you are using the windoor tool for your doors + windows check that the default class settings for the windoor classes are set to "use at creation" for the graphic attributes. i tried a render like yours + found that my default windoor classes weren't set to "use at creation" + it rendered the same as yours. on re-setting the classes you also have to regenerate each windoor element to get the new settings to take. e.g. click on each windoor element + toggle, say, "opaque glass" on + off . smarter people than me will have a better way to do this, but it works for me, and your model doesn't look too big... this may also apply to the VW window tool, but it rendered fine in my test so i am guessing it's "windoor" hth
  8. petri again you are behaving like a smart-arsed little kid with petulant retorts to people who know your online habits and yet take the time to try help you... grow up
  9. you could draw 3d poly's in elevation at the correct height + angle etc, and float them just "inside" the walls, but the way you have described is actually better IMHO
  10. i suppose there's a really good reason for this? not...
  11. @ray so how does NNA test new graphics drivers immediately after they come out? any problem: update your graphics drivers; it's getting a bit thin...
  12. and added to all of the above, "stacked layers" must be OFF...
  13. @ray there is no reason why VW should be producing PDF's that are readable by only the latest version of acrobat, there is nothing "clever" in a VW PDF file requiring only the latest versions. it's like the usual nonsense about constantly updating the graphics drivers, while insisting on staying with an obsolete quicktime version... @monkey this all depends on the particular sheet being printed. sometimes 'export' is really fast + small, sometimes many times larger than a 'print' if size is an issue you should try both ways. 'export' is nice because it doesn't mess with the 'paper size' + title blocks don't wander, but it also screws up some non-standard fonts, in my case rotis gets all jaggy, arial is fine...
  14. orso, the "custom stair" does show upper + lower floor views, which is very useful for calculating landings, headroom etc, but doesn't work properly for most other things. the new stair has lots of new options, but doesn't show upper + lower floor views... how can this be clever or better? escher aside, what staircase leaves one floor + doesn't arrive at another floor? what stair doesn't need to to be shown in plan on upper + lower floors? it's not clever or a matter of choice to have two stair tools that don't do the job properly, and suggesting that a CAD system need not properly cater to a building of more than 2 storeys is ridiculous. this is a great disappointment + this alone will probably stop me upgrading
  15. it's cripple-ware.... hardly a "design-only" function there is no reason other than petty marketing to disallow pdf importing advertising disabilities like this will only drive the lower end of your market away to a more amenable competitor, not what you need in a competitive economy, or am i mis- understanding modern business again
  16. dbg, our hp has a tab in the windows xp printing prefs dialog called "services" with a "troubleshooting" button, with a choice "send job as a bitmap (process in computer). this works for us; without it selected we get random memory complaints from the printer... vw12.5 + win xp
  17. in artlantis there is a fairly well hidden set of options camera -> "post process" where you can create some nice sketchy effects, but only for rendered bitmaps. i.e. you can't get the VERY nice sketched line drawings, that you can get in VW. and if those are only available through RW, then that alone makes RW worth it for me. clients are AMAZED how fast i get from rough sketch plans to dimensioned general arrangement drawings
  18. islandmon, sounds like artlantis then? just finished a presentation on friday as you described, sent across the model for lighting and materials, + background rendered 10 images while i finished off the sheet layers in VW. images were done before i had finished fiddling with annotations + dimensions... i don't know how much longer i'll stick with RW...
  19. peter, what version are you using? this has been stuffed since 12.5.... the usual response is check your permissions, which doesn't fix anything...
  20. have you tried fiddling the default settings in the script editor? you can access almost all classes in either the parameters or strings <+ sometimes properties> sections then copy those fiddled PIO's to the other pc... beats having to fiddle around with the layermap nonsense. keep a text file handy with your own class names to cut + paste into the script editor + keep backups handy...
  21. pat, it can't be that hard; microstation has been able to do exactly that for 15 years! they only have one "layer" so the reference can't go anywhere else...
  22. tguy, there's a difference between being "calling out" and "pulling a unilateral" having grown up in a state that did a lot of the latter, i cherish getting to see + hear the other side, no matter how distasteful corporate drones punting the party line are every bit as painful as a snotty one liner from petri...
  23. benson, in shaun's example image the grey road belongs to the background image, there is no modelled "floor" visible. the shadows that are visible are being cast onto the "shadow catcher", an invisible floor in this case, and only the shadows become visible. this allows for the model to cast shadows onto a background without having to fake them in in photoshop afterwards, or to fake out a floor that they were being cast onto...
×
×
  • Create New...