Closed technicbasics closed 1 year ago
Thank you for reporting this behaviour.
FYI, there are several significant updates (some in progress) in the latest DevOps build.
Was this behaviour present before the DevOps r166 release ?
Cheers,
Hi Trevor No, just since r166
Addendum: Only the step number problem has been present since r166. The NOSTEP problem was also present earlier.
After adding a "0 !LPUB NOSTEP" command in a callout of a submodel, the step number show "-1".
This behaviour has been corrected.
Another problem is, if a "0 !LPUB NOSTEP" command is in a submodel, and you want to convert it in a callout, LPub3D crash.
This behaviour has its own ticket - #706.
Cheers,
Subject
After adding a "0 !LPUB NOSTEP" command in a callout of a submodel, the step number show "-1". Here is a picture with a callout with "NOSTEP" (left), and one without. (right)![2023-04-20 21_55_55-](https://user-images.githubusercontent.com/49073781/233476676-3ab45342-1239-4086-b3b4-7bc44c54539b.png)
Another problem is, if a "0 !LPUB NOSTEP" command is in a submodel, an you want to convert it in a callout, LPub3D crash. This may be associated with this error message if you use the command in combination with a buffer exchange as I like to do. See Command window in the picture above.
Environment