Weber

Hello CJ Coll, The Argument set-up looks correct, as does the executable path. At this point, I would need to see your local folder and macro file in order to help you in this specific case. But I could give you some advice, how I would troubleshoot the problem: - Store all the input files (.stl, .sim and .java) in the same location as the CAESES project file. - In the macro file, you can then just use the name of your input stl file instead of referencing the absolute path, like in this case it would just be "basis...4.stl" - Try to avoid spaces when naming objects, since this can lead to errors sometimes (e.g. "Original HPW 30-01-24.sim")

Hello CJ Coll, If you already imported the simfile into the connector by referencing the absolute path from it inside the window "Filename", you don't need to add the absolute path anymore inside the argument. If "Original HPW 30-01-24.sim" is your simfile you would just need to add: "/Original HPW 30-01-24.sim" after "getResultsDir() +", since it copies the simfile into the connector folder when importing it. I hope this helps. Best regards, Johannes

Hello CJ Coll, It seems that there is a problem with the Argument and its order inside your Connector. First, I would check, if your simfile from StarCCM+ is located in the same location as your CAESES project file. Afterwards, import the setup file into your Input Files Window and double-click on it to directly import it into your connector. Now, you should have the possibility to edit the java file also in CAESES directly. Then, you can import the simfile and reference the absolute path inside window "Filename". Please use quotation-marks when adding a path as an argument: "-----your-path----". After this is done, you can use following argument as the Connector's Argument: "-batch ----your-setup-file----.java -np 2 -rsh ssh -power -licpath 1999@flex.cd-adapco.com -podkey ----your-podkey---- " + getResultsDir() + "/----your-sim-file----.sim" I hope that will help you with the issue. If not, don't hesitate to ask further questions. Best regards, Johannes

Hi CJ Coll, Apologies for the late response. I would simply import the edited feature definition via "Import Definition" which is located in the "Features" section in the Model Workspace. After the import, you can right-click on the feature and select "Create Feature" to create a feature in the object tree. To view and edit the feature, double-click on the feature inside the "Features" section. To locate commands inside a feature, you can use the searching command (Ctrl+f). You can find the commands in the lines 30,35 and 40 and just change the input from "false" to "true" in order to make the objects visible. I hope that answers your questions. Best regards, Johannes

Hi CJ Coll, I edited the feature so that the labels are not on top of each other anymore and the points are removed inside the profile view. You can find the edited linesplan feature attached to this reply. To toggle the visibilty of the orientation points from the group section curves, you can use the command .setShowOrientation(true/false). If you want to further edit the feature yourself, you can access the it in your CAESES installation directory under "CAESES...\etc\features\features\Maritime". To add a line that follows the topdeck, my solution was to create an image curve from the hull's surface/brep upper edge. I hope that solves your problem. If not, don't hesitate to ask. Linesplan_edited.fde