Mark McCay-Moran

6. Export as HDRI with a low number of pixels, let?s say 128x128 and give the file a name. I had no idea we could make our own HDRIs. What export option is being chosen here? An image file? what format to use as an .hdr? thanks, mmm

I'll be darned... Peter's got it. Usually the model would consist of many layers in Stacked Layers mode (and in 11.5 as a Layer Link). Because the kitchen drawing was done on one layer I never thought to use Stacked Layers and it wouldn't render. Definitly a bug. Dave, I'm not sure I understand your comment. I would never have Active Only option on when viewing a model in Stacked Layers. Of course I just gave the exception with my Kitchen file (and also when viewing a layer link in the old method). I had tried the responsivness pref in my test file and it didn't seem to make a difference, I should go back and try with the Stacked Layers option on. Thanks, mmm

I really don't use RW to its full capability, but one thing I find useful is showing clients basic schematic building models akin to the old cardboard study models that we used to do. Recently I've run into problems with the model staying rendered (not reverting to wireframe) in Open GL when using the fly-over or walk-thru tools. First, is this graphics card dependent or memory dependent? Yes, my models seem to be getting more sophisticated, but in the past fairly complicated layer links with textures and 3D symbols would stay rendered. Seems like problems got worse from 11.5 to 12. Also I?m not running the speediest or best graphics cards in my computers but have a number of G4s with 1.5 to 2 gigs of ram and OK g-cards. What got me thinking was a simple kitchen that I did recently with cabinet objects (about 15 of them), 2d/3d symbols, walls and a couple of windows. Not the whole house but a partial plan, mind you, and would revert to wireframe with fly-over. I think file size is an issue. I?m up to a 70 MB file when opening a new doc using my standard template (complete with preset design and sht layers, VPs, common symbols, and textures etc.) BLOAT! The Kitchen file went down to 54MB after purging unused items, but still won?t stay rendered. Interestingly I?ve got a house file at 115MB that stays rendered. Methinks the type of objects (or texture) may be culprit. So I set up a test file: blank file (not template) which starts at 40KB and insert 100 simple base cabinets with wood texture. Continue duplicating and doesn?t revert to wireframe until I?m at 1200 cabinets! (with a noticeable slow down around 800) File is 20MB. I?m not sure what I?ve learned. 1200 textured cabinets is a lot more than the 15 in my kitchen file, but file size is less than half. Any thoughts would be appreciated. cheers, mmm

Darn.

Is it possible to get them to map properly on stile and rail portions of panel doors? Any tips appreciated. mmm

Agreed. Its been a long standing wish of mine.

The advantage to Saved Views is the preset class and layer parameters. While viewports have a lot of class and layer flexibility, the Sheet Layers itself doesn't remember default "views" (ie- moving from a Design Layer in a "structural" Class in active only mode, to a Sheet layer with nothing in that Class...huh? where are my images?) For this reason, my office protocall now says all VPs and items/object directly on a Sheet Layer are given the none class (which is usually on). cheers, mmm

Huh? There were plenty of icons in VW/MC in '92! Sorry, couldn't resist. cheers, mmm

I like the potential for this tool and asked the same question with no response some time ago. I've since stopped using it because there were numerous times that I had forgotten to manually updated and the dates didn't coordinate with revisions etc.

I would like to think that Andrew (and Sean for that matter) would ask Robert A. if true live sections would be useful to an architect. I think I know the answer. I put a lot of effort into drafting in 3d and personally, I'd like to reap the benefits. Currently I still spend an enormous amount of time doing 2d electronic drafting to make sections and elevations "right." cheers, mmm

Hi mw, Yes, all the benefits and a few glitches. Maybe I'm too picky about the graphic quality of my drawings, but... a known bug disregards "Part line style" in the window and door PIOs forcing the user to select one window/door at a time and reset line weights. Also the Jamb wt controls the sill. In my case, it means individually selecting around 300 windows to gracefully move everything to 12.5. Having said that, the speed improvement is great and the app is less buggy than 12.0.0. cheers, mmm

Agreed, and I really like the improvements and refinement of the program (in addition to the difficult task of porting to intel based machines). Good Job NNA! I'm using 12.5 on two new jobs, but the dozen or so that were started in 12.0 will need to stay there for now cheers, mmm

Omitting window PIOs in VWA thread. This one sent me back to 12.0.1.

Hi Henry, Upon reflection, my methods may be different than others, but typically I use a combination of Keynotes (more often) and callouts with text. Looking at an entire 24x36 drwg I can pick out text and modify without needing to read. Why? cause they're usually assembly notes (wall floor etc) or stair specs, or a few other predefined note types that don't show up as keynotes, OR they are already keynotes (that have numbers only). Flexibility to work however suits your system seems key. Hopefully VW can provide both. BTW I agree about screen size, all stations in my office have multiple monitors ranging in size from 19 to 30. I use a 23" with my 15" PB. cheers, mmm

