BMS 4.33 crashes if I change my pilot profile

[AlphaCharlie]

Hi everyone.

I haven’t simmed in a long time, but decided to get back into it. The F16 has always been my favourite plane since Strike Commander, and later, Falcon 4. I have purchased an X52 Pro, and while I am waiting for it to arrive and have been practising ramp starts. I discovered an unusual issue yesterday. If I use the “Joe Pilot” Callsign: Viper profile, everything is fine. If, however, I edit the profile to my own name and call sign, the sim crashes when it hits the 3rd progress block in the loading screen.

How do I create a new profile?

Thanks - AC

[AlphaCharlie]

Just read a sticky about call signs needing to be < 12 characters. Mine is exactly 12, so I will check it again tonight.

Cheers - AC

[CobaltUK]

You might want to start reading in the saitek section whilst waiting for stick. A few hints/tips and problem solutions there.

[Frederf]

Logbook profiles are determined by the callsign name. The NEW button always creates a callsign “Viper”. Viper should not be used but instead left as a blank template. Creating a new logbook should be done by taking the Viper logbook and renaming it as desired. Then press the NEW button to create another starter Viper. The logbook list should be all the callsigns you use plus a blank Viper.

Be aware that logbook selection affects a lot more than just your pilot name:
Graphical settings
Audio settings
Controls
Data cartridge file
Key file
Difficulty

Does a callsign “test” logbook crash? Let’s try to figure out if it’s crashing on any non-Viper logbook or just the callsign that you’ve chosen in particular. If Viper works but Test doesn’t, look for the differences between them in settings.

[AlphaCharlie]

@Frederf:

Logbook profiles are determined by the callsign name. The NEW button always creates a callsign “Viper”. Viper should not be used but instead left as a blank template. Creating a new logbook should be done by taking the Viper logbook and renaming it as desired. Then press the NEW button to create another starter Viper. The logbook list should be all the callsigns you use plus a blank Viper.

Do you mean copy and rename in the file system, or in the sim?

Thanks - AC

[Frederf]

In the sim. There are various links to the logbook scattered throughout the UI but I’d use the one on the main menu, works more reliably.

Just copying and renaming files in the directory is probably a fast way to get crashes. If it’s not plain text like the DTC (callsign .ini) best not be doing stuff like that.

[AlphaCharlie]

SOLVED.
It was just that particular callsign, (AlphaCharlie), which is 12 chars, so quite possibly the issue mentioned in the sticky.

Thanks for the help.

AC

[AlphaCharlie]

*** UPDATE ***
I finally managed to upgrade to 4.33 U3 with a lot of manual effort - no matter what folder I selected, the setup would not run, nor would the updates end up in the correct spot, but that’s another story, I guess. Anyway, the upshot is, that my AlphaCharlie call sign works just fine on U3.

Thanks - AC