Doug_N

Do you mean the opening in the wall or the actual glass area of the window? The window area (including frame and all other components for mounting the glass) are baked in calculations that CA does automatically and can show on the schedule. The area of the glass not including mounting components is not tracked by CA but can be calculated using a custom ruby macro.

I am experiencing the same problem with X-13 and Windows 10 64b pro. The number of crashes has been reduced, but I lay the responsibility for this pretty squarely at the feet of NVidea. The only thing that I think that CA could do is somehow program a trap that still allows work up to that point to be saved. For some reason auto save seems to stop working sometime prior to the fatal crash and abend.

One more question, does this only happen with NVidia? Any of your experiencing this with AMD or any other cards?

Have any of you notice something strange with the auto-save feature before one of the dreaded device removed crash. It seems to me that auto-save stops working at some point prior to the crash. It may be that there are a few things going wrong with the program's functioning before the device removed crash occurs. The most frustrating thing is that this crash, that seems to be related to camera views, completely abends (makes the internal processes) stop entirely, except for the ability of the program to display the crash notice. There is no way to do a save. The exit is fatal to anything that you did from the last time that you opened the plan and layout file. Thoughts and observations anyone?

Rob is so right! Demot, I have owned CA for a while now and can download older versions if I need to use them for any reason (I haven't found one yet, but I can imagine doing work for someone else that has an older version and wants it maintained in that version). If you buy a new license, will CA let you download and use an older version that predates your first use of the product?

Here is an old video on "California Room Addition". Great job by the author.

It can be done, but it is really awkward to do in CA. Most times I just cover this off with a note pointing at the valley. This note reads "Board 1 x 10 Flat on Existing Sheathing".

Here is an illustration of how the plank is laid flat on the roof. Note the sheathing is removed for clarity, normally the sheathing outside of the new roof is left in place, while the sheathing under the new roof is partially removed for air circulation. .

Yes just like that. So far as I can tell it is pretty much the same everywhere in North America where shingle roofs are used.

The valley rafters are normally on the flat over the other roof structure, not on edge as CA generates then though.

Do you have truss selected in the roof DBX?

Have you made a report to tech support? This looks like a bug to me, especially if you had automatic birdsmouth.

Brother Printer https://www.brother.ca/en/p/MFCJ6945DW This does it all. Two trays (I load them 8 1/2 x 11 and 11 x 17. Prints both sizes flawlessly, scans up to 11 x 17 in colour and isn't all that bad on ink. Had mine for a year now with no problems at all.

CA Blocks can also be edited without exploding since X13. Just saying.

With AutoCad you can edit blocks in place to change line weights and edit text etc. Just saying.

Good news for some of us, but there is the same problem with GTX cards as well, such as my GTX970 running on Windows 10 64b Pro. Hopefully, they will solve that issue too.

Unfortunately, all of my project files have been done in X13 and I wasn't experiencing this problem until about a month ago. The problem has gotten progressively worse to the point where it is becoming difficult to make any progress. There is no chance to save anything, nor report the error, as in Rich's example. Mine just crashes and exits. If you are in the clean up drawing problems during workflow, when a crash occurs, you have to go and check all the corrections that you have made. It is easy, at this point, to miss something that you thought that you corrected, but has reverted to the error condition. This is a real headache.

Updated the driver, but still getting the crashes. They seem to be more frequent as the project file grows.

Working on it. Let's see how this goes. Fingers crossed

I wonder if this is related to Covid-19? The device removed error and resulting crash seems to be spreading. My setup: X13 MSI NVidia GTX970 Windows 10 64b Pro 2 TB SSD drive C: data is mirrored to MS OneDrive. I would attach the working files, but the zip file is too big. I have reported this to tech support. This is the crash message. When it appears the menu for the program is locked and there is no chance to save whatever you were working on. If you click on "Check Knowledge Base" this is what you get:

Rene, Well that is disappointing to hear. Thanks for your feedback though. I will have to find another way to do the in situ background. CA certainly doesn't make this aspect easy, Doug

Rene, I bought a 3d camera to document my as built projects prior to doing renovation and addition drawings. I was wondering if could offer any advice for creating somewhat realistic neighborhood spherical background pictures so that I could drop my model into the actual neighborhood of the project? The camera that I bought is the RICOH THETA SC2

The roof baseline, when generated by CA is located above the outer plane of the wall's main layer. (from the CA Help File) Editing Roof Baselines The pitch direction and initial height of any roof plane - manual or automatic - is determined by its Baseline. See The Baseline. In plan view, a Baseline can be selected and edited independent of the roof plane. To select it, click on the roof plane at the location of the Baseline and then click the Select Next Object edit button. The Status Bar tells you when the roof plane Baseline is selected. See Select Next Object. If a roof plane Baseline is moved, its height will not change. Instead, the height of the roof plane will be affected. In most cases, therefore, moving a roof plane’s Baseline independent of the roof plane itself is not recommended. If the angle of a roof plane’s Baseline is changed, the direction of the roof plane’s pitch will be modified. The Baseline Angle can be modified in either of two ways:In the Roof Plane Specification dialog. This will change its angle relative to the floor, and will tilt the roof plane along an axis perpendicular to its Baseline. This method is helpful when a specific eave angle is needed. See General Panel. Using its Rotate edit handle in plan view. This will change its angle rela tive to the roof plane’s eave or ridge and will modify the direction of the pitch. This method is best when the pitch direction matters more than the angle of the eave. Both of these methods can be used to modify the same roof plane, although the second approach makes it difficult to control both the pitch direction and eave angle, and is not recommended. The length of a roof plane Baseline can be lengthened or shortened using its edit handles without changing any of the roof plane’s attributes. This is from a test file that I used to auto generate roof planes, then the edit roof DBX The roof BASELINE seems to be the place where the outer plane of the wall main layer intersects the top edge of the roof rafter when using conventional framing. Moving the baseline by editing WILL CHANGE THE ENTIRE LOCATION OF THE ROOF PLANE! This means that all of the intersections of the roof valleys, ridge intersection and fascia height for that plane will be changed. This is just a heads up that changing the location of the baseline may have unexpected results in the roof structure. It may be easier to delete the plane, and then draw a new roof baseline over the bearing wall, then editing intersections using the join roof planes tool.

Do you have any evidence that this is, in fact, the case? I have not seen any such evidence, and to the best of my knowledge, everyone who has reported this has a valid licence. I know that I do. I experience erratic mouse behaviour with X-13 that I never experienced with X-12.

Framing groups doesn't help with this problem unless you frame the interior floor, then change the "ballooning" attribute for the rear wall, then frame the deck, and make sure that you don't have automatic floor framing turned on at any time or command the floor framing to be rebuilt.