Hello, I have the pro version installed, but before I start messing around with it I'm trying to understand what the program does by default and what requires more user intervention.  I did some spotting and noticed that I had A320's without the strobes operating as they should be (or as I saw in the teaser video).  The wingtips were double strobes, but the tail strobe was as well and was flashing after the wing strobes had flashed.  The strobes didn't look as impressive as in the teaser video so I'm wondering if I've messed something up altogether.  Do I not have this installed properly or is that aircraft-specific light pattern something I need to go and add by aircraft category?

To get started after opening the program, I select "scan and configure AI airplanes" then it takes me to the AI Lights Setting tab, I click on apply settings and then launch P3D. 

Am I missing something?

Thanks

12 minutes ago, regis9 said:

Hello, I have the pro version installed, but before I start messing around with it I'm trying to understand what the program does by default and what requires more user intervention.  I did some spotting and noticed that I had A320's without the strobes operating as they should be (or as I saw in the teaser video).  The wingtips were double strobes, but the tail strobe was as well and was flashing after the wing strobes had flashed.  The strobes didn't look as impressive as in the teaser video so I'm wondering if I've messed something up altogether.  Do I not have this installed properly or is that aircraft-specific light pattern something I need to go and add by aircraft category?

To get started after opening the program, I select "scan and configure AI airplanes" then it takes me to the AI Lights Setting tab, I click on apply settings and then launch P3D. 

Am I missing something?

Thanks

Which P3D version are you using? and do you have dynamic lights enabled in the sim?

I’m using 4.5 with hotfix 2, dynamic lights are enabled.

Change to expert interface, increase the amount of intensity for the strobes.

Skywolf can also share his presets with you.

Regards,

Simbol 

I will post my presets later in the day (at work right now) with the screenshot.

I just did 4k setting (due to my 4k monitors),

and bumped up everything to 160%.

 

3 hours ago, regis9 said:

Hello, I have the pro version installed, but before I start messing around with it I'm trying to understand what the program does by default and what requires more user intervention.  I did some spotting and noticed that I had A320's without the strobes operating as they should be (or as I saw in the teaser video).  The wingtips were double strobes, but the tail strobe was as well and was flashing after the wing strobes had flashed.  The strobes didn't look as impressive as in the teaser video so I'm wondering if I've messed something up altogether.  Do I not have this installed properly or is that aircraft-specific light pattern something I need to go and add by aircraft category?

To get started after opening the program, I select "scan and configure AI airplanes" then it takes me to the AI Lights Setting tab, I click on apply settings and then launch P3D. 

Am I missing something?

Thanks

Are you using the FAIB AI models for the A32X?

Airbus uses two types of strobe lights. To cite from airliners.net:
"Airbus uses a direction identification logic in their strobe lights. Forward facing strobes (left and right wingtip) double flash, whereas the rearward facing strobe is a single flashing unit. As a result you can identify whether the aircraft is coming towards you or away from you by the strobe flashes (double = towards you, single = away from you)."

This a feature that Simbol has incorporated in the Professional version. However, you need to use the non-wingflex model of the A320. Erez Weber, the designer of the beautiful FAIB models, offers two models. Winglex and non-wingfelx. The non-wingflex models have their effects attached via a position setting in the aircraft.cfg and hence a different effect can be assigned by AILRP for each strobe. The wingflex model, however, have their effects attached to the model itself and Erez used only one effect file name for all strobe lights. Therefore, AILRP can - resulting from a sim limitation - only replace the lights based on the effect file name. And with every effect calling for the same name, we needed do decide what effect to use. We opted for the double flash, as this is most characteristically for an Airbus.

Further, it can happen that the effect synchronization of the sim will get deranged. For example, higher simulation rates like 4x can trigger this but it can happen also in normal mode. As a result, you will see random flashing lights instead of the normal sequence. But this normally does settle after a few minutes.

Best,
Christoph

I have always said that adding wingflex to AI planes was an exercise in pointless complexity, and this is a classic example.

