- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
It seems that this problem may be caused by DVIEW TArget and CAmera points being very close together in Z-value. (I still don't know what cause that). Trying to set them coincident to test failed as AutoCAD does not allow them to be coincident... so I set them very close to each other but that did not cause DVIEW TWist to recreate the problem. Nevertheless, there were similarities between this problem and another I had some while back:
https://forums.autodesk.com/t5/civil-3d-forum/cannot-select-3d-lines/m-p/6223167#M297306
I've modified my code to set both FRONTZ and BACKZ, turn off clipping, and reset TARGET Z-values (POints option sets this) before my DVIEW TWist command. That seems to have solved my problem... so far.
Summary: DVIEW TWist sometimes changes the TARGET and/or BACKZ Z-values to huge or minuscule numbers (#.#e+99). It seems especially so if they are already not zero. Resetting FRONTZ, BACKZ, turning OFF DVIEW CLipping and resetting the TARGET (POints option) before executing DVIEW TWist keeps these Z-values from being jacked... so far.
;Use (GETVAR "VIEWCTR") to keep the view in the same place after DVIEW
(COMMAND "._DVIEW" "" "CL" "B" "0.0" "CL" "F" "0.0" "CL" "OFF" "PO" (LIST (CAR (GETVAR "VIEWCTR"))(CADR(GETVAR "VIEWCTR"))0.0) (LIST (CAR (GETVAR "VIEWCTR"))(CADR(GETVAR "VIEWCTR"))1.0) "TW" vwang "")
Product Version: 13.6.1963.0 Civil 3D 2024.4.1 Update Built on: U.202.0.0 AutoCAD 2024.1.6
27.0.37.14 Autodesk AutoCAD Map 3D 2024.0.1
8.6.52.0 AutoCAD Architecture 2024