Hi,
I am having problem with the component “FEM-Design.Connection” . Not really sure what is going on here…? It is connected exactly like your live link example.
Also tried to use the actual example files from : https://www.youtube.com/watch?v=XyC6oldJFiU and from: https://www.youtube.com/watch?v=GEcWkDzyQkY
Same issue, also tried to connect boolean toggle. I have installed FEM 2020-2023 and using Rhino 7.
Hi @erikaj87
It looks like that you have saved the file in a folder which has some ASCII characters and they are not currently supported.
In order to fix the issue, connect OutputDir using the following method:
C:\tempIn this way, FEM-Design API will create the text file to comunicate with the software.
Excellent, thank you that solved the issue 
Next question. I don’t get my analysis to show up in FEM with the 3D Truss script that I have received from the YT-clip " How to get started with parametric design in your everyday structural engineering work"
I had to update some of the components to latest version, but everything else exactly the same as the provided file.
This is what I get in analysis:
I could send the file if that would make it easier? since I cannot upload here as new user.
Try to share the file now 
I have changed the settings and it should be now possible.
Excellent!
I also tried some other files that I downloaded from the other YT clip " Rhino User Webinar: Next-level workflows for structural engineers with Grasshopper and FEM-Design" that you also attended. Exactly the same issue, the results are missing and same for my co-worker on her computer.
3D Truss Test.gh (33.9 KB)
Hi @erikaj87
A bug has been introduced in FEM-Design API 23.2.0 and, therefore, the script was failing to run the analysis.
For the time being, you can solve the issue specifying comb and combSettings. I have attached a revised script that show you how to solve the issue
However, in the next release, you can just run the analysis as you have done!
3D Truss Test_Rev_MP.gh (40.2 KB)
Great, it is working now with that solution! Thank you so much for your prompt support and reply!
Good luck then! 
Make sure to open new thread for questions which are not related to each others
It will help other people in solving the issue.
Hi @erikaj87! 
The character encoding issue with directory names for the API files has been resolved. Starting with our next release (v23.3.0), we will be able to use an extended ASCII character set called UTF-8. This will allow you to use a wide range of special characters for your directory names in the future. 
