Having the same issue myself, has there been a resolution yet?

I guess its a mistake in the both bat-files...try to delete all before "Program\..." and safe..think it will work then

The `.bat` files haven't changed in 0.8.0. They both just call the .exe to tell it to run its install/uninstall logic.

For those of you where the installation is failing, can you tell me the path you're running from? The installation code hasn't changed in 0.8.0.

(I have just spotted an error where it'll probably fail if you have spaces in the path name, which is a bit of a schoolboy error, but that problem was there in all previous versions. I'll ship a quick fix for that. The .bat files are going away soon and will be replaced with a first-class installer.)

I lied. 😞 The installation script did change in 0.8.0 after somebody reported a problem when they ran the installation as administrator (which isn't necessary). Fixing that required making the path explicit, but I screwed that up so that an installation from a path with spaces in it no longer worked. That's an embarrassingly stupid schoolboy error and I should know better - apologies!

I've just released 0.8.1 which fixes the install.bat + uninstall.bat scripts. You don't need to uninstall an old version: just install the new version. It also includes more PMDG 737 configuration and new features in the variables list.

Apologies again - thanks for letting me know about the problem!

No worries at all. Appreciate the quick fix. To confirm I do have a space in my main add-on folder. Thanks again for this awesome product.

Thanks for the update, I'm glad to hear you are working on it, I'm really grateful for your work, it makes using the Bravo so much better. I was able to purchase the plane before the store went down and have been experimenting a bit, but also getting constant CTD if I try to use the Variable List. Lmk if I can help. Thank you!

Thanks. Yes, I got some CTDs earlier off the variable list. There seems to be an issue with reading very large numbers of A: variables. If you clear out the KnownSimVars.csv file it'll use only L: variables, which are completely stable (and more interesting for the PMDG 737!). It's definitely an experimental UI right now, hence all the disclaimers! 😉

I'm collecting bits of configuration here:

https://github.com/RoystonS/BetterBravoLights/issues/39

So far I have all the autopilot lights and the doors figured out. The rest of the lights are proving a little elusive.

Thank you!

Btw, looks like Microsoft have fixed the CTD issue. The Variable list looks stable again after the last post-SU9 patch released today.

Some PMDG 737 settings shipped in the 0.8.0 release of BBL but I've got some more settings since, which I'm collecting here if you're interested: https://github.com/RoystonS/BetterBravoLights/issues/44

sorry , it is not lightbulb in the system tray. if i start the BetterBravoLights.exes it shows short a lightbulb and the app it is running but not a lightbulb in the system tray.

Ok, so you're seeing the splash screen when the program starts up. That's a good sign, as it means the program is able to run. After it has shown that splash screen for a few seconds the program will shift into the background and it'll put a lightbulb icon in the system tray so that you can still interact with it. Something has gone very wrong if that system tray icon isn't there. I've not heard of that before.

So, can I ask: have you checked your system tray's overflow menu? Windows might not show all the system tray icons if you have more than a couple of them, and will move some of them into a separate dropdown. (I have 25 system tray icons in the overflow menu on my computer.)

thanks for answhere

thanks for the answer. i found it now it is hidden on the right side of the taskbar. just tried it. after opening the "better bravo lights variable list" crash to desktop cdt.

but it is there now thank you very much

It made no difference. It's still totally random if it works or not when loading up the game. Same issue with the original software from Aerosoft as well. I have no clue what the issue could be.

Would you mind raising an issue on GitHub so I can look into it in more detail?

https://github.com/RoystonS/BetterBravoLights/issues/new/choose

It would be extremely helpful to see the contents of your `exe.xml` file, which is at

USER/AppData/Roaming/Microsoft Flight Simulator

if you have the Steam MSFS

or

USER/AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

if you have the Windows Store MSFS

That exe.xml file controls the program which MSFS runs at startup, and if something has corrupted it (and some software out there is going round accidentally corrupting it), it'll break.

The other possibility is that BBL isn't exiting properly so then doesn't start up again properly, but as you're saying you're seeing the same issue with the Aerosoft software I'd really like to see your exe.xml file.

Had an issue with my pc today and lost all my files. Will have to reinstall everything and knowing microsoft download speeds it will take probably 2 days to reinstall MSFS. If a clean install doesn't fix the issue I've been having, I'll upload the file as you requested.

I've just released BBL v0.8.0. Whilst it doesn't - and can't - stop other installers from breaking the file that controls which programs MSFS starts up, manually running BBL will now tell you whether something has broken the startup, and offer fix suggestions.

Hiya. I've just released BBL v0.8.0. In that I've rewritten the logic used to detect when MSFS has exited, as the MSFS API isn't reliable, as you've found. It should now exit much more reliably.

Fantastic. Thankyou!

Btw, did you figure out the change for the LowVolts light for your JF PA28?

If so, it would be great to share it with others. If not, would you like a hand figuring it out?

I haven't had chance yet but will try and take a look soon. If I can do it I'll certainly share it. If not I'll come back and seek help 😊

it seems i just have to run the exe every time manually now

That's strange. If you've installed other tools recently it's quite possible that once of those has broken the file that MSFS uses to start programs up. Try rerunning the BetterBravoLights install and it'll ensure that file is correct, or tell you about the problem.

I've just released BBL v0.8.0. Whilst it doesn't - and can't - stop other installers from breaking the file that controls which programs MSFS starts up, manually running BBL will now tell you whether something has broken the startup, and offer fix suggestions.

I don’t have this mod and I also have the inability to add

I have notice, to be honest, that this bug is not related to Better Bravo Light. When you have this problem try to change the aircraft with another once. Sometimes it resolve the issue. But i am not sure if it function all the time

Thanks for the update. I'll close the GitHub issue.

Thanks, I did it (and some other lines, I know the FBW document), but it didn´t work.

Strange: HDG + VS are always illuminated, and all other are allways dark.

I use a lot of FBW variables with FCUIPC7, but I don´t find the right one for BBL.

https://docs.flybywiresim.com/pilots-corner/a32nx-briefing/a32nx_api

But I don´t give up, one day I´ll find the variable.

[EDIT] > Solved

Thanks works fine now, I hardly dare to say it, but it was my mistake: typo in the command line

My Config.ini

[Aircraft.FlyByWire_A320_NEO]

HDG = L:A32NX_FCU_HDG_MANAGED_DASHES == 1

NAV = L:XMLVAR_Baro1_Mode == 1

APR = L:A32NX_FCU_APPR_MODE_ACTIVE == 1

REV = L:XMLVAR_Baro1_Mode == 2

ALT = A:AUTOPILOT ALTITUDE SLOT INDEX, bool == 2

VS = L:A32NX_AUTOPILOT_VS_SELECTED == 0

IAS = L:A32NX_FCU_SPD_MANAGED_DASHES == 1

Remark: I never used NAV/REV, so I set the lights to show me the BARO status 1013 (NAV) or local (REV)

I have always exited using the Quit to Desktop option. I tested a couple times and BBL closed correctly today. So now I'm confused ha. But I will continue to monitor and report if it hangs up again. Thanks for your response.

FS2 Crew seems to be a payware module. I don't have it right now, so if you could provide some info on how it conflicts, I'd like to try to diagnose the issue. BBL should be completely independent of anything else so I'm a little lost as to what sort of conflict could occur.

FS2Crew have an app that auto loads as FS2020 loads, 'FS2CrewCommandCente', this has to remain open for FS2Crew FWB and pushback express to work.

As soon as I installed better bravo lights FS2 Crew threw an error saying the WASM module was corrupt. I immediately uninstalled Better bravo lights and the FS2crew error was resolved. so I'm assuming thats what caused the conflict?

Interesting. So it's the FS2Crew command centre app that's complaining about a corrupt WASM?

I can see some entries on the FS2Crew troubleshooting page about a WASM error, and also about a log file: https://fs2crew.com/fs2crew-command-center-troubleshooting/

Are there any more details accompanying the 'Corrupt WASM' message? (Any error codes might be helpful) and is there anything in the log file from around that time?