Display posts from previous
Sort by

Changes to 12.1 causes issues with relative/absolute inputs.

#1 by sln8458
What has changed between 12.0 and 12.1?

While my problem is highlighted in my piping lsp add-on, the issue is NOT lisp related I believe.

Here I have created a line from 0,100,0 to 100,0,0 via lsp, but when I 'list' the line it is not from/to these co-ordinates.
Command: _line
ENTER to use last point/[Follow]/<Start of line>: 0,100,0
[Angle/Length]/<End point>: @100,0,0
[Angle/Length/Follow/Undo]/<End point>:
Command:
Opposite corner:
Command: _ERASE
1 found
Command:
Opposite corner:
Command: LI
--------------------------- LINE ----------------------------------
Handle: 67B
Current space: Model space
Layer: 0
Color: BYLAYER
Linetype: BYLAYER
Line weight: BYLAYER
From point: X = 0 Y = 0 Z = 0
To point: X = 100 Y = 0 Z = 0
Length: 100
Angle in UCS XY plane: 0
Delta values: X = 100 Y = 0 Z = 0
Anyone have a clue why this is??
CMS INTELLICAD 13.0.737.158051.PE+.VC17.x64.CMS130

i9-12900k / 64gb-3200 - NVIDIA GeForce TRX 3060 Ti 8Gb Windows 11 Pro

Re: Changes to 12.1 causes issues with relative/absolute inputs.

#2 by sln8458
Here is another example:
Create a cylinder of radius 14.6 and a height of 265 at WCS origin

code:

Code: Select all

(command "_cylinder" "0,0,0" (* 0.1 FTF#) (rtos  OBORE#))
FTF# = 146
OBORE# = 265

result:
Command: _cylinder
[Elliptical]/<Center of base of cylinder> <0,0,0>: 0,0,0
[Diameter]/<Radius of cylinder>: 14.6
[Center of second end/2Point]/<Height of cylinder>: 265
Command: '_PMTHIST
Command: LI
------------------------ 3DSOLID ----------------------------------
Handle: 5D1
Current space: Model space
Layer: 0
Color: BYLAYER
Linetype: BYLAYER
Line weight: BYLAYER
History: Record
Show History: No
Bounding Box:
Lower Bound: X = -14.6 Y = -14.6 Z = 0
Upper Bound: X = 14.6 Y = 14.6 Z = 265
CMS INTELLICAD 13.0.737.158051.PE+.VC17.x64.CMS130

i9-12900k / 64gb-3200 - NVIDIA GeForce TRX 3060 Ti 8Gb Windows 11 Pro

Re: Changes to 12.1 causes issues with relative/absolute inputs.

#4 by sln8458
QuanNguyen wrote: ↑
Thu Apr 04, 2024 9:14 pm
 Hi Steven,
Maybe the issue is due to using commands in the lisp routine.
Try to turn off the Snap before calling any commands.
Regards.
Hi Quan,
Thanks, but I have tried that both in the code and manully via setting.

I have noticed this morning that using:
(setvar "OSMODE" 0)
.....
(setvar "OSMODE" 7)

Has NO effect on tha snaps shown in the snaps toolbar on the side of my screen!!?
CMS INTELLICAD 13.0.737.158051.PE+.VC17.x64.CMS130

i9-12900k / 64gb-3200 - NVIDIA GeForce TRX 3060 Ti 8Gb Windows 11 Pro
Attachments
snaps.jpg
snaps.jpg (159.54 KiB) Viewed 1329 times

Re: Changes to 12.1 causes issues with relative/absolute inputs.

#5 by sln8458
I have solved the problem :)
Quan was correct :wink:

I found an additional OSMODE statement (instruction) within my code which I had forgotten about which was overighting the changes I was trying to make.
This was also impacting my manual changes via settings.

Thanks to Quan, I re-checked this morning and found my earlier error, though I'm not sure why this did not surface in 12.0 but solved now.
CMS INTELLICAD 13.0.737.158051.PE+.VC17.x64.CMS130

i9-12900k / 64gb-3200 - NVIDIA GeForce TRX 3060 Ti 8Gb Windows 11 Pro

Re: Changes to 12.1 causes issues with relative/absolute inputs.

#6 by tetroupsa
sln8458 wrote: ↑
Thu Apr 04, 2024 1:03 am
What has changed between 12.0 and 12.1?

While my problem is highlighted in my piping lsp add-on, the issue is NOT lisp related I believe.

Here I have created a line from 0,100,0 to 100,0,0 via lsp, but when I 'list' the line it is not from/to these co-ordinates.
Command: _line doodle jump
ENTER to use last point/[Follow]/<Start of line>: 0,100,0
[Angle/Length]/<End point>: @100,0,0
[Angle/Length/Follow/Undo]/<End point>:
Command:
Opposite corner:
Command: _ERASE
1 found
Command:
Opposite corner:
Command: LI
--------------------------- LINE ----------------------------------
Handle: 67B
Current space: Model space
Layer: 0
Color: BYLAYER
Linetype: BYLAYER
Line weight: BYLAYER
From point: X = 0 Y = 0 Z = 0
To point: X = 100 Y = 0 Z = 0
Length: 100
Angle in UCS XY plane: 0
Delta values: X = 100 Y = 0 Z = 0
Anyone have a clue why this is??
To troubleshoot, try switching to a different UCS or explicitly set the UCS to match your desired coordinates before drawing the line. You could also check if any settings or preferences were altered in version 12.1 that affect how coordinates are interpreted. If the problem persists, consider reaching out to CMS for further support regarding this behavior.

Latest Posts
Post Reply

Return to “General”