TDWrks

OK, got it, thanks for the info. @Rob BooksI hear your, though that doesn't describe the way the RGB sliders seem to revert to a default "near color" after editing. Is this part working as intended? "basically, it is like taking a filter and placing it over an image, you are going to have bleed from the image come through and affect the color of the filter. Hope that makes sense. " That's fine and well, and being a color guy I wouldn't have any problem tweaking the filter to the desired output, but need the tools to work properly in order to do so. @Alan WoodwellThanks for that... yes that would be the "right way." This is a simple example that would easy to grab in photoshop with a magic wand. However, this is a fairly "down and dirty" workflow that I've used in the past to tint or shade an existing stone or wood texture to get to a desired hue/value. easier and quicker than an export, photoshop mod, etc. especially since I'm not doing photorealistic renderings here.

Hi Rob, Issue is in edit texture pane from RB. Render mode doesn't matter since its texture itself not editing properly, tho I've tested with open gl, and several RW qualities. No effects being used (referring to artistic RW mode or something else?). Attached are screen shots: in the first you can see me attempting to change color filter of a white drop siding to RGB (143, 136, 119). 2nd screen shot shows just moments after the attempted change and the RGB values are now (133, 133, 133). If i directly change the RGB values and accept changes, they revert back to 133, 133, 133.

Having issues with color shader within texture edit pane: shader > color > image ... select edit to open Edit Image Color pane: Filter Color > Use Chosen Color... when editing (regardless of method i.e. color wheel, or pantone, or "crayon" etc) colors won't "stick." Oddly gross color changes (from orange to blue) work, though if fine tuning (bluish gray to greenish gray) the color filter is ignored and reverts to previous color. Other quirky behavior within these edit panes as well. Happens regardless of render mode. Is there a known bug or am I doing something wrong? I don't expect photorealistic application of a Benjamin Moore color for example, though as a color consultant its been awkward for me to show things to clients that are so obviously out of whack. Any help greatly appreciated! Cheers, m

Wondering if this can be done? I've tried messing with class overrides and surface hatch edit within texture, but can't seem to get results. Can set sketch on items within annotation (or leave default VP sketch), but not those generated from design layers. Let me start with what I'm trying to do: Frequently use custom sketch settings for elev, plans, perspectives on SLVP (for prelim design). When sketch is applied to hatches problems often occur. Typical example: overshoot, wobble, etc. that look great on main elements of a building elevation will be applied to a surface hatch and look terrible. Windows are a prime example: I use a fine "crosshatch" surface hatch associated with my glass texture to get windows to read "dark" in hidden line render, but the overshoot will obscure muntins, run well past sashes and generally look like a mess. Any advice appreciated, thanks,

Thanks Mike! Yes, understood. Old habits die hard... all the acad drafters I know (many) may use linewt by layer, but individual layers are represented by a single color. That's why I'm exploring class/layer mapping as a tool. Robert is a great source! I miss his frequency on these forums... BTW I've been around on these boards since the 90's (just under different handles).

Thanks Mike! Yes, understood. Old habits die hard... all the acad drafters I know (many) may use linewt by layer, but individual layers are represented by a single color. That's why I'm exploring class/layer mapping as a tool. Robert is a great source! I miss his frequency on these forums... BTW I've been around on these boards since the 90's (just under different handles).

Thanks Mike! Yes, understood. Old habits die hard... all the acad drafters I know (many) may use linewt by layer, but individual layers are represented by a single color. That's why I'm exploring class/layer mapping as a tool. Robert is a great source! I miss his frequency on these forums... BTW I've been around on these boards since the 90's (just under different handles).

Thanks Tim, I'll review those threads... I often draw linewt. by class anyway tho there are always overrides-- my drafters say fine as long as those items are in 0 class (acad layer). Haven't even attempted that, if its possible. There's no way I'm going to start drawing in cyan and yellow Which is why I'm going to try and set up a series of scripts to automate a pre-export sequence. pio's are a piece I'm still baffled by.

I didn't know abt the redefine in the nav palette either... thanks! by happenstance, I've got two separate files that are resetting my saved views at random-- classes, layers, etc ok, just the "view" and render setting. Not sure if this is a sign of a corrupt file, but I've worked around by creating new saved view with same name, but it has happened a couple of times now. Feeling like I need to copy objects into a clean file, but I'm hesitant to do so since I've modified from my standard template quite a bit and don't want to create more work. Any insight would be appreciated!

