josecarlos

This issue persists across three consecutive Nvidia driver updates. Currently, neither Nvidia nor Chief Architect support has provided a timeline for a fix.

We are now on the third Nvidia driver iteration without a resolution. There is still no official ETA for a fix from either Nvidia or Chief Architect support.

Beside testing, will you provide an ETA for a fix on this issue?

Don't update to NVidia 610.74 Driver as chief architect X17 unexpectedly quit.

@LotzCC this will happen when if you join different pitch roof together. This error it seems is affected by the Gable/Eave Fascia setting, as you turning off the soffit will match.

Hi Deoug sent you an email, I believe I can help you.

I don't know if this issue is related to multi monitor setup, as I make some samples with one monitor and ray tracing enable, I didn't have the problem again, could someone confirm?

I have the same Issue and I just disable GPU Ray Tracing as the recommendation on known-incompatibilities from Chief Architect on Intel Arc Graphics (no problem so far). This Issue seems to be happened before: Known Incompatibilities with Chief Architect Software - Windows 11 with NVIDIA 30 Series Graphics. I do use other software for rendering and no related issue with nvidia driver or Ray Tracing.

Hi @Doug_N, I don't believe it has anything to be with the mouse but it could be a hardware related issue.

Found similar posts.

I have the same Issue but I'm using corsair gaming mouse, I change the report rate to 250 and didn't work for me, also there are two more threads reporting this issue.

I do have the same Issue on my computer and the only similar things on the hardware are: i9-9900K, 32gb, nvidia 1080 card, and a raid0 2 TB SSD drive.