SHCanada2 Posted 19 hours ago Share Posted 19 hours ago seems to happen on residential template as well. only happens in section views. plan views are fine. auto build framing is off Anyone else seen this? its pianfull when trying to move something to a specific spot, because you have top move the mouse and then wait for CA to catch up Its been happening for awhile. I updated my video driver a couple days ago, but its no better see attached ' Screen Recording 2026-05-27 203604.mp4 Link to comment Share on other sites More sharing options...
ValleyGuy Posted 19 hours ago Share Posted 19 hours ago 10 minutes ago, SHCanada2 said: seems to happen on residential template as well. only happens in section views. plan views are fine. auto build framing is off Anyone else seen this? its pianfull when trying to move something to a specific spot, because you have top move the mouse and then wait for CA to catch up Its been happening for awhile. I updated my video driver a couple days ago, but its no better see attached ' Screen Recording 2026-05-27 203604.mp4 11.01 MB · 0 downloads I also experienced this. I did a complete shut down and rebooted my Mac and it seemed to clear up the glitch. Link to comment Share on other sites More sharing options...
Joe_Carrick Posted 18 hours ago Share Posted 18 hours ago I'm not seeing this problem. What rendering mode are you using? What LayerSet? Link to comment Share on other sites More sharing options...
SHCanada2 Posted 6 hours ago Author Share Posted 6 hours ago (edited) 12 hours ago, Joe_Carrick said: What rendering mode are you using? What LayerSet? i just drew 4 walls on the stock residential template, then a back clipped cross section, so the stock layerset assocaited with that. But I did try before that, on my own plan switching to the all layers off layerset, so nothing was showing, and it was still happening. But the plan view is always fine 13 hours ago, ValleyGuy said: I did a complete shut down and rebooted my Mac and it seemed to clear up the glitch. how often are you rebooting? I get windows crashes on a regular basis when I have PBR opened (never used to before say 5 months ago), so for this reason the computer is getting rebooted on a fairly regular basis. but I will try and do a clean reboot to see if it changes anything Edited 6 hours ago by SHCanada2 Link to comment Share on other sites More sharing options...
ValleyGuy Posted 5 hours ago Share Posted 5 hours ago 42 minutes ago, SHCanada2 said: i just drew 4 walls on the stock residential template, then a back clipped cross section, so the stock layerset assocaited with that. But I did try before that, on my own plan switching to the all layers off layerset, so nothing was showing, and it was still happening. But the plan view is always fine how often are you rebooting? I get windows crashes on a regular basis when I have PBR opened (never used to before say 5 months ago), so for this reason the computer is getting rebooted on a fairly regular basis. but I will try and do a clean reboot to see if it changes anything It only happened once and I am not quite sure what triggered it. I don't use PBR, ...well I do click on it once every year or so - I'm not sure if I hit the button the day that I had the lag issue or not. The only computer crashes I have are if I leave CA open (no plan or layout open) too long without using the program. Example: if I close down the plan but don't exit the program overnight, then in the morning I will see where my computer rebooted itself with a 'Kernel Panicked' reboot report. But no crashes while I'm using the program. On a separate note, I just had an error the other day to which I followed CA protocol and sent in a bunch of information. It too was on a cross section elevation; just updating a view port on the layout. CA Helpdesk couldn't find or replicate any issues and I haven't had any issues since. Both the lag issue and the error code seem to be one-offs. I only loaded up X17 a couple of months ago but have had two strange things happen as well as a few Kernel reboots. Link to comment Share on other sites More sharing options...
Joe_Carrick Posted 3 hours ago Share Posted 3 hours ago Evidently this only happens on a Mac - and then only under certain conditions. Link to comment Share on other sites More sharing options...
SHCanada2 Posted 3 hours ago Author Share Posted 3 hours ago 37 minutes ago, Joe_Carrick said: Evidently this only happens on a Mac - and then only under certain conditions. well maybe if it happened in 1988 when I last used a mac ... Link to comment Share on other sites More sharing options...
SHCanada2 Posted 4 minutes ago Author Share Posted 4 minutes ago (edited) i rebooted, same issue. Tried to see if it happend on X16, and got this error when just starting X16 without opening anything going to try and roll back the driver Edited 3 minutes ago by SHCanada2 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now