Is there a "best practices" standard for using motor adapters in OpenRocket?
1. Ignore it: I can select and sim smaller motors and just ignore the missing mass of the adapter and precise location of the motor. How much does this affect sim accuracy?
2. Separate rocket files for with or without adapter. Accurate, but what a pain! It's harder to compare simulations, and if you change the rocket design at all you have to update every file.
3. Motor files for motors with adapters. I like this solution, but each different adapter would need its own set of motor files. That could end up being a whole lot of data to sort through to find the motors you want! Plus if you design and make your own adapter, you'd need to make your own set of motor files...
What's the "best" approach? Is there a built-in capability I don't know about? Has anyone already made motor files with adapters?
1. Ignore it: I can select and sim smaller motors and just ignore the missing mass of the adapter and precise location of the motor. How much does this affect sim accuracy?
2. Separate rocket files for with or without adapter. Accurate, but what a pain! It's harder to compare simulations, and if you change the rocket design at all you have to update every file.
3. Motor files for motors with adapters. I like this solution, but each different adapter would need its own set of motor files. That could end up being a whole lot of data to sort through to find the motors you want! Plus if you design and make your own adapter, you'd need to make your own set of motor files...
What's the "best" approach? Is there a built-in capability I don't know about? Has anyone already made motor files with adapters?