MarkMc

Thanks.

@Chopsaw Hey does the attached PDF do what you want. Did this in Bluebeam-created text box, edit action, paste link string, add to my tool chest. Click anywhere to add the link . NOTE the links only work once you download and open in PDF program, they don't work when opening it on the Chief site in browser. Bluebeam has a trial version that last I knew (a while ago so could changed) is fully functional for 30 days. If not and you get me the pdf and info I can add these for you. Pages from grandview.pdf

The Y origin of the symbol needs to be changed. It may be set wrong, or it may be that it is meant to be installed on the floor since it has feet and is not a built in object. In any case you will come across this occasionally. Place the symbol on the floor. Open the symbol, check the depth of the bounding box, copy. Paste into the Y origin, then adjust since the depth includes the handle so would recess too far. I just took a quick guess at correct depth. Generally you want the Y origin set 3/4" back from the face that you want to be flush. Once done add to your user library so you can select it for the cabinet. Then go to the help or reference manual and read up on symbols, origins and stretch planes. Note that a lot of us float appliances in on the Y set to depth of bounding box. Y adjusted (guesswork) From library and original

Um, uh, yeah-me too. First the laptop, then the DT. If I had what you have and could wait until late fall I would before building new or even upgrading. Just use regular PBR or CPU based RT until then. (I'm hoping not to be building another but then who knows...:) I had mine built by AVA Direct and had (has) a full range of GPU choices. I talked with a sales guy to find out which parts of what I wanted had the best availability (IOW in stock) so got my machine in their normal build time of 6 weeks (including burn in and testing). The total was cheaper than parts would have cost me. I see on their site that GPU upcharges have dropped since then too. As to Quadro, i.e. workstation cards, this from Chief website. Video Card (GPU): Also referred to as the Graphics Card or Graphics Processing Unit (GPU), this is the part of your computer that produces the image you see on your screen. Since Chief Architect is a graphics intensive program, the graphics card is an extremely important part of the computer for day-to-day design work. There are a few types of Video Cards: integrated, workstation, and gaming. While some integrated (Intel) and workstation cards will work with the software, it may run slower since integrated (Intel) cards share computer resources from the CPU and RAM and workstation cards don’t perform well when doing 3D rendering in Chief. Gaming video cards do not share computer resources and are designed specifically for 3D rendering tasks used in Chief Architect. For best performance, we recommend a gaming class video card with 4GB+ or more of video memory on a Mac, and on a Windows PC NVIDIA’s GeForce RTX series or AMD

For me the answer was a 3070. When I had each of my machines built I had a choice of a full range of cards (except Ti which were not out then), first in the 2000s on the laptop and later the 3000s on the DT. I picked the xx70 for balance of performance, heat and noise. I also ran X13 on a laptop with a 6700k and GTX 980m w. 8GB. Been fine on all of them, just faster RTRT on the 3070 than the 2070s. I do enough RTRT to warrant jumping to the 3070 which is why I got the DT. I evaluated the time saved with Chiefs posted times for cards against actual times I had with the 2070s. A 3060 wasn't a sufficient jump for me though as Kbird notes plenty of folks on the forum are happy with theirs. Also for me, a 3080 or 90 didn't have the cost to time savings per year to be worth it while the heat and noise were higher than I wanted. Noise-I purposely was aiming for a (nearly) silent machine. The DT is right on the desk at ear height, 2 ft from my head. If there is nothing making any noise I can strain to hear a very slight barely perceptible low rumble all the time but never changes. There is no perceptible increase in noise when running RTRTs, often with 2 or 3 open. Temperature all around is always well within limits. (I have "cap live samples" checked, "use raytracing" unchecked in defaults turn on as needed, and set material defaults to show standard view instead of RT; seems to help? YMMV) Ti cards-From what I see a lot of the cost of Ti cards is an increase in VRAM. I've never seen any of my cards use more than 6GB of VRAM so not sold on the extra cost. Maybe the 3060Ti. Note that Dell shortens the GPUs on the AW machines which means that extra GPU cooling may be a good idea? FWIW I ran Dell Precision machines with Quadro cards for several years but switched shortly after I began using Chief to gaming machines; not looking back. 4000 series cards due in the fall look really interesting BUT the power consumption is way up. I haven't seen heat or noise yet and it appears they will benefit from a PCIE 5 MOBO for the power supply. Which may mean it might be best to just build a new machine, will wait and see, but likely staying where I am for a while. (don't scratch stuff that don't itch.)

Still have to clear the hinge body so I don't typically bother with those except for other reasons.

Note that you need more clearance on both sides for typical double door frameless cabinet unless you want to run into issues with the hinges. Also doors on frameless do not completely clear the inside of the sides the way Chief shows them. Attached library has 3 ROS set for proper clearances. ROs.calibz

A method that works in any view using an adjusted Rev-A-Shelf rollout. I have a bunch of other but for simplicity no need to build unless you really want to. This is for a single door cabinet offset more on the door side as is standard (I never put rollouts in double door cabinets, instead that width cabinet would be a 2drawer with an RO or 3 drawer) I don't bother to put the hardware for the offset either but certainly doable. The offset from the cabinet sides is achieved increasing the bounding box, then changing the X origin to offset to one side. TO get correct location within cabinet the Y origin is adjusted. I locked the depth so this is only for a 24" deep cabinet. You would need a left, a right and one centered with no X origin change for doubles. Place in library. IT is possible to NOT lock the depth OR to make special depths for more control.

As Ryan and Chop suggest you build it. This uses glass pony walls both top and bottom are glass walls.Place shower pan, place front glass wall, add barn door, change that to glass, drag wall down at top, drag wall up at bottom, set bottom glass pony wall to match top of door, raise bottom of door. Once you are happy with height of front wall drag side walls from the end of that so they match. You likely need to reverse the hinge side of the door to get it inside the shower. The corner brackets get floated in and moved to location. The hard part to get close to you picture is to hack the existing bonus sliding barn door hardware symbols to something close to what you show- OR build them from scratch. Note that both the track and hanger symbols need to be offset in the Y direction to end up inside the shower. The track also need to be offset in the X direction or it will be wrong. That part will require learning quite a bit about symbols, origin, stretch plane and such.

Needs to a drawer in CA. Use a trash as a drawerbox and use a door for the front.

I'm interested, sent PM.

Is this what you are after? it's bit easier in X13 but similar principle Curved panel.zip

Panel is a psolid, edge bead is a 3D molding line. Might consider searching for what I mentioned I don't generally make videos, just plans and info. I make all symbols completely within Chief. Digging into the plans is a way to learn how to deal with symbols overall instead of "how to do this one thing" ; at least that's how I learned so that's what I post. YMMV :)

Before converting to a symbol you need the panel and the frame to be using different materials. They can be copies of the same material with different names. FWIW that video is kind of old. Check over in symbols (or maybe in tips?) I've posted some plans for making cabinet doors-been a few over the years. IN general I make a center panel (wainscot panel) that has the framing bead on it. Convert that to a cabinet door symbol, then use a wall cabinet to make the door style. Then save that for later to make it EASY to change rail and stile widths, split to a double for tall cabinets, change the wainscot panel AND if you end up with a wood grain it will go in the proper direction on the rails and stiles. I just whipped up a quickie here that shows the sequence of making the door from a cabinet. Be sure to open ALL of the DBXs and ALL of the tabs in the symbols to understand what is going on. Wainscot panel symbol For the cabinet start with framed, 0" separation, set front to opening, delete the top and bottom separation and unCheck the wrench of the stiles so they are NOT set to default, no shelves. Then go around each side and back, select match front, then select custom face. Then go back and change the default separation to what you want-like 2". Go to the front, click the wrench for left and right stile so they are now default, add a top and bottom separation. Change the opening to side panel inset. Select a custom made wainscot panel., Check materials, convert to symbol, set stretch planes and check the offset. During conversion set each of the different materials to Plan Materials, USE default. Make a cabinet door.zip

It would be a good idea to select Copy and give it an appropriate name before deleting those layers. Otherwise ALL of the walls of that type will now not have drywall.

Use a color that matches roof with no real texture, rename it to OSB, edit surface and use the new OSB FWIW this has been around since the beginning of X13

After setting the reference display "save plan view" works for me.

Yes that's clear. What did you do before SPVs? that behavior for layersets has been around longer than I have. Back in the day-before annosets- sending to layout had the option to create a new layerset, think that was actually the default. Downside was it led to far too many layersets and little idea of what each one was. No I don't think it's necessary...I'd bet you can manage to work with the system I use. As I mentioned I have all of my clients use this and most are not particularly adept CA operators (why they hire me and they all manage. Personally I don't want extra warnings popping up (with my ADHD), I like control. Well as outlined below NO views share a layerset unless they are for different floors in which case I see no need anyway. If there is a need to have a different layerset for another floor see number 9 and 10 below. Thought about this a bit more and just to make sure I'm being clear. How I deal with it evolved from how I used Annosets. I had each set trigger a layerset (despite being told they were not intended to do that?) So just as you have I do that for everything that gets sent to layout-each has it's own default set and layerset. For some clients I keep the layout boxes in the layout template so already linked as I draw in relation to 0,0 (marker set in template). Make sure that the default set has a dedicated layerset do NOT allow "use active layer set". (this was the one I forgot to mention and can raise havoc) All of those have "save options" set to never so I don't get confused on closing. (should I stay or should I go..) Similarly I like to have a SVP for each discipline set to a specific floor. I often will jump floors while working and that way I (or client) don't mess up the layout. I set any defaults text size to by layer to reduce the number of default sets needed. Keep a working SPV per floor with a working layerset. That layerset can be changed at will. The SPV save setting is a personal pref and matters little. For clients I typically set to never to avoid pop ups. I do want them to save the plan though :) I keep a few default sets that are not tied to any SPV to make dimensioning some things easier and avoid needing to delete points from auto dims. Example is kitchen cabinets: a layerset that only shows what I want the dimension to snap to; base, wall, appliance centers. The dims all go to the same layer and the dim line is set to proximity fixed. Can also be useful for windows/doors. I'm in the middle of transitioning a client to SPVs and they are used to using some sets for different scalse. I don't use them myself since I use layer for text size which works for everything but rich text and arrows but left them to ease the transition. Not sure if that's a good idea but we're early in the transition. If needed when working it's easy enough to copy a layerset for a discipline then add visible layers to the dedicate layerset in the SPV as soon as done if needed or not if just for reference. I also have a few reference layer sets saved to use with different disciplines/views like demo, roof.... (can be used with number 9 above) Hope that helps.

Layersets have always worked this way even if you were to go back to annosets. Solution I use that's may help ... have a SVP (or more if you want one per floor) "working" which uses a layerset also "working" and a default set also set to working. That SVP and layerset never gets sent to layout. Actually I set all others to never save so that I'm not asked. IF there is a good reason to change a layerset then I save it when I make the change. That allows for changing dimension defaults and CAD layer within the working set, and indiscriminate changes to the working layer set since it never goes to layout. BUT those changes can be reflected in the appropriate SPV/layerset that does go to layout. Then tell my clients, who all use Chief, to NEVER change ANY other layerset or default set (annoset) UNLESS they absolutely know what they are doing and why.

Yes if you need the look OR if actual size of doors matters. Note that even with 1/16" reveal as the default you Chief makes the gap on a double door 1/32", which would bind IRL. It works better and has more control. I was making frameless cabinets from framed with 3/4" separation before Chief added frameless. I tried it, and check every new release, but have never found a reason to use the frameless option. I just don't get it. Now if it would allow for a true 5/8" side then maybe. reveals.plan

As with many appliance manufacturers nowadays you can get pretty much all current direct from Bosch-the zip folders contain several 3D format files and many also have 2D .

I'm guessing you are using notes to create the schedule? At least that's the only way I can reproduce what you have. Object number one is there it is just not showing a 2D symbol, if you were to include the number column I bet you would see the number. Which would mean that the object doesn't have a 2D symbol. Right click that row in the schedule and select "open row object". Note tab look at text above line- is it blank? should say %simple_schedule_number% Then the line style tab- is it using a layer that is off? or is the line style a blank? Below are the settings I used to reproduce what you have for the first item.There could be some other way to reproduce it but would need the plan for that.

The most likely issues are pline solids or some other symbol that pokes through the ceiling, roof layers, sometimes a wall definition or a wall defined as no room defintion, sometimes I've also sen a wall connection, a bad roof connection...Posting the plan would help.

Another Bluebeam Revu user, 12 years now. Only upgraded it twice. It's gotten a bit expensive, $350, since then but worth it IMO and only licensed to one machine. I have two licenses- one older than the other. Two things I use often is the ability to measure on an image with a user defined scale, and generate bookmarks for an entire PDF based on areas. I have TurboPDF (which is a version back of Foxit if you want to see a trial) on a third machine. I got that in a bundle along with TurboCAD deluxe that I got in a bundle currently at $250 for the bundle. The best cheaper option is PDFExchange Pro, $100. Trials are available. Bookmark areas

As Kbird1 said, check dell, it's $1700 there Personally I'd look at something newer and I'd go for a 3000 series card with a mobile processor for the budget