Thanks for the responses, I do have enhanced lights now (I found 160% too high but settled around 120% for most).  I still seem to be having issues with the strobe sequencing.  I do use the FAIB A320, I actually didn't realize there was a wingflex version of it.  I use what AIGAIM/OCI installs for the most part so I'm not sure which version that is.  Here is the light section from my CFM A320 if that helps:

[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=1, 5.998, 0, -5.835, fx_fsreborn_beacon2628
light.1=1, 3.718, 0, 8.5, fx_fsreborn_beacon2628
light.2=2, 0, 0, 0, fx_fsreborn_stfb2628
light.3=3, -69.63, 0, 4.645, fx_fsreborn_navwhi2628
//light.4 = 2, -14.023, -55.505,  2.871, fx_FAIB_A320_strobe
//light.5 = 2, -14.023,  55.505,  2.871, fx_FAIB_A320_strobe
//light.6 = 3, -13.5, -55.151,  2.852, fx_FAIB_A320_navred
//light.7 = 3, -13.5,  55.151,  2.852, fx_FAIB_A320_navgre
//If you have Shockwave lights you can enable them by removing the "//" from the beginings of the next lines
//light.8 = 5, 0.09, -7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light
//light.9 = 5, 0.09, 7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light
//light.10 = 5, 37.319, -0.71, -5.463, fx_shockwave_landing_light_narrow // shockwave landing light
//light.11 = 6, 37.319, 0.706, -5.463, fx_shockwave_landing_light_narrow // shockwave taxi light

While spotting I had A320's with both the wingtip and rear strobes doing double flashes, and I had a 737-800 doing the same thing so it seems like something is not quite right in my setup.  I loaded the airport and let it sit for around 30 minutes to give things time to stabilize and the result was the same.

This is the FAIB 737-800, again installed by OCI:

[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=3, -19.971, -55.145, 4.795, fx_fsreborn_navred2652
light.1=3, -19.971, 55.145, 4.795, fx_fsreborn_navgre2652
light.2=2, 0, 0, 0, fx_fsreborn_stfb2652
light.3=1, -5.242, 0, -4.21, fx_fsreborn_beacon2652
light.4=1, 1.1, 0, 9.567, fx_fsreborn_beacon2652
light.5=3, -26.315, 55.062, 4.698, fx_fsreborn_navwhi2652
light.6=3, -26.315, -55.062, 4.698, fx_fsreborn_navwhi2652

Thanks

Edited October 20, 20196 yr by regis9
Added 738 light info.

8 hours ago, regis9 said:

Thanks for the responses, I do have enhanced lights now (I found 160% too high but settled around 120% for most).  I still seem to be having issues with the strobe sequencing.  I do use the FAIB A320, I actually didn't realize there was a wingflex version of it.  I use what AIGAIM/OCI installs for the most part so I'm not sure which version that is.  Here is the light section from my CFM A320 if that helps:

Ok by the looks at your light config it seems you have the WinFlex version installed.

I have been speaking to KAII to give users the option to users choose. If you change to a NFW (Non Wing Flex Model) you will notice how the strobes will behave as real world.

S.

Edited October 21, 20196 yr by simbol

Thanks Simbol, i’ll give that a shot tomorrow.

I downloaded the FAIB A320 base pack and replaced the model with the NFW model.  I now have properly functioning strobes on the wings, but the rear strobe is not working.

Here is what my lights section looks like after AI Lights configures the aircraft. 

[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
//If you have Shockwave lights you can enable them by removing the "//" from the beginings of the next lines
//light.8 = 5, 0.09, -7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light
//light.9 = 5, 0.09, 7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light
//light.10 = 5, 37.319, -0.71, -5.463, fx_shockwave_landing_light_narrow // shockwave landing light
//light.11 = 6, 37.319, 0.706, -5.463, fx_shockwave_landing_light_narrow // shockwave taxi light
light.0=2, 0, 0, 0, fx_fsreborn_stfb2628
light.1=3, -13.5, -55.151, 2.852, fx_fsreborn_navred2628
light.2=3, -13.5, 55.151, 2.852, fx_fsreborn_navgre2628
light.3=1, 5.998, 0, -5.835, fx_fsreborn_beacon2628
light.4=1, 3.718, 0, 8.5, fx_fsreborn_beacon2628
light.5=3, -69.63, 0, 4.645, fx_fsreborn_navwhi2628

The FAIB 737-800 does not have the custom strobes working, it has the standard double flash both on the wings and the rear.  It doesn't appear that there is a wing flex or non-wing flex version of this aircraft?  Here is the 737-800 lights section.

[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=3, -19.971, -55.145, 4.795, fx_fsreborn_navred2652
light.1=3, -19.971, 55.145, 4.795, fx_fsreborn_navgre2652
light.2=2, 0, 0, 0, fx_fsreborn_stfb2652
light.3=1, -5.242, 0, -4.21, fx_fsreborn_beacon2652
light.4=1, 1.1, 0, 9.567, fx_fsreborn_beacon2652
light.5=3, -26.315, 55.062, 4.698, fx_fsreborn_navwhi2652
light.6=3, -26.315, -55.062, 4.698, fx_fsreborn_navwhi2652
 

Edited October 21, 20196 yr by regis9

29 minutes ago, regis9 said:

I downloaded the FAIB A320 base pack and replaced the model with the NFW model.  I now have properly functioning strobes on the wings, but the rear strobe is not working.

Here is what my lights section looks like after AI Lights configures the aircraft. 

[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
//If you have Shockwave lights you can enable them by removing the "//" from the beginings of the next lines
//light.8 = 5, 0.09, -7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light
//light.9 = 5, 0.09, 7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light
//light.10 = 5, 37.319, -0.71, -5.463, fx_shockwave_landing_light_narrow // shockwave landing light
//light.11 = 6, 37.319, 0.706, -5.463, fx_shockwave_landing_light_narrow // shockwave taxi light
light.0=2, 0, 0, 0, fx_fsreborn_stfb2628
light.1=3, -13.5, -55.151, 2.852, fx_fsreborn_navred2628
light.2=3, -13.5, 55.151, 2.852, fx_fsreborn_navgre2628
light.3=1, 5.998, 0, -5.835, fx_fsreborn_beacon2628
light.4=1, 3.718, 0, 8.5, fx_fsreborn_beacon2628
light.5=3, -69.63, 0, 4.645, fx_fsreborn_navwhi2628

The FAIB 737-800 does not have the custom strobes working, it has the standard double flash both on the wings and the rear.  It doesn't appear that there is a wing flex or non-wing flex version of this aircraft?  Here is the 737-800 lights section.

[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=3, -19.971, -55.145, 4.795, fx_fsreborn_navred2652
light.1=3, -19.971, 55.145, 4.795, fx_fsreborn_navgre2652
light.2=2, 0, 0, 0, fx_fsreborn_stfb2652
light.3=1, -5.242, 0, -4.21, fx_fsreborn_beacon2652
light.4=1, 1.1, 0, 9.567, fx_fsreborn_beacon2652
light.5=3, -26.315, 55.062, 4.698, fx_fsreborn_navwhi2652
light.6=3, -26.315, -55.062, 4.698, fx_fsreborn_navwhi2652
 

Regis,

Will review tomorrow, going to sleep quite late here in UK.

Check the ATC type of your Boeing, I think it is wrong or missing. It goes under the general section.

Regarding the Airbus, send me the full aircraft config file to [email protected]. Maybe the back tail strobe wad not set initially, this is an easy fix

Best,

Simbol 

Thanks Simbol, looks like my issue is that I edit my aircraft.cfg and change ATC type to SILENT so I don't have to hear default ATC refer to aircraft by more than their type.  I changed that and the 737 works.  With the A320 I saw one that had no strobes at the rear and one working perfectly, so I need to do some more testing on my system but things are looking good, I'll report back.

@Simbol and Beta testers my questions as to aircraft.cfg entries, in this case on example FAIB A320 CFM_NWF.

And here as to the lights entry numbering section. In particular as to 5=landing

 

Before applying AIFLR pro settings the “maiden FAIB aircraft.cfg looked as to LIGHTS as follows

 

[LIGHTS]

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing

// FAIB A320 Lights

light.0 = 1,  5.998,   0.00, -5.835, fx_FAIB_A320_beacon

light.1 = 1,  3.718,   0.00, 8.5, fx_FAIB_A320_beacon

light.2 = 2, -69.63,   0.00,  4.645, fx_FAIB_A320_strobe

light.3 = 3, -69.63,   0.00,  4.645, fx_FAIB_A320_navwhi

//light.4 = 2, -14.023, -55.505,  2.871, fx_FAIB_A320_strobe

//light.5 = 2, -14.023,  55.505,  2.871, fx_FAIB_A320_strobe

//light.6 = 3, -13.5, -55.151,  2.852, fx_FAIB_A320_navred

//light.7 = 3, -13.5,  55.151,  2.852, fx_FAIB_A320_navgre

//If you have Shockwave lights you can enable them by removing the "//" from the beginings of the next lines

//light.8 = 5, 0.09, -7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light

//light.9 = 5, 0.09, 7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light

//light.10 = 5, 37.319, -0.71, -5.463, fx_shockwave_landing_light_narrow // shockwave landing light

//light.11 = 6, 37.319, 0.706, -5.463, fx_shockwave_landing_light_narrow // shockwave taxi light

 

And no additional entry [FSREBORN_LIGHTS_CTRL] entry

 

After applying AI Lights reborn pro settings

 

[LIGHTS]

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing

light.0=1, 5.998, 0, -5.835, fx_fsreborn_beacon2677

light.1=1, 3.718, 0, 8.5, fx_fsreborn_beacon2677

light.2=2, 0, 0, 0, fx_fsreborn_stab2677

light.3=3, -69.63, 0, 4.645, fx_fsreborn_navwhi2677

//light.4 = 2, -14.023, -55.505,  2.871, fx_FAIB_A320_strobe

//light.5 = 2, -14.023,  55.505,  2.871, fx_FAIB_A320_strobe

//light.6 = 3, -13.5, -55.151,  2.852, fx_FAIB_A320_navred

//light.7 = 3, -13.5,  55.151,  2.852, fx_FAIB_A320_navgre

//If you have Shockwave lights you can enable them by removing the "//" from the beginings of the next lines

//light.8 = 5, 0.09, -7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light

//light.9 = 5, 0.09, 7.01, -3.778, fx_shockwave_landing_light_narrow // shockwave landing light

//light.10 = 5, 37.319, -0.71, -5.463, fx_shockwave_landing_light_narrow // shockwave landing light

//light.11 = 6, 37.319, 0.706, -5.463, fx_shockwave_landing_light_narrow // shockwave taxi light

But no entry new [FSREBORN_LIGHTS_CTRL] entry.

 

And an additional entry at the bottom

[FSREBORN_LIGHTS_CTRL]

light.0=1,  5.998,   0.00, -5.835, fx_FAIB_A320_beacon

light.1=1,  3.718,   0.00, 8.5, fx_FAIB_A320_beacon

light.2=2, -69.63,   0.00,  4.645, fx_FAIB_A320_strobe

light.3=3, -69.63,   0.00,  4.645, fx_FAIB_A320_navwhi

 

 

Now my question I am wondering why there is no entry 5=landing lights. Can anybody comment on this, is there something wrong in my configuration?

 

Are your LIGHTS sections looking different, have the entry 5=….?

 

Tks for help.

 

Andreas

20 minutes ago, Andreasmb said:

Now my question I am wondering why there is no entry 5=landing lights. Can anybody comment on this, is there something wrong in my configuration?

Nothing wrong.. FAIB comes with lots of lines commented // which means P3D should "IGNORE" them and so do we.

Landing lights are attached using 3DS Max as per LM SDK requirements (inside the .MDL) and FAIB developer is following the standard correctly.

S.