Was it autosaved to a backup file? I think this is a must. I also periodically Save As with a new date giving me archive files back to first set-up. Good luck with the file.

I can't seem to duplicate Gideon's problem on my machines. My workaround for the sill linewt is to create windows with "Timber Sill" with a small enough Sill and Stool that they don't show up in Plan View (can control wt with Part Line Style). Great for new drawings, but without global control over windows and doors, revamping each wnd/dr on even modestly complex projects is way too much work. Looks like I'm back to 12.0.1 for a while Too bad cause so many thing work better: general speeds and render times, assoc dims in VPs, chain dims, nav pallette, dup array, wnd/dr options, among other things that I've only started to explore. Lets hope for a speedy maintenance release! cheers, mmm p.s. when transitioning from 11.5 to 12 I left my old jobs in 11 and ran both versions side by side. Can't do that with 12 and 12.5 due to no re-naming within major upgrades.

This is the first thing that went back into my custom workspace. The "double-tap v" (for zoom out 2x) is an old habit that I'll never break.

I'm on the opposite side of the fence. I like being able to edit text of a callout in a dialog box without zooming in close. I find the less often I zoom, the more efficient the drafting. I wish text objects could be edited with dialog boxes as well. In the old days one had to zoom in, select the text tool, modify text, zoom out, select pointer. Now one can double click callout, modify text, exit. Just another opinion. mmm

Arrgh! spoke too soon. Speinding a little more time with the upgrade, I can confirm that all PIO windows have the "sill" controlled by the Jamb line style. Frustrating that something that was broken in 12.0.0 and fixed in 12.0.1 is now broken in 12.5.0. Are you asking for a seperate 2D line style for the threshold? Should 2D mullions take on this line style or should they too have their own line styles? What (mostly*) worked in 12.0.1 is fine, ie, Jamb line style controlled wt from wall (or trim) to sash and is independent of "sill" weight. Note: "sill" as used here is not Stool or Sill in Parts dialog but rather the edge of window frame (in absence of Sill Part). Clear? Mullion should have same wt as Jamb line style. Don't necessarily need additional control over this "sill" as long as this edge (and the edge of sash in distance) is a light line, as it was in prior PIO. *there was an issue where the PIO window mullion would not pick up the Jamb line Style. mmm

Some additional info: Class line wt (use at creation) now overrides "use part line styles." This is true of new VW 12.5 docs as well. If you want to have doors in a door class (to give PIO color, fill, etc at creation) then you have to pick a line wt. that will always override the "part line styles." The work around (read: short term bug fix) is to select PIO give it a zero line wt (which only controls the line at "shim space") then set to another value. A lot of the door elements that should have worked in 12.0.1 now *do* work! Thanks! Frustrating that these little things get in the way of feeling joy for all the other fixes. Another "new" issue: new sidelite control allows for depth of mull...great. But the Jamb Part Line Style seems to control the "sill" wt. a lot like the Window PIO in 12.0.0 before it was fixed in 12.0.1. (By sill I actually mean the line viewed in plan at the edge of the mullion "frame"--not the Wall Line or Threshold). cheers, mmm

Another example of where a global edit (or at least multiple edit) of doors and windows would be helpful. cheers, mmm

Mike, Is this why I have trouble with the 2nd and 3rd modes when adding graphics to a VP or SVP ? (typically when I want to use them!) Thanks, mmm

I'll bump this just once. I'm stalling on retyping a bunch of callouts, so if anybody has advice on this, its reatly appreciated. cheers, mmm

This should be the case. I have so many different windows in a custom residence that placing as symbols would still force many actions to replace glazing line weight, for instance, that could be done globally. Unfortunately, one is not even able to SELECT all the windows globally due to there necessary interaction with walls (a serious peeve of mine from way, way back). I'm hoping window/door editing and insertion are addressed in the near future. cheers, mmm

If Carbon does the job and isn't leaving VW "behind" as the OS continues to grow and evolve, then Carbon it is. If NNA is postponing the inevitable, or removing options for the app to interface with the system or other apps, I'd like to see a transition to Cocoa. I'm not tech saavy enough to give anything other than an end users opinion. Certainly VW following the move to intel based machines is a priority for me, as my office considers new computer purchases. I don't know if or how its related, but I'd like to see dual and "quad" processors addressed, and soon. Its been quite some time since apples pro machines (except some lowest tier models) have come stock with multiple processors. Render times (and file sizes) have gotten out of hand. cheers, mmm