roystons / betterbravolights Goto Github PK

Software version
0.1.0

Is your feature request related to a problem? Please describe.
Whilst there's a list of A: vars, L: vars are very aircraft-specific, and so without a list of available L: vars it can be hard to figure out how to map values for a particular light.

Describe the solution you'd like
Some part of the UI should offer up a list of the available L: vars for the current aircraft.

Describe alternatives you've considered
Not really any alternative. The L: vars change over time.

Alpha

**Is your feature request related to a problem? Please describe. No

**Describe the solution you'd like See above

Haven't figured out how to do this myself yet.

Additional context

Software version
0.6.0

Is your feature request related to a problem? Please describe.

Hi @RoystonS It is me again, I was flying today and I realised that FBW team changed some LVars again, I am talking about pressure LVars, the ones you have by default config (L:A32NX_HYD_BLUE_PRESSURE < 2000 OR L:A32NX_HYD_GREEN_PRESSURE < 2000 OR L:A32NX_HYD_YELLOW_PRESSURE < 2000) do not longer exist.

Describe the solution you'd like

The new LVars are:

LowHydPressure = L:A32NX_HYD_BLUE_SYSTEM_1_SECTION_PRESSURE < 2000 OR L:A32NX_HYD_GREEN_SYSTEM_1_SECTION_PRESSURE < 2000 OR L:A32NX_HYD_YELLOW_SYSTEM_1_SECTION_PRESSURE < 2000

Describe alternatives you've considered

There are also this variables:

L:A32NX_HYD_BLUE_PUMP_1_SECTION_PRESSURE and same for green and yellow systems, but I am not sure yet wich ones are correct. I have already changed them in my config file (the ones in "describe the solution you would like" section) and it seems to me they are working like the previous ones.

Additional context

The rest of the lights seem to be working just like before.

Software version
0.6.0

Problem
BetterBravoLights refused to install because my exe.xml file is corrupt.

My exe.xml file is located at
C:\Users\fred\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml

The error reported was

Unexpected end tag. Line 2, position 3.

The contents of the exe.xml file are as follows:

<?xml version="1.0" encoding="Windows-1252"?>
</SimBase.Document>

I understand that BetterBravoLights didn't corrupt the file and that it's simply warning
about the corrupted file. But could you help me fix it?

Several users on flightsim.to have reported that 'after a while' BBL no longer starts up with MSFS.

This will likely be for one of two reasons:

1. User has moved the BBL installation, so MSFS is trying to start it up but can't find it.
2. Some other tool installed since BBL was installed has trashed the exe.xml which means that BBL and other programs won't start up correctly.

None of the reports so far have suggested the first cause; others have suggested other applications are also failing to start up, suggesting that we have a situation where something else is corrupting the exe.xml file.

We check and report on the exe.xml file when attempting to install, and users have managed to fix the problem by reinstalling or manually running BBL every time. We should check on all startups: if BBL looks like it's supposed to be installed but the exe.xml file is corrupt, warn the user.

Software version

0.8.0

What are you trying to do?

Loading BBL 0.81 / exe. xml

What's the problem?

Hi,

my exe.xml doen't load after updatng it with/to work with BBL 0.81. exe.xml is - of cours
EXExml.txt
e renamed to EXExml.txt attached.

Would be fine if you woould find the time to look over it...

regards,
Martin

What have you tried already?

Correct location of exe.xml: Checked. OK

Correct xml syntax: Checked (as far as I can tell...) OK?

Manually starting the entries in exe.xml: Checked. OK

Other information

No response

Is your feature request related to a problem? Please describe.

If lvars aren't working properly, Better Bravo Lights doesn't report the problem very obviously.

Describe the solution you'd like

BBL should indicate more clearly whether lvars are working, and which lights are affected by an lvar issue.

With the FSUIPC API being used right now, we're simply given the value 0 if FSUIPC isn't installed or configured correctly. This isn't very helpful.

