Settings screen

[marloscaida]

At the moment when I was changing the configuration, pressing one of the checkboxes caused the simulator (XP12) to crash. The log.txt file shows the following: 0:16:49.610 I/OVR: User is entering the holodeck. 0:16:49.610 I/WIN: Opened window Settings 0:17:28.430 I/OVR: User is leaving the holodeck. --=={This application has crashed!}==-- (Art controls are modified.)

I'm going to try again to see if I can reproduce the error and be more specific. Before I am going to use the plugin with the default configuration

Thank you very much for your excellent work and one of the most useful additions of XP

[marloscaida]

BP works normally with its default settings. The problem occurs when I try to change to the Spanish language. A poster also appeared whose capture I attach. Regards carlos

[marloscaida]

In version 0.50 there is no longer a crash but the default configuration is maintained, without changing the language or any other parameter. The good thing is that there is no crash! We are advancing.

[marloscaida]

In version 0.51 three problems still occur: 1.- When trying to change the configuration, the simulator hangs, generating the report for X-plane. 2.- Does not take configuration changes. That is, it continues with the initial configuration, without the possibility of changing the language. 3.- It does not detect the language of the country of the airport, to change it automatically.

In conclusion, the configuration screen is inoperative.

Regards carlos

[acaproni]

Same issue here with the latest version of BP. From the logs at startup, BP tries to read the configuration but it fails. Everything work properly but changing the configuration from the BP option panel does not work. In my case XP hangs for a while then resume but the configuration is not stored.

For home cockpit it is a big problem as the default configuration forces the user to press the disconnect button at the end of the push back. But the user of an home cockpit does not a have a mouse at his hand.

An acceptable workaround would be to know the format of the configuration file and edit by hand but I have not found any documentation.

[acaproni]

I played a bit and found that if the BetterPushback.cfg is written with notepad then pushback takes the properties. In my case I wrote

disco_when_done = 1

in BetterPushback.cfg and it solved the problem of my previous comment.

Saving the configuration from XP does not work but reading works well.