Zirax1

Thank you both so much for your help. Chopsaw - The particular trusses I want to use don't go bigger than around 24-26 feet at 16" deep (The size I am using). Glennw - Thanks! I completely forgot about the Bearing Line. That did the trick. The extra 8 Inches won't mess me up. It's more about the accurate counts and the length being within the closest 2 feet. Since I am doing lapped, any little bit extras won't matter.

Yes, they are floor trusses. When I edit the truss, I can see the name of them are "Floor Truss". They need to be broken due to the lengths. Some of the spans are 34+ feet. The length and height of trusses I am looking to use do not span that far. There isn't a break option when I select the truss like there is on a wall. The I-Joists are lapping (Breaking) successfully over the walls and the beams since I specified the walls and beams are bearing walls/beams. The trusses just seem to ignore the bearing beams for some reason.

Hello all, Recently upgraded to X15 and started using the new Auto Truss feature. I have a couple of beams and have trusses set to bare on them, but they are just going over the beam between the walls and not lapping on the beams. The heights are correct, but unlike the I-Joists, they are not lapping on the beams. They are working properly on the baring walls, just not the baring beams. Am I missing something or is this a bug? If I switch back to I-Joists, they lap properly over everything (walls and beams). Thanks!

Wanted to note that after updating to the latest version, 23.2.0.55x64, the problem has been resolved for me.

Repair didn't help. I am still at a loss as to what could be causing it. It is exactly as Kintaro said.

Something I have seemed to notice is it lasts almost exactly 14-15 min before the issue occurs. It also doesn't seem to count time that Chief Architect is NOT the active window. I'll try to pay closer attention, but I believe that is what is occurring. Example: Working in Chief Architect for 10 min, watch a 30 min cat video, 5 more min in Chief Architect and it will lock whatever function I am in (normally the mouse selector). I just decided to run a repair, so I'll see if that has any bearing on the issue and report back.

I would assume if this was a larger issue, a lot more people would be having it. So it must be something unique to our setups. I am running a newer computer. Custom built myself. i9-9900K, 32 GB of RAM, M.2 NVMe 2 TB SSD, NVIDIA GeForce RTX2060, Logitech Wave Keyboard and Mouse. I am running Windows 10 Pro fully updated to 21H1. I am using Chief Architect Premier X13. How about everyone else? I want to see if we have any similar hardware or software that could have some conflict with Chief Architect.

I have the same/similar issue. After about 5-10 min of using the mouse, if I am in camera view, my mouse will get stuck where it moves the view around without clicking any buttons. If I am in layout view, the mouse will get stuck as if the left mouse button is stuck down and will only draw selection boxes. I can hit escape to stop the box, but as soon as I move the mouse it will draw another selection box. It doesn't actually select anything though because it doesn't "Release" the selection of the items. Worked fine on X12 on this PC. Installed X13 and it's occurred since that moment. Mouse works fine on all other functions of the computer.