No others with "good experience?" I've got ACAD on my machine via parallels so I can check translation easily enough. Really looking for first hand advice regarding workflow. My acad drafters prefer (insist) on color/lineweight by layer (read vw class). I've played around with setting up a script to run just before export that will custom select/custom modify all objects by linewt. and convert to std acad colors. Issues: --it seems that these tools (even though they say search within group, pio, symbol etc) won't convert items within "containers" unless exploded first, which causes a nightmare of line segments in acad. --PIO's, e.g. a window, has multiple classes within and multiple linewts (by object in my case, but could switch to by class). I personally put all of this within a std door/wnd class by one color for organizational purposes. of course this scenario is completely counter-intuitive to my acad peeps... and generally ridiculed-- they with black screen and no line thkness -- what about linewt to color in dwg export dialog box? can ACAD easily select by color and dump into acad layers? If i keep my number of linewts down, its seems this might be the solution. how would hatches, groups, pios, symbols be effected? Linewt by color is just one of many, many hurdles to cross. In the past I have never had any issues working with consultants on acad, tho sometimes some grumbling about layer org. (hey, I do the same grumbling when I import a survey). but honestly, while I'm anal about my drawing aesthetics, I'm not picky about the way the struct or mech engineers' work looks. Now I'm looking to create in-house drafting standards (linewt, text, materials graphics, det bubbles, callouts, titleblocks etc) as well as logical workflow (layer/class/viewport/x-ref organization) that work across both cad platforms and it seems nearly impossible. One other item: what about effective use of the layer/class mapping tool? Or customizing the auto classing feature. I wish I could easily add a prefix (like "A-") to all import or exports. that would help. I have spent lots of time reassigning names to surveys for instance that could have had a simple "survey-" prefix so that all classes nest within. Aarrgh. Any, and I mean any suggestions greatly appreciated!

Just started working in an office with both ACAD engineering and VW design stations and I'm struggling a bit with interfacing. I'm being tasked to help set up new office standards. For now I'm concentrating on one-way communication (no back and forth, tho that would be nice). Our ACAD drafters are willing to revamp they way they organize there workflow, but as is typical there are long term habits, CAD conventions, opinions, etc. Im guilty too: long time minCad/VW user with my own workflow. If anybody has good experience with this, I'm all ears Some specifics I'm trying to tackle: --line wt. by color vs object --discrepancies in intent of class/layer workflow --xrefs --vw layers --3d data --symbols/PIO/groups to blocks (and how they interact with acad layers) Thanks,

To clarify-- this is an older license that had not been upgraded: VW 2008. May just park the seat, tho has value to somebody looking to buy new.

Have an older version of VWA+RW for sale that qualifies for upgrade pricing--$800 cheaper than buying new. Need to transfer license on this unused seat prior to upgrading to VSS in December. Feel free to message me, thanks, M.

Andrew, still interested? I would like to upgrade and purchase a VSS, but rules require me to upgrade all licenses, therefore I need to lose the one not in use. Like I said, its an older VWA+RW though qualifies you for upgrade pricing and cheaper than buying new. thanks,

I have and extra seat of VWA+RW (older version but eleigible for upgrade pricing). Let me know. Thanks,

Bummer, was hoping 2016 would finally address this as 3d workflow has become more and more important, yet 2d con docs still represent the bulk of the end product in the arch industry. I've been requesting this since about VW 8 (that's 8, not 2008) and have seen similar posts many times over the years. Two separate pieces for me: 1) the ability to read depth in 2d elevations and sections by varied linewts (lighter as they recede) 2) the ability to "profile" and indicate elements with heavier line at the perimeter of a building form. The process of "doctoring" to create linewt variations within annotation layers is a waste of time and unacceptable (especially with live sections etc). might as well go back to the old "convert to lines" workflow and completely dissociate the 3d from the 2d. I agree with previous posts suggesting B/W and grayscale could be solutions-- if clean printable grayscale textures could be controlled (like a class override, or hybrid texture) and used to describe materials in 2d while simultaneously providing colored versions in 3d views I could do away with hatches altogether. Of course I would then want these textures to lighten as they recede in the back ground too. Many of us old guys insist that its not just an artistic convention, but a way for our drawings to "read" properly and lends additional clarity. SU uses fog to create the desired affect and while not a change in linewt or profiling, can effectively describe depth. I'm ok with that. I'm not ok with elevations that are all of mono line wt (even tho some of my younger colleagues wonder what it matters). Until the time 3d drawings can be submitted for permitting, architects will continue to need 2d plans, elevations, & sections to adequately describe proposed building projects and as clearly as possible including differentiating elements that occur in the foreground vs. background.

Well, I'd at least try it, but I was given a licensed copy of ACAD for Mac and it requires better spec'd machine than I have. Of the computers I have, the most current is a 4,1 macbook (2.2 intel duo) that I actually bought for my kids before the economy really tanked. Any further word about sticking with VWA+RW '08 for now on a new(er) mac? oops! I was logged in under a different profile. Sorry to confuse. Cheers, Mark

Well, I'd at least try it, but I was given a licensed copy of ACAD for Mac and it requires better spec'd machine than I have. Of the computers I have, the most current is a 4,1 macbook (2.2 intel duo) that I actually bought for my kids before the economy really tanked. Any further word about sticking with VWA+RW '08 for now on a new(er) mac?

Hi all, Long time VW user here looking to upgrade computer but NOT VW. NVW tech specs stop at 2009. Does somebody have experience with VWA+RW 2008 on a newer Mac computer? I'm guessing multiple processors won't buy me anything, but graphics cards, ram, etc. Not even sure about intel processors (yeah I know, I'm a dino, but the economy hasn't allowed much the last few years). I'm pretty happy, not thrilled, but happy with 08 performance, features and stability. I'd like to avoid the headaches people have had with 2011 and put my cash into a new machine. TIA, Cheers, mmm