Page 1 of 1

Findings: 3DROTATE, DYNAMIC INPUT - Z AXIS and CRASHES

Posted: Sun May 17, 2026 3:50 am
by sanches
Hi guys,

I wanted to share a few findings with the community that I think everyone will find useful:

1. The "ROTATE3D" function is not working.

2. Dynamic Input does not work for the Z-axis. This is a big one, as I initially thought something was wrong with IntelliCAD itself. However, there is a workaround: instead of just typing a value (e.g., 500), you need to type the full coordinates: 0,0,500. Also, if you drag the line downwards, you must explicitly type the minus sign (-), even if you have already pointed the cursor in that direction.

3. In general, the software is quite unstable when handling larger files or when working directly from the cloud. I highly recommend saving your progress constantly using incremental file names (e.g., Filename_R12b7xc). If it crashes, check your temporary files folder—you might not get the absolute latest version, but it will definitely save you from starting from scratch.

Hope this helps. Happy to hear if anyone has found better workarounds.
AleX

Re: Findings: 3DROTATE, DYNAMIC INPUT - Z AXIS and CRASHES

Posted: Fri May 22, 2026 2:27 pm
by CMS Inc
Avoid storing active working files in cloud-synchronized folders. Cloud sync platforms, such as OneDrive, are incompatible with the way .dwg files are saved. This conflict particularly impacts CAD software handling large .dwg files or external references (xrefs).
Characterizing the software as unstable is inaccurate in this scenario; the root cause lies entirely with the cloud-synchronization conflict.

Re: Findings: 3DROTATE, DYNAMIC INPUT - Z AXIS and CRASHES

Posted: Fri Jun 19, 2026 2:14 am
by Quintorrell
CMS Inc wrote:
Fri May 22, 2026 2:27 pm
Avoid storing active working files in cloud-synchronized folders. Cloud sync platforms, such as OneDrive, are incompatible with the way .dwg files are saved. This conflict particularly impacts CAD software handling large .dwg files or external references (xrefs).
Characterizing the software geometry dash as unstable is inaccurate in this scenario; the root cause lies entirely with the cloud-synchronization conflict.
Have you been able to reproduce the ROTATE3D issue and the Dynamic Input Z axis behavior when working entirely from a local drive?