SHCanada2

...and yes I get this all the time as well. When I first started using CA I think the first "suggestion" I made was to correct this behaviour

I tried out a soffit yesterday and it seemed to work (if square instead of angle works for you, but it was also between two walls, so only the front had to be covered.

well, I've been doing some testing over the last year. I used to always print to ARCH D but that took forever. So I changed to tabloid. I've tried different DPIs. Today I print at 300 DPI, 11x17, 29 pages with 8 PBRs is 5MB file size. Elevations are plot line. The most I ever see is around 15MB PDF file size. Not sure what I am doing different if you are getting 30-50MB PDF files

5 seconds to print, but it also takes the following time to "manage" the image files: 1. open each from layout: 2s2. Render the 300 samples: 6 seconds3. Export image to file at 1800 pixels per inch: 1 second That doesnt include sending it to layout, it assumes the "export to the same filename" method (I don't remember who said they do this, in order to not have to resize the image all the time) multiple that by 8=72 so 1min 17 seconds total it takes ~2 min to print the layout with the PBR layout boxes ...the first time. any subsequent times because the memory is pinned now takes a long time, PBR camera are also down to 1 sample/s, from what I normally get which is ~40 sample per second. If I close the layout and reopen, everything is fine. CA is now aware of this issue, and I would assume they will correct it. So yes I could uses images, but seems like an awful lot of click click, rinse repeat. if the memory issues was sorted out, and released, then I would be taking a ~45 second hit when printing compared to managing the image files. In my view, something that is done repetitively manually should not be quicker than doing it automatically. If the automatically (PBR layout boxes) is markedly slower, perhaps then CA should look at creating image files for the PBR box when printing PBR boxes. In my view, looking ahead into the future, there will be more and more PBR used and it would be worthwhile for CA to make the printing of the PBR as efficient as possible. For me, once I setup the PBR cameras, I dont really look at them, I'll work on the plan's little details using the elevations, floor view, or external non pbr camera , and then I just print the layout. I really dont want to constantly think to myself, "did I do something that affects the PBR camera and now I have to export the image?" I just want to print to pdf

a bit of an update: The problem where the GPU memory stays pinned at ~ my max of 8GB, is repeatable. Occurs after printing to PDF on a layout I have which has 8 PBR views on it if I close the layout the GPU memory drops to zero. Support is looking into it

post the plan and which room you want to change

thats what I do, one for the plot and building, one for objects on the foundation level, one for eaves from the top level

purely a guess, but did you check your date time settings in windows? In the Region panel, under the Date and time formats section, you’ll find the option to select the Short date, Long date, Short time, Long time, and First day of week from the respective drop-down menus.

if you have some of the more advanced, cheaper, laser measurer, you can stand 20' away, take a horizontal measurement, and point to the top of the tree and take that measurement, and then the device will calculate it for you. ...but the above method usually only works at night/dusk when you can see the laser

slick...and creative use of solids. merci. would be nice to appear by default. otherwise need to place one per room. It might also help solve another problem for sections and elevations related to global variables...

after playing around, I forgot that text macros are just text, and there is no real way to create a macro which does a if %DET_CLADDING%=="STUCCO" then %RSI%=2, as ruby macros cannot read text macros or write to text macros (well they can read in a round about way but then you have to manage the global variable problem between plans, and because these show up in cross sections, that is harder to do), but even if it could read them, it would write to a global variable, and then I would have to manage them between plans ...or start writing to files. Anywho, maybe I'll come back to it another time so I think in absence of doing the Kristjanm method of the model (whiich I will put on my "try this out list"), I think the master spreadsheet and copying either to text boxes, or notes is the way to go. Notes have one advantage in that one doesnt have to place text boxes, one just keeps the notes in the user library, and put the note on the section. If there is a new wall assembly, then create a new note, which I assume is similar to your text box blocks. ...not a whole lot of difference However, the note method is also not as pretty as having the wall assembly graphic next to it, which, especially the 3D ones, have the wow factor. so a chocie between a little quicker, but less pretty . I suppose the note method would also guarantee the wall number in the cross section matches, where if using text boxes there would be a possibility of putting a W2 label on a wall in the cross section, and then the text box actually has W1. But my guess is, there is always the same numbering, W1 for above grade W2 for below grade, W3 for garage etc..

L shaped as you come in the door. then swap bedroom for bathroom. you may wish to check with the engineer. for here typical 2x10 joists will span more than 6'. Maybe you can have him move those two beams closer together in the middle

yeah its something weird, if you look at the GPU processor it is up and down like a yo yo

i may be imagining things, but it seems like this got worse after the last update a couple months ago. So I just printed to pdf my layout, and tried to close the layout without saving and the GPU is going crazy for like a minute and a half, before the layout would finally close we will see what they say

I can try the sample size cut down. I personnally hate the continual sending of images. Ultimately, I would just like to know why it doesn't seem to obey the "update on demand" and if there is a way to make it only update when I tell it to.

I thought the whole point of update on demand is so it does nothing on the PBR, until I ask it to update (or it prints). seems odd I'll send it in thanks

not really the floor joist,. it gives a nailer instead of using an anchor bolt to put the wall on. They nail the 2x4 boards into the form before pouring, and then they just put the nails out and leave the 2x4 on edge. blocked every 48". it actually makes for a nice cribbing job because they take a flat tool like an ice scraper and just scrape off the conrete using the 2x4 on edge embedded in the top of the wall. Very level and mostly flat

yup something to do with the layout. once I close it, the memory is released and GPU drops to 0

I've noticed the undo and other things(today I right clicked on a PBR camera in th project browser) sometimes takes a very long time(> 1 min) to complete (of course the object browser has a preview so perhaps that is why it takes so long, but why longer than opening up the camera in its own tab?). Today I added a revision to layout and then I clicked the undo. CA sat there spinning for a minute or so, and the kicker is the GPU is going crazy in task manager with CA occupying it. I have 5 "update on demand" PBR layout boxes in my layout . Anyone else seeing this? and if so, do you have layout boxes with PBR (i.e. not images)? Its not repeatable on demand. Its like something is triggering the PBR, but even if it was, the :"sitting there spinning" is lasting a lot longer than the PBR actually takes to complete when the PBR is open. .....maybe all 5 are bing updated periodically even though nothing was changed that affected them .... intreresting that the GPU memory is also pinned. I haven't noticed that before.

i heard from a transpanted cribber than no one else but alberta uses a "ladder", so that will be interesting to see if it is adopted in the NBC 2) Except as provided in Sentences (3) to (6), anchorage shall be provided by a) embedding the ends of the first floor joists in concrete, b) fastening the sill plate to the foundation with not less than 12.7 mm diam anchor bolts spaced not more than 2.4 m o.c., or c) embedding in concrete two 38 mm by 89 mm sill plates placed on edge and separated by blocking spaced 1.2 m o.c c) is alberta and the whole "suite" thing is different between provinces. I'm not holding my breath that they will be harmonized...maybe the just the energy component

