The behavior you are seeing is by design. From the comment header in
XR2RavenstarPrefs.cfg:
#--------------------------------------------------------------------------
# Define the default name, age, pulse, mass, rank, and mesh of all crew members.
# If a scenario does not contain UMmu data for passengers, the values below are used.
In other words, the values in the config file are
default values that are used
only when no UMMU scenario data is present; e.g., when the ship is spawned via the scenario editor as TS said. If you are loading a scenario and there is valid UMMU data in the scenario, the UMMU data in the scenario is used; otherwise, any crew member changes you made via ingress or egress would be lost when you saved and reloaded the scenario (this behavior is the same as any other UMMU-enabled vessel). If you want to change the UMMU names in a given scenario, edit the UMMU data in the scenario file:
Code:
UMMUCREW XI0-Lee_Nash-39-65-78
UMMUCREW XI1-Kara_Miller-32-65-58
UMMUCREW XI2-Sharon_Valerii-26-67-54
UMMUCREW XI3-Cameron_Mitchell-36-65-77
UMMUCREW XI4-Samantha_Carter-33-66-53
UMMUCREW XI5-Daniel_Jackson-35-68-75
UMMUCREW XI6-Teal_c-31-64-104
UMMUCREW XI7-Vala_Mal_Doran-30-67-53
UMMUCREW XI8-Elizabeth_Weir-36-68-56
UMMUCREW XI9-John_Sheppard-34-64-77
UMMUCREW XI10-Rodney_McKay-35-72-90
UMMUCREW XI11-Teyla_Emmagan-27-68-57
UMMUCREW XI12-Ronon_Dex-32-63-97
UMMUCREW XI13-Carson_Beckett-38-74-95
The order is tag-name-age-pulse rate-mass (do not change the tag values). If you set 'XRUMMU_CREW_DATA_VALID 0' or delete that line the default UMMU data defined in the config file is used (since no UMMU data is available in the scenario in that case). However, UMMU data is always saved with the scenario, so the correct thing to do is edit the UMMU data in the scenario.