There is another FSUIPCClient API that allows us to get notifications about lvar values changing, and the known list of lvars. This would enable us to discover whether lvars are working properly, and read them more efficiently, and provide a visual list of lvars and their values to help with expression building (see #5).

Software version
0.6.0

Is your feature request related to a problem? Please describe.
The default Honeycomb driver disables the lights until power is available, this is not present in BetterBravoLights.

Describe the solution you'd like
A "master toggle" option of some kind that would disable all the lights for a given condition. The Honeycomb configuration appears to be when A:ELECTRICAL MAIN BUS AMPS == 0

Describe alternatives you've considered
Adding an AND condition to each individual configuration with A:ELECTRICAL MAIN BUS AMPS > 0

Software version

0.7.0

Request

The PMDG 737 is now out, and people will be wanting configuration for it. Let's get it figured out.

Config so far:

Autopilot lights confirmed working:

[Aircraft.PMDG 737-700, Aircraft.PMDG 737-700BDSF, Aircraft.PMDG 737-700BBJ]
HDG = L:ngx_MCP_HdgSel > 0
NAV = L:ngx_MCP_LNav > 0
APR = L:ngx_MCP_App > 0
ALT = L:ngx_MCP_AltHold > 0
VS = L:ngx_MCP_VS > 0
IAS = L:ngx_MCP_LvlChg > 0
AUTOPILOT = L:ngx_MCP_CMDA > 0 OR L:ngx_MCP_CMDB > 0

Other lights confirmed:

Door = L:FwdLwrCargoDoor > 0 OR L:AftLwrCargoDoor > 0 OR L:FwdLeftCabinDoor > 0 OR L:FwdRightCabinDoor > 0 OR L:AftLeftCabinDoor > 0 OR L:AftRightCabinDoor > 0 OR L:OverwingFwdLeftEmerExit > 0 OR L:OverwingFwdRightEmerExit > 0 OR L:OverwingAftLeftEmerExit > 0 OR L:OverwingAftRightEmerExit > 0 OR L:EEDoor > 0 OR L:AirStairs > 0

Standard configurations which are working out of the box:

• Parking Brake

Suspected but unconfirmed:

EngineFire = L:NGXLeftEngineSmoke > 0 OR L:NGXRightEngineSmoke > 0

Other:

• AntiIce has a first-class annunciator in the cabin, but no LVar or AVar seems to map to it. :-(
• No sign of LVars (not even the standard MS one) for master caution or master warning. :-(
• ELECTRICAL MAIN BUS VOLTAGE seems to be 115V when running (i.e. main AC voltage), so the standard < 26V option will need changing

Describe the solution you'd like

It'd probably be nice to be able to configure both steady lamp lightings and blinking lamp lightings. For example, slightly low oil pressure might cause a light to light up but VERY low oil pressure might cause it to blink. (e.g. existing differences between warning and caution annunciators.)

Describe alternatives you've considered

We already do have some blinking light support in the cases where we're mapping a light to a sim variable that itself blinks. For example, the Hawk in MSFS and the A10C in DCS both have annunciators that naturally blink, causing BetterBravoLights to do light-blinking already.

But there will be cases where we're not mapping to existing annunciator lights. For example, in the G1000 both 'warning' and 'caution' lights are defined, sometimes for the same conditions but different levels of severity.

Additional context
Need to be very careful with this. Because of epilepsy triggers we might want to make blinking lights an opt-in feature.

Thanks to @jcabanascachi for the suggestion at #14 (comment)!

Software version
0.6.0

Describe the bug

When I run install.bat I get the following:-

Little Box Entitled Better Bravo Lights with a red cross in it and the text "Operation failed. System.NullReferenceException:Object Reference not ret to an instance of an object. Please report this to the application author.
The Box only had an OK button, which when pressed gets rid of the command prompt that was running the program.

To reproduce

Run install.bat again

• MSFS: Windows Steam Edition

If I'm firing up a new aircraft it's hard to know what to expect from BBL. If it has no specific configuration for that aircraft I'm probably only going to get a handful of lights working - at best, and that's assuming that the aircraft creator hasn't simply ignored all the standard variables and replaced them with their own custom LVars.

So, in that situation it would be nice if BBL could just give a quiet, polite little message to tell the user that they're going to be running with reduced lights functionality for such an aircraft, either to reduce expectations or perhaps inspire the user to develop and configuration.

Problems

This might, however, be rather tricky, as there doesn't appear to be a standard API for simply sticking a bit of text on the screen.

• Yes, I could use a panel but that's VERY heavyweight.
• SimConnect_Text apparently hasn't worked since SU5.

The parser doesn't currently support unary minus, e.g. -4. It's easy to work around, by writing 0 - 4 but it's a bit rubbish not being able to write negative numbers directly.

Software version

0.8.2

Location of my exe.xml file

C:\Users\cigay\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml

Contents of my exe.xml file

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
	<Descr>Launch</Descr>
	<Filename>exe.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Name>FenixA320</Name>
		<Disabled>False</Disabled>
		<Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
</SimBase.Document>

The installation error

The 'Launch.Addon' start tag on line 7 position 3 does not match the end tag of 'SimBase.Document'. Line 11, position 3.

Software version

0.8.1

What are you trying to do?

I'm trying to map the Door light from the Bravo to the custom L:vars of the NextGen EMB110

What's the problem?

BBL is giving the error 'A boolean expression is needed to drive a light, not a numeric one.' Thus no light can be driven.

What have you tried already?

(L:EMB110P1 CARGO DOOR OPEN > 0) OR (L:EMB110P1 MAIN DOOR OPEN > 0)
(L:EMB110P1 CARGO DOOR OPEN, bool > 0) OR (L:EMB110P1 MAIN DOOR OPEN, bool > 0)
L:EMB110P1 CARGO DOOR OPEN > 0 OR L:EMB110P1 MAIN DOOR OPEN > 0
L:EMB110P1 CARGO DOOR OPEN == 1 OR L:EMB110P1 MAIN DOOR OPEN == 1
(L:EMB110P1 CARGO DOOR OPEN, percent > 0) OR (L:EMB110P1 MAIN DOOR OPEN, percent > 0)

None of these work

Other information

No response

Software version

0.8.0

Problem

Some users are unpacking the zip, installing the software, and then not realising that they need to keep the unpacked zip file. If we move to a real installer instead of a zip, we can copy the BBL files to a separate location safe from zip-deletion.

Suggested solution

Use an InnoSetup installer.

What alternatives are there?

We could use NSIS or WiX. InnoSetup looks straightforward, although it doesn't provide an easy way to customise error messages with links (e.g. our 'report a problem with my exe.xml' link.)

See also #42 and #43, which this enables.

Hello,

I'm running the latest version of BBL. Version 0.7. I'm trying to program the autopilot buttons HDG through IAS to work properly on the Bravo Throttle Quadrant. The code that I'm putting into the "config" folder isn't having the effect that it should be. I've added this code:

[Aircraft.FlyByWire_A320_NEO]
HDG = A:A32NX_FCU_HDG_MANAGED_DASHES == 1
NAV = A:XMLVAR_Baro1_Mode == 1
APR = A:A32NX_FCU_APPR_MODE_ACTIVE == 1
REV = A:XMLVAR_Baro1_Mode == 2
ALT = A:AUTOPILOT ALTITUDE SLOT INDEX, bool == 2
VS = A:A32NX_AUTOPILOT_VS_SELECTED == 0
IAS = A:A32NX_FCU_SPD_MANAGED_DASHES == 1

to the bottom of the document and saved it. Nothing happens. HDG and VS lights are still stuck on, with no other lights illuminated on the autopilot panel. I've tried moving the code into the larger base config file and it makes no difference. I have the Steam version of MSFS.

Thanks!

Software version
0.6.0

Problem
BetterBravoLights refused to install because my exe.xml file is corrupt.

My exe.xml file is located at
C:\Users\aless\AppData\Roaming\Microsoft Flight Simulator\exe.xml

The error reported was

Unexpected end tag. Line 7, position 3.

The contents of the exe.xml file are as follows:

<?xml version="1.0" encoding="Windows-1252"?>
  <Launch.Addon>
    <Name>AFCBridge</Name>
    <Disabled>False</Disabled>
    <Path>E:\Steam\steamapps\common\MicrosoftFlightSimulator\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
   </Launch.Addon>
</SimBase.Document>

I understand that BetterBravoLights didn't corrupt the file and that it's simply warning
about the corrupted file. But could you help me fix it?

Software version
0.6.0

Problem
BetterBravoLights refused to install because my exe.xml file is corrupt.

My exe.xml file is located at
C:\Users\matoc\AppData\Roaming\Microsoft Flight Simulator\exe.xml

The error reported was

Unexpected end tag. Line 7, position 3.

The contents of the exe.xml file are as follows:

<?xml version="1.0" encoding="Windows-1252"?>
  <Launch.Addon>
    <Name>AFCBridge</Name>
    <Disabled>False</Disabled>
    <Path>D:\msfs\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
   </Launch.Addon>
</SimBase.Document>

I understand that BetterBravoLights didn't corrupt the file and that it's simply warning
about the corrupted file. But could you help me fix it?

Lights are [ON] in managed mode:

[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

I noticed that the annunciator light for Starter Engaged is not tied to the actual starter switch. It is tied to the engine master switch. I.E. the light won't come on until the engine master is switched on regardless of the condition of the starter switch.

I was able to fix this by making the below changes...

Original code...

StarterEngaged = A:GENERAL ENG STARTER:1, bool == 1 || A:GENERAL ENG STARTER:2, bool == 1 || A:GENERAL ENG STARTER:3, bool == 1 || A:GENERAL ENG STARTER:4, bool == 1

New code...

StarterEngaged = A:TURB ENG IGNITION SWITCH EX1:1, bool == 2 || A:TURB ENG IGNITION SWITCH EX1:2, bool == 2 || A:TURB ENG IGNITION SWITCH EX1:3, bool == 2 || A:TURB ENG IGNITION SWITCH EX1:4, bool == 2

I have tested and the light now comes on when the switch is set to Start, and turns off when it is moved to any other condition (normal or crank)

I only fly the FBW A32NX, so haven't tested with any other aircraft, but I think it should work with any of them.

Software version

0.2.0

Describe the bug

decimal values are converted in integer for example 24.5 becomes 245 (the dot separator is ignored)

Expected behavior

I expect the value 24.5 in Config.ini to be read 24.5 (with the comma separator) for Bravo's lights to work as they should for me.
for example:
in Config.ini - section [Aircraft.Asobo_TBM930] the line
LowVolts = A:ELECTRICAL MAIN BUS VOLTAGE, volts < 24.5
will never turn off the light "LOW VOLTS" of Bravo because the value is parsed as 245 while the value returned by the sim will be 28,9 (see the comma).

I spotted this with the debbuger of the application.

Other software

• MSFS: Windows Store edition or Steam? Store
• FSUIPC: Do you use FSUIPC? yes i do (freeware)

Additional context

my system is in Italian but the simulator is in english

Software version 0.60

Describe the bug

Had installed AFC Bridge and the folder was present in my Community folder. Downloaded Bravo from flightsim.to and extracted contents to dedicated folder on my E drive. Run install.bat as admin. No change from Bridge results. Look in Community folder and bridge folder is still present and working. Ran uninstall.bat. Manually removed bridge folder. Run install.bat . Noticed no change in community folder. Took flight , no lights working at all. Restore bridge folder - lights working

To reproduce
tried same steps three times wirth same results - evidently Bravo is not installing.

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

Um, I expected the lights to work - they did not.

Screenshots
If applicable, add screenshots to help explain your problem.

Other software

• MSFS: Windows Store edition or Steam? Store
• FSUIPC: Do you use FSUIPC?
  Yes
  Additional context

Otyer than not working there was no damage or problem caused by Bravo - just didn't work.

FWIW, my MSFS install is on my F: drive.

Software version

0.8.2

Problem

I think it would be really helpful for people to be able to test certain lights on their Bravo.
I myself am having an issue where some lights are indicating as something else. This is not related to your software, but Honeycomb shipping me an RMA unit that was not wired correctly.
It would be a cool and useful feature for some to make sure their lights are working appropriately and might even faster resolve any future issues.

Suggested solution

Make buttons that can test each light individually, and all lights at once.

What alternatives are there?

I have not found any yet.

Other information

Thanks for the good work so far!

Software version

0.8.2

What are you trying to do?

install and have the led lights operational on the Bravo throttle quadrant

What's the problem?

honeycomb software not working and trying to install betterbravolights

What have you tried already?

all you tube suggestions, nothing works

Other information

I have attached my xml.exe and cant fix it or identify corruption. can you help fix it? Thanks, Tom

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
	<Descr>Launch</Descr>
	<Filename>exe.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Name>FenixA320</Name>
		<Disabled>False</Disabled>
		<Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
  <Launch.Addon>
    <Name>AFCBridge</Name>
    <Disabled>False</Disabled>
    <Path>C:\Users\purpl\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
   </Launch.Addon>
</SimBase.Document>

Software version

0.8.2

Problem

The Fenix A320 is a popular aircraft so it would be good to have configuration for it.

Suggested solution

No response

What alternatives are there?

No response

Other information

No response

Software version

0.8.0

Problem

Right now we ship all the required .NET framework files with BBL. That's responsible for about 95% of the download and installation size of BBL. If a user already has the right version of .NET (not unlikely given that many other MSFS tools use .NET) it's a bit of a waste of time.

Also, pre-installing .NET as part of bootstrapping an installer (see #41) would mean we could use a .NET DLL during the installation process, which would make exe.xml-corruption fixing and the like much easier.

Dependencies

Depends on #41

Software version

0.8.0

Problem

Back in v0.7.0 we split out the user configuration file from the built-in configuration file to make it easier for users to keep their own configs between versions. That's good, but we can take it further by completely separating those files, storing the user's config file somewhere else (in their profile) rather than in the installation directory.

This issue really requires a proper installer (#41) to implement.

Dependencies

Depends on #41.

Software version

What are you trying to do? After installing 0.7.0 using install batch file, Bravo lights not correct. This is with FBW A32Nx. Prior version was working perfectly.

What's the problem? Starter Engaged light always on. Parking Brake light always off. Not sure other lights working correctly.

What have you tried already? I tried uninstalling BBL 0.7.0 using uninstall batch file. Reinstalled again using install batch file. Still lights are not correct.

Other software
After installing BBL using batch file, is BBL supposed to show in MSFS Addons Linker? The AFC_Bridge file still shows in MSFS Addons Linker. Another question, if I uninstall BBL using uninstall batch file, do I need to reinstall AFC_Bridge file?

• MSFS: Windows Store on S: drive. MSFS SU7. FBW A32Nx Development version - latest update.

Is there a way to verify whether BBL is installed and working correctly or not? Thank you for any help you can provide.

Software version

0.8.2

Location of my exe.xml file

C:\Users\gurup\AppData\Roaming\Microsoft Flight Simulator

Contents of my exe.xml file

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document version="1,0" Type="SimConnect" >
	<Descr>Launch</Descr>
	<Filename>exe.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Name>Aerosoft VDGS Driver</Name>
		<Disabled>False</Disabled>
		<Path>D:\MSFS\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe</Path>
	</Launch.Addon>
	<Launch.Addon>
		<Name>Couatl</Name>
		<Disabled>False</Disabled>
		<Path>D:\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
	</Launch.Addon>
	<Launch.Addon>
		<Name>FenixA320</Name>
		<Disabled>False</Disabled>
		<Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    <Launch.Addon>
		<Name>AFCBridge</Name>
    	<Disabled>False</Disabled>
    	<Path>D:\MSFS\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
   </Launch.Addon>
</SimBase.Document>

The installation error

No response

The installation logic currently only works for MSFS installed via the Windows Store. It also needs to be able to locate exe.xml properly for Steam installations.

Software version
0.6.0

Problem
BetterBravoLights refused to install because my exe.xml file is corrupt.

My exe.xml file is located at
C:\Users\jstor\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml

The error reported was

Unexpected end tag. Line 7, position 3.

The contents of the exe.xml file are as follows:

<?xml version="1.0" encoding="Windows-1252"?>
  <Launch.Addon>
    <Name>AFCBridge</Name>
    <Disabled>False</Disabled>
    <Path>G:\Base Sim\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
   </Launch.Addon>
</SimBase.Document>

I understand that BetterBravoLights didn't corrupt the file and that it's simply warning
about the corrupted file. But could you help me fix it?

Is it possible to use K: events?

Software version
0.2.0

Is your feature request related to a problem? Please describe.
I've seen one machine with a corrupt exe.xml file (there were 4 XML root elements, all pointing to RealSimGear software) and had reports of another: https://flightsim.to/file/21253/better-bravo-lights/193817

The message Operation Failed: There are multiple root elements. Line7, position 4 is enough to tell me that there's a problem with multiple roots caused by somebody else's broken installer, but it needs a message that a real user will understand.

Describe the solution you'd like
Explicitly detect this situation and provide help with fixing it, perhaps linking to a web page that explains the problem.

Software version

0.8.1

Problem

Light on REV button for VNav function

Suggested solution

The 737 does not have a Backcourse, but uses this button REV to enable VNav.
Put in the PMDG 737-700 section of the Config.Buildin.ini this extra code:

REV = L:ngx_MCP_VNav > 0

Works great for me!

What alternatives are there?

No response

Other information

No response

Software version

0.8.2

Location of my exe.xml file

C:\Users\RONPR\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml

Contents of my exe.xml file

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>EXE.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>FSUIPC7</Name>
    <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
    <CommandLine>-auto</CommandLine>
    <NewConsole>False</NewConsole>
  </Launch.Addon>
  <Launch.Addon>
    <Name>BravoLights</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Users\RONPR\Desktop\BetterBravoLights_JRpUI\Program\BetterBravoLights.exe</Path>
    <CommandLine>/startedbysimulator</CommandLine>
    <NewConsole>False</NewConsole>
  </Launch.Addon>
	<Name>FenixA320</Name>
	<Disabled>False</Disabled>
	<Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
  </Launch.Addon>
</SimBase.Document>

The installation error

The 'SimBase.Document' start tag on line 2 position 2 does not match the end tag of 'Launch.Addon'. Line 26, position 5.

Software version

0.7.0

Modifying or adding?

Adding

Which Aircrafts?

FBW A32NX

The configuration

Better Bravo Lights Variable List
FSUIPC7

See

[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

Additional context

I don´t use NAV and REV, so I replaced them to set NAV = [QNH local] and REV = [QNH STD]

Software version

0.7.0

Describe the bug

I found an issue related to sim world map. If i install Better Bravo light it is not possible to insert a third point between an A -B route. In other words, i make a flight plan from an A airport to B airport and the sim shows the lines that connect the two airport. But if i want to insert a POI between the A-B route it is not possible because the voice menu ADD that appears when you click on a POI is not clickable. I hope you can understand what i am saying. Let me know otherwise. If i uninstall the Better Bravo Light the problem disappear.

To reproduce

Steps to reproduce the behavior:

1. Go to 'World Map'
2. Make a Leg from an airport to another once
3. Try to insert an intermediate POI between the A and B airport
4. You should notice that you cannot click on ADD of POI menu

• MSFS: Windows Store edition or Steam?
• Windows Store Edition

*Hi, I downloaded your tool version 0.7.0. I unzipped it and run the installer. The black window opens for a split second and closes again.
I then run MSFS, but there are no lights at all. I reboot and try again: The lights are there. Next and all later attempts: no lights at all.

I use MSFS: Windows Store edition

I tried to download and install the AFC Bridge fom Honeycomb/Aerosoft, run your uninstaller, but there are no lights either. Since they worked once, I assume that the LEDs are ok.
Any help would be appreciated.
Thanks!
Cheers
Gunter

The current bundle assumes that .NET Core is installed. It's possible to produce a distribution bundle that contains .NET Core and not require the separate installation.

It would bump the distribution up from 0.5Mb to about 100Mb, but the extra convenience is worthwhile, and compared to the 100GB download MSFS had to get their software installed, it's tiny.

Software version

0.7.0

Flight Simulator installation type

Windows Store

Problem

As of Sim Update 9, the experimental variables list is causing CTDs in MSFS very easily.

How to reproduce the problem

Scroll down through the A: variables list. After a few seconds MSFS will CTD.

Software version
0.4.0

Describe the bug

Installation failure.

Screenshots

CC: @JimHerrod

Software version

0.4.2.0

Modifying or adding?

Modifying some of the configuration

Which Aircrafts?

A32NX FBW

The configuration

AUTOPILOT = L:A32NX_AUTOPILOT_1_ACTIVE == 1 OR L:A32NX_AUTOPILOT_2_ACTIVE == 1
LowFuelPressure = A:GENERAL ENG FUEL PRESSURE:1, psi <= 10 OR A:GENERAL ENG FUEL PRESSURE:2, psi <= 10
LowOilPressure = A:ENG OIL PRESSURE:1, psi <= 60 OR A:ENG OIL PRESSURE:2, psi <= 60
Door = A:CANOPY OPEN, percent > 0 OR A:EXIT OPEN:0, percent > 0 OR A:INTERACTIVE POINT OPEN:3, percent > 0 OR A:INTERACTIVE POINT OPEN:5, percent > 0
; StarterEngaged will turn on when engine mode selector is in IGN/START
StarterEngaged = A:TURB ENG IGNITION SWITCH EX1:1, enum == 2
APU = A:APU GENERATOR ACTIVE, bool == 1
ParkingBrake = L:A32NX_PARK_BRAKE_LEVER_POS == 1
; AntiIce will be on when PROBE/WINDOW HEAT is on, 
AntiIce = L:A32NX_MAN_PITOT_HEAT == 1
LowHydPressure = L:A32NX_HYD_BLUE_PRESSURE < 2000 OR L:A32NX_HYD_GREEN_PRESSURE < 2000 OR L:A32NX_HYD_YELLOW_PRESSURE < 2000
LowVolts = L:A32NX_ELEC_DC_1_BUS_IS_POWERED == 0 OR L:A32NX_ELEC_DC_2_BUS_IS_POWERED == 0

Additional context

Thanks for this amazing job you have done

Software version

0.8.0

Change type

Modify existing aircraft

Aircrafts

PMDG 737

Configuration

; Additions + corrections to what shipped in 0.8.0:

[Aircraft.PMDG 737-700, Aircraft.PMDG 737-700BDSF, Aircraft.PMDG 737-BBJ]

; Anti Ice annunciator light is on if either left or right probe are off
; CAPT PITOT, L ELEV PITOT, L ALPHA VANE, TEMP PROBE, F/O PITOT, R ELEV PITOT, R ALPHA VANE, AUX PITOT
AntiIce = L:switch_142_73X != 0 OR L:switch_143_73X != 0 OR L:switch_144_73X != 0 OR L:switch_145_73X != 0 OR L:switch_146_73X != 0 OR L:switch_147_73X != 0 OR L:switch_148_73X != 0 OR L:switch_149_73X != 0

; Left and right master caution button lights
MasterCaution = L:switch_3481_73X != 0 OR L:switch_4381_73X != 0

; APU switch isn't OFF
APU = L:switch_118_73X > 0

; Monitor the 6 fuel pressure lights
LowFuelPressure = L:switch_41_73X > 0 OR L:switch_42_73X > 0 OR L:switch_43_73X > 0 OR L:switch_44_73X > 0 OR L:switch_47_73X > 0 OR L:switch_48_73X > 0

; Monitor the 4 hyd pump pressure lights
LowHydPressure = L:switch_161_73X > 0 OR L:switch_162_73X > 0 OR L:switch_163_73X > 0 OR L:switch_164_73X > 0

; Either engine is something other than OFF
StarterEngaged = L:switch_119_73X != 10 OR L:switch_121_73X != 10

; ENG1, APU and ENG2 fire lights
EngineFire = L:switch_6972_73X != 0 OR L:switch_6982_73X != 0 OR L:switch_6992_73X != 0

Other information

No response

I've not managed to reproduce this myself, but several users have reported on flightsim.to that BBL hasn't exited when the sim has exited.

In my testing, BBL exits every time, whether you exit the sim cleanly or not but we need to do something as several users have reported this.

Software version

0.8.2

Change type

New aircraft

Aircrafts

PMDG737-600, PMDG 737-800, PMDG 737-900

Configuration

;; PMDG 737-600, 737-700, 737-800, 737-900, 737-900ER
[Aircraft.PMDG 737-600, Aircraft.PMDG 737-700, Aircraft.PMDG 737-700BDSF, Aircraft.PMDG 737-700BBJ, Aircraft.PMDG 737-800, Aircraft.PMDG 737-800BCF, Aircraft.PMDG 737-800BDSF, Aircraft.PMDG 737-800BBJ2, Aircraft.PMDG 737-900, Aircraft.PMDG 737-900ER]
HDG = L:ngx_MCP_HdgSel > 0
NAV = L:ngx_MCP_LNav > 0
APR = L:ngx_MCP_App > 0
; Thanks to @Flintstone2k12 for the REV/VNav mapping!
REV = L:ngx_MCP_VNav > 0
ALT = L:ngx_MCP_AltHold > 0
VS = L:ngx_MCP_VS > 0
IAS = L:ngx_MCP_LvlChg > 0
AUTOPILOT = L:ngx_MCP_CMDA > 0 OR L:ngx_MCP_CMDB > 0

; ENG1, APU and ENG2 fire lights
EngineFire = L:switch_6972_73X != 0 OR L:switch_6982_73X != 0 OR L:switch_6992_73X != 0
; PMDG 737 shows Low Oil Pressure warning in the engine status display, but the oil pressure reported to MSFS doesn't seem to correspond to anything
LowOilPressure = OFF
; Monitor the 6 fuel pressure lights
LowFuelPressure = L:switch_41_73X > 0 OR L:switch_42_73X > 0 OR L:switch_43_73X > 0 OR L:switch_44_73X > 0 OR L:switch_47_73X > 0 OR L:switch_48_73X > 0
; CAPT PITOT, L ELEV PITOT, L ALPHA VANE, TEMP PROBE, F/O PITOT, R ELEV PITOT, R ALPHA VANE, AUX PITOT
AntiIce = L:switch_142_73X != 0 OR L:switch_143_73X != 0 OR L:switch_144_73X != 0 OR L:switch_145_73X != 0 OR L:switch_146_73X != 0 OR L:switch_147_73X != 0 OR L:switch_148_73X != 0 OR L:switch_149_73X != 0
; Either engine is something other than OFF
StarterEngaged = L:switch_119_73X != 10 OR L:switch_121_73X != 10
; APU light is on if the APU switch isn't OFF
APU = L:switch_118_73X > 0
; Left and right master caution button lights
MasterCaution = L:switch_3481_73X != 0 OR L:switch_4381_73X != 0
; PMDG 737 annunciator does have an 'Anti Ice' entry which is on if either probe heat is off, but these don't seem to be reflected in any A: or L: vars
Vacuum = OFF
; Monitor the 4 hyd pump pressure lights
LowHydPressure = L:switch_161_73X > 0 OR L:switch_162_73X > 0 OR L:switch_163_73X > 0 OR L:switch_164_73X > 0
; PMDG 737 reports 24V to all voltage variables, even if all power is off, so we can't map LOW VOLTS right now
LowVolts = OFF
; PMDG 737 annunciator reports DOORS light for cabin doors, cargo doors, emergency exits, equipment hatch or air stairs
Door = \
    L:FwdLwrCargoDoor > 0 OR L:AftLwrCargoDoor > 0 OR \
    L:FwdLeftCabinDoor > 0 OR L:FwdRightCabinDoor > 0 OR \
    L:AftLeftCabinDoor > 0 OR L:AftRightCabinDoor > 0 OR \
    L:OverwingFwdLeftEmerExit > 0 OR L:OverwingFwdRightEmerExit > 0 OR \
    L:OverwingAftLeftEmerExit > 0 OR L:OverwingAftRightEmerExit > 0 OR \
    L:EEDoor > 0 OR L:AirStairs > 0


### Other information

Edited to add PMDG 737-900 support. Add this to your config.ini in your bravo lights folder to overwrite the default PMDG support until we get this officially supported.

You're doing an excellent job on the A32NX config and I like the way the APU and ANTI ICE lights now behave. One item that may need to be revisited is the Low HYD pressure light. It remains always on and according to the expression, it should only be lit if the blue, green or yellow pressures are below 2000 psi. As shown below, my pressures are at a constant 3000 psi in the aircraft, but the light remains illuminated. Also, if I'm understanding the debugger correctly, it looks like the software is seeing values of 0 on all 3 hyd systems

Software version

0.6.0.0

Describe the bug

I had just flown from PHNG to PHMK and landed. Taxi'd in, and refueled. Started the plane back up, and was talking to ATC for taxi clearance, and had a crash to desktop of MSFS and BetterBravoLights. Please understand that I am not mad, I'm just curious about what happened. Not sure if it was an MSFS thing, a BetterBravoLights thing, or something unrelated. The high number of CTDs and lack of any error logging in MSFS is frustrating. :\

Other software

• MSFS: Steam

Additional context
I ran "View Reliability History" in Windows and it showed me that both FlightSimulator.exe and BetterBravoLights.exe had "Stopped Working." (Control Panel\All Control Panel Items\Security and Maintenance\Problem Details)

Here's the information that it showed me from FlightSimulator.exe:
Source
FlightSimulator.exe

Summary
Stopped working

Date
‎11/‎30/‎2021 19:48

Status
Report sent

Description
Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.21.13.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.21.13.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 0000000002483577
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 54d2
Additional Information 2: 54d2a9747ca914384141a26ff29a12eb
Additional Information 3: a770
Additional Information 4: a7706ce3baf24deea7469f253ee5f9b5

Extra information about the problem
Bucket ID: 667fa6f8d3909a703f717e361a01eb07 (2265730858373737223)

Here's the info from BetterBravoLights:
Source
BetterBravoLights

Summary
Stopped working

Date
‎11/‎30/‎2021 19:49

Status
Report sent

Description
Faulting Application Path: C:\Program Files (x86)\BetterBravoLights_gZBm4\Program\BetterBravoLights.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: BetterBravoLights.exe
Application Version: 0.6.0.0
Application Timestamp: 614cbf2c
Fault Module Name: KERNELBASE.dll
Fault Module Version: 10.0.19041.1387
Fault Module Timestamp: 0b9a844a
Exception Code: e0434352
Exception Offset: 0000000000034f69
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 319d
Additional Information 2: 319df3396735776e06e788ea83f355bb
Additional Information 3: ff92
Additional Information 4: ff92b0239c28fa9cf388aff689e28fb8

Extra information about the problem
Bucket ID: 3abf95950e657e16ebf20a1edf8cd1b2 (2013683111103877554)

Please let me know if there are any other logs or diagnostic stuff I can get for you. Thanks! -Andy

Software version
0.4.0

Problem
BetterBravoLights refused to install because my exe.xml file is corrupt.

My exe.xml file is located at
C:\Users\User\AppData\Roaming\Microsoft Flight Simulator\exe.xml

The error reported was

Unexpected end tag. Line 7, position 3.

The contents of the exe.xml file are as follows:

<?xml version="1.0" encoding="Windows-1252"?>
  <Launch.Addon>
    <Name>AFCBridge</Name>
    <Disabled>False</Disabled>
    <Path>C:\Users\User\AppData\Roaming\Microsoft Flight Simulator\Packages\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
   </Launch.Addon>
</SimBase.Document>

I understand that BetterBravoLights didn't corrupt the file and that it's simply warning
about the corrupted file. But could you help me fix it?

Software version
0.2.0

Is your feature request related to a problem? Please describe.
Unless I happen already to know exactly which version of the software I've downloaded and running, there's no easy way (other than to inspect the .dll/.exe files) to find out which version of the software is running, so it's harder for people to report the version number in bug reports.

Describe the solution you'd like

• the version number needs to be visible in the software whilst running; maybe in the tray icon tooltip?
• the version number needs to be visible in the unzipped folder in case of installation problems; possibly add a README.md or VERSION file?