Thanks, I'll take a look. Alberta, but we also have our own version of the NBC. So it will be interesting to see if we adopt it

how do you do this for rimboard, floors above garages, cantilever floors, walls partially above grade, etc. polyline apoolza? interesting, I had thoguht one needed somne sort of software to do this, good to know you are able to do it (I assume with not too much effort) in CA

i am concurring with you. i.e. figuring out the areas required for the tradeoff is too time consuming. I did it once for a whole house, it was a PITA. right ... I didnt think to go 2x8. zone 7A for 2x6 requires R24 and the RSI of the cladding to make 2.97. I just looked and zone 6 is the same, 2.97. Throw on another layer of gypsum to make it to 2.97 for 2x6 tall walls if you arent including cladding in your calc? or add exterior insul? exterior stone? 2 ply gypsum would be unconventional but would get to the number: ...would just have to remember to get a different window thickness EXTERIOR AIR FILM 0.03 CLADDING 0 WATER RESISTIVE BARRIER 0 3/8" OSB SHEATHING 0.09 2X6 (12" O.C) C/W R24 INSULATION 2.6 POLYETHYLENE VAPOUR BARRIER 0 1/2" GYPSUM BOARD 0.08 INTERIOR AIR FILM 0.12 ASSEMBLY EFFECTIVE RSI 2.92 ZONE 7A (W/HRV) ABC 9.36 REQ 2.97 or if the tall wall has no windows, calcualting the actual area of the studs instead to the 25.5%? or is it a well kept trade secret ?

good advice

once you get to a tall wall, arent you going to need the RSI of the cladding to make the requirement? or do you put in R24?