SHCanada2

for interior doors I've always known the RO to be door width +2" for prehung off the shelf doors

@solverhow did you get the frieze to show up on the short walls? I cant tell from the video

i have a macro as well tied to a poly line. Draw a polyline in the elevation, mark the windows as being on that elevation and it will calculate a percentage. If Doug_N does not get you what you need, let me know. he has been around a lot longer so his may take care of more scenarios

thats kind of what I came to the conclusion of...they were snapping too often to where I did not want. I'll also confess though that I never ensured the walls were on the gridlines

The other tidbit I discovered to help prevent these (not equal to the correct angle) is the make parallel/perpendicular tool. Using this tool you can ensure your roof planes are always 90s or whatever, just not 90,123455 (draw a 45 deg line an then make it parallel to that line)

well I turned off ray tracing and then turned it back on and now the samples are increasing on the dental camera (which I create a new one today) but now I notice the outside wall baseboard looks like a bad paint job, some light problems or something

well interestingly, the status bar where the samples normally count just said "rendering finished", where the samples keep increasing for the lobby camera, but I cant tell the difference in settings

..well I think it is ... doesnt the little check box on the right mean it is?

as a somewhat new person to CA, (been at it for a year and a half) I don't understand the approach comment. Rene seems to be able to get good ray tracing, but others cannot. What does that have to do with an approach? I'm confused Please all, enlighten me. For what I think was my second attempt at ray tracing, with some help from people here, I thought it turned out pretty darn good, but maybe I'm missingsomething

use a railing with 4x4 posts, and hand draw a roof

there is also attic walls on the second storey for the garage. you might want to try a quick model of putting the garage on the foundation, and build the house on the 1st level

you might want to send it to tech support. The fact that the concrete wall works, and the wood wall does not seems odd, even when I cut the stucco with the roof plane, it still draws a thin attic wall. and I aligned the wood wall to the outside so i think it should have worked The pony wall idea did not really help (it is the same outcome as the other solution). so if you set the wall to "Roof cuts wall at bottom" and perhaps move the roof plane in, you should get the last output above but if you want ot play with the pony wall

but it is also not modelled correctly between the two floors there is a gap in the concrete now, presumably for the sill plate. so not sure this is the best solution. If I just set the wall to "Roof cuts wall at bottom" it also works but the overview still shows off, but the attic wall is still there becuase if I toggle it off it no longer shows so not sure how to get rid of it I suppose you could assign that attic wall to a different layer and not show it, but probably not tte best solution

is your intent to have wood walls below the terrain? if I change your wall type to concrete for the garage and this wall, then it works correctly. I then created a pony wall for that wall and moved the roof plane to cut the stucco: shows correct in floor overview but not in perspective, the attic wall is still there. if you toggle it off it will not show btw your closet elevation does not match the adjacent room

your 14" dimension does not line up to the 13-1/2" dimension. My guess is one of your dimensions is going to drywall, the other to stud. Turning on the wall layers in your active layer display options as MPDesign indicates, should show what is going on

maybe post the plan, assuming you tried the "all layers on" layer set

i've been looking for similar, for side entry garages, to show that the vehicle can make it in and out I searched for sweep paths a couple months ago, but did not find anything easily useable

interesting, one downside is that if one works with full zoom to the building, then, one would have to zoom out to click them. other downside is it opens up a new tab, but i'm not sure that is a downside. Today I go to the layout where I have these already predone, and then double click on them to open them as a new tab, if I am "checking" the layout

I tend to add these(camera views and other things) to my template as opposed to "saving as a template". Just a preference as Im never certain what I have done to a plan through the life of the project, But I also have 4 walls and a foundation on my template, so this is my starting point per se for my projects.

what I've gone to is once I sent the plans to the customer, before I come back and open up the plans to do another revision, I create copy of the plan in the directory using windows explorer. Then you never need to do the above. One half dozen or the other

yup that worked thanks

the more I look at the screenshot the more it seems unlikley. The macro could fail on owner.function or owner.floor_number but kBrid looks to have a room selected, so it should not. The comparison statements are using the correct data types so it should not fail on that. i tested it by hooking it to other objects and all it ever comes back with is evaluation error I suppose it is possible owner.function or owner.floor_number returns nil and the comparison fails and never returns The only other failure could be the rounding or _to_s for standard_area. so if standard_area return nil, I suppose the rounding function could break and never return. but by testing it against objects that do not have those properties, that tests most of the above and after all that, the bottom right of the TMM editor in Kbird's screenshot actually has a result so it would suggest it ran sucessfully so it still seems rather odd it would hang in the editor, @Kbird1 did it only hang the once?

well i posted the check pretty much everything version over in the tips and tricks. but I also ran it 5 ways to sunday with some without some checks, never saw it hang. If it hangs in TMM but not in the macro execution, then this would suggest the TMM is not following the same behaviour as the CA plan view version of the macro execution. it would also appear by the screen shot that it is actually in the TMM editor, not the TMM container as normally once you click on the marco in the TMM container it runs the macro. The macro is very basic, it would seem odd it would falter on something so simple. my thoughts are perhaps it is something else. Perhaps it is the goofy browser thing, which happened again to me today, except it was a zoom web window

attached is the error checking and variable assignment checking versions (with an _1). It ensures if you have two files open with different number of floors and then close the one with more floors and go back to the one with less floors, it maintains the correct number of floors. one caveat, you need a polyline with a label anywhere on the mainfloor plan view(I have mine just above the richtext box) which assigns a unique id to the plan for variable $fileVerify. if you do not know how to do this send me a message. These macros with the error checking also leaves the rich text box blank if it does not have all of the floor areas or runs into an issue. Printing the layout with all the floors will update the floor areas, or simply going up and down through the floors in plan view will do it as well I personally would rather see "evaluation error" but i suppose if things go sideways, no one wants to see that on their layout allarearef_1.json floorarea_1.json

looks like you need a rich text box because the macro uses the tab function. for some reason it did not always take if I pasted %allarearef% into the text box. I would suggest select the allarearef marco using the >M