Are you using a scenario with just the Cargodragon2 and Cargo2Trunk ?Thanks, now it's fine! In the log is still an unspecified mesh error but it doesn't bother.
============================ ERROR: ===========================
Mesh not found: .\Meshes\.msh
[LoadMesh | .\Mesh.cpp | 1269]
No, the mesh error occurs twice with your test-scenario 'CargoDragon2 with Bishop Airlock.scn'. When I remove BATruss and BishopAirlock from this scenario and have only CargoDragon2 and Cargo2trunk in it, the two mesh errors aren't in the log file.Are you using a scenario with just the Cargodragon2 and Cargo2Trunk ?
I tested this already. It's the same with your scenario 'CD2 launch to ISS.scn': With BATruss and BishopAirlock the two mesh errors appear, without both modules in the scenario the mesh errors are gone. But everything works anyway.Would you try the Launch scenario. Let me know if that works.
Ok, when I set 'THGROUP_MAIN = FALSE' or let it TRUE with 'THGROUP_MAIN_THRUSTERS = 1' (change from -1) it works. Which solution is the right one? There is no change in the "Bishop Airlock(1).zip" yet.That's because I deleted the Mains from the thrust group. You can go in and undefine the Main thrust group or redownload.