-
Posts
4324 -
Joined
Content Type
Profiles
Forums
Gallery
Everything posted by MarkMc
-
I'm planning a new build this year and asked at the show about video cards, specifically if anything changed or would change regarding the Radeon Pro cards. Answer I got was get a card that supports real time raytrace. Since they have no idea of what the supposed upcoming RT on AMD is an RTX card was suggested, especially for rendering.
-
Nowadays I use 3/4" which is easy in CA, more than that gets tricky and exactly what it looks like depends on framed or frameless (and if frameless check with the maker to make sure you get what you want) Plan attached.
-
It sounds as if you took a 3D view sent to layout as update on demand, then moved the camera sent to layout update on demand,...etc. So you only used one camera. Chief will update those views when printing. Since you used only one camera they will all look the same. IF that is the case then either send to layout using current screen as image OR export the view and then import it. The latter is used if you need better DPI than you get just using the send as image. IF that is not the case the best way to get an answer is to backup entire project from the layout, send to zip and post it. Note that the file must be under 25MB once zipped so if large plan you will need to trim the plan of non essentials.
-
When you say "change something" ; are you adding, removing, moving, or altering objects in the kitchen plan? and you expect that to not happen to those objects in another view? Just guessing here.
-
Here's how I do it. Then if you save these to your user library you can just drag a doorstyle onto the framed drawers to change JUST those to something different. Changing drawer fronts.mp4
-
Even if it were available that would change ALL the doors on the cabinet not just the top ones. Make a copy of the door style in user library and name it so you can identify it in the materials tab. Change the panel material there. Since you're cabinets appear to all be painted instead of using the default it's likely you need to change the species for the door frame too. I just used a framed door panel for now since that door is not on my system. Might look into taking advantage of using defaults more, also might want to purge your plan materials and merge some.
-
Did you try closing all and re-opening? Earlier today I was unable to paste a cabinet from one X12 plan into another. I tried clearing the clipboard but no go. Closed and re-opened and it was fine so not reproducible.
-
Just build it backwards plan attached Might want to consider attending free webinar next week Angle back cab.plan
-
There are several each with a downside. First one left is easiest-change horizontal separations to side panel inset specify slab. That should give you an idea of what to try next. As you try variations on the left one you'll get the idea of the problems and alternative answers. Far right is a custom side panel (one for each side) and a hacked back (next to try would be a custom sub-base/toe) OR you can decide it's not worth the trouble (hasn't been worth the trouble for you to dig in to try everything possible yet has it?) and leave it alone. (A big reason I don't like doing videos is that most often they teach how to do one thing and keep folks from digging into to how and why things happen.)
-
Referencing Several .plan files in a single Layout
MarkMc replied to kwhitt's topic in General Q & A
select layout box, click relink, browse -
I have no idea if there is a decent video, never watched one for it. Learned it all by trial and watching Scott Harris presentations/trainings. After seeing where you had gone I thought about doing one, instead decided to do a webinar. Here: https://chieftalk.chiefarchitect.com/topic/25146-cabinet-configurationhacking-webinar/
-
Open the cabinet in the attached. Ignore the defaults as they don't apply. Standard cabinet will give you toe on the side, custom side with "side panel inset" using a "wainscot panel" door symbol, set separations to suit. The curved side is a different matter ;-> (but can be done-maybe you can try that next) waiscot side.plan
-
Simplify. Frame elements are cabinet separations so you have complete control. All the rest is a single cabinet door. Open the plans I posted and open the objects!! Make special doors to use as "side panel inset" Plan attached is old but instructive, has the parts to make an assortment of panels and cameras to check location of moldings. I dropped on wainscot panel door symbol in as well. New Door template.plan
-
Thought I'd put these up before but guess not. Attached plan has a group of beaded inset cabinets (think these are 1/4" bead but didn't check). The are meant to be used when the make wants cabinet ordered individually then combined. These are meant to overlap each other by 1 1/2" so that they read correctly in the schedule then are called out as combined cabinets. The ones I posted some time ago are meant to be spit to create compound cabinets (takes some practice :))
-
Also posted coved edge frames
-
Plans with full set of cabinets are in the symbols forum from a few years ago. There are stand alone and a group meant to be used to get combined cabinets into a schedule (they overlap each other) OOPs split the wrong parts on that, corrected version attached. wainscot with bead.plan
-
Make he profile part of the door symbol. I have a collection of cabinet doors just for wainscot, here are two (right one done as Dermot suggests for Wainscot, left done as would be supplied by cabinet mfg Well you can but it's a lot of work. samples exist in the symbols forum from a few years ago. Stuck one in here wainscot with bead.plan
-
Mull two single doors.
-
I'm PC and regularly work with clients on Macs without issue. The only issues would be the same if working different machines all on the same OS-libraries and textures. Since all my clients are remote we use backup entire project though I also sometimes also make a library folder with symbols and textures per project for them. Since you indicated that you are already working multiple machines I'd guess you have the all set up.
-
Unless it's changed for X12 the ALDO is only in Premier edition. One client recently upgrade from Interiors to get it.
-
Since you aren't posting a plan I had a run at it. No idea how accurate it is to your model, only added enough windows to get some light in there. Roof is manual, second floor height was altered after roof was in. At first the entire front of the balcony was glowing, never managed to reproduce just the triangles glowing so some may not match yours. This is what finally go rid of all of the glow, bit counter intuitive but ....may help. The attached plan screenshot was X11, after I saw you were using 12 I checked it and it's the same. loft.plan
-
I've had this occur when a wall, or section of a wall is defined as no room definition. Attached were in X11 No room definition Change to room definition I chased lights, added subtracted and adjusted when this happened. The only thing that worked was changing the room definition. Yes it was sent in.
-
Locating drawer boxes in cabinets.Default slide clearance
MarkMc replied to DaveBox's topic in General Q & A
I made a quick run at this, had a little time, but no luck. Figured out what does NOT work and what likely has to happen to get you there. No help was- Adding a macro to an OIP field in the drawerbox symbol prior to adding to cabinet-doesn't show in cabinet, or any schedule once inserted into a cabinet. Tried adding an accessory to the components list and placing a macro for the box width-this may work but the macro I tried failed.. It IS possible to add a macro to an OIP field in the cabinet that calculates the correct width based on the cabinet width. That could easily be set up to be based on cabinet construction-framed, frameless, assorted frame widths. It is also possible to have the depth, front to back, calculated from the cabinet box in an OIP field. The difficult one is the box height. It is likely best calculated from the actual accessory. This IS possible BUT I don't yet know the correct way to do it. The Drawer box accessory symbols end up in a "Collection" in Ruby. I got that far and the first thing I tried failed. I just have to look into accessing information from a collection, which is doable. That will take me a little more time to look into, will let you know if I figure it ou. Figure getting this to work might get that potential client moving
