Subassembly composer: compiler error processing expression...

Subassembly composer: compiler error processing expression...

Buzz0m
Collaborator Collaborator
977 Views
6 Replies
Message 1 of 7

Subassembly composer: compiler error processing expression...

Buzz0m
Collaborator
Collaborator

Hi,

my team member is working on a subassembly and we have run into an issue I can't solve. Basically subassembly composer runs into some kind of error and is unable to resolve the error and seems to completely corrupts the .pkt file or at least all intelligent definitions. The symptom is that when trying to input formulas into the geometry definition fields (e.g. delta x and delta y) there is an compiler error (see pic). Is this a know issue and what can we do to prevent or solve this?
2023-11-20 SAC issue.png

As far as I can tell there isn't a typo and according to the author this isn't the first time the issue rises.

 

I would have posted the .pkt file as well but I can't see a way to work around the forum attachment restrictions. We are using civil3d 2022 and 2024.

0 Likes
Accepted solutions (1)
978 Views
6 Replies
Replies (6)
Message 2 of 7

CharlieGreene7827
Advocate
Advocate

I think it is because you are using distance to, from point, to an auxiliary point, as they are 2 different types of point DistanceTo wont work, try a auxiliary link between the 2 points and link length, or use an auxiliary point in the same position as P2

0 Likes
Message 3 of 7

CharlieGreene7827
Advocate
Advocate

Just tried it, and it works, I am assuming you are using a decision, without being able to look at you pkt file if difficult to tell, try zipping up the file that used to work, another thing to try is cut out the expression, write one that works to get rid of the error then repaste the original,

 

CharlieGreene7827_0-1700579593407.jpeg

 

0 Likes
Message 4 of 7

Buzz0m
Collaborator
Collaborator

Thanks for your troubleshooting efforts! And confirming that there isn't an issue with the formula in itself.

I'm trying to attach the pkt-file now again. I just changed the file extension from .pkt to .zip. Let's see if that works.

0 Likes
Message 5 of 7

CharlieGreene7827
Advocate
Advocate
Accepted solution

i think my first suspission seemed correct DistanceTo from a normal point didnt work, I added an auxiliary point AP26 before P2, with the same criteria, and used that in decission, Test it and let me know if this solves the issue

Screenshot 2023-11-22 120228.jpg

Screenshot 2023-11-22 120251.jpg

 

0 Likes
Message 6 of 7

Buzz0m
Collaborator
Collaborator

Thank you! It seems like a bug or lacking feature that the classes point and auxiliary point can't be used together in the "DistanceTo" function(?)! What could be the reason they can't be used together? -> this lead me to test this with a totally new file and there the cross usage of P and  AP in distanceTo is not an issue! Also i tested that if the problem has to do with the geometry definition being in different "flowcharts" but that didn't matter.

As a side note: I also tried the "SlopeTo" function but in SAC2024 with the subassembly I posted and I couldn't get that to work even by using only point object references. Even though @CharlieGreene7827 solved the problem I am still prone to believe there is some kind of corruption or file format mismatch happening. It is possible, that the original pkt-file has been developed with c3dSAC 2020 and might not be fully compatible with newer versions(?)! Any more insight is appreciated!

0 Likes
Message 7 of 7

CharlieGreene7827
Advocate
Advocate

Not sure why it will work somtimes and not others, thats why I sugested cutting out the expression replacing with any thing that works to clear the error then replacing the original expression. Glad it worked

0 Likes