Runway lights on in the day (broken LUA script)

[darrylacw579]

Hello

After installing AIG I’m noticing some anomalies with runway lights being activated in the day mode and won’t turn off    specifically at FLYTAMPA CYYZ.   

Contacting flytampa they said there is no fix  from their side and that upon investigation the aig is messing up the LUA script.   

Please advise if there is a fix for this or how to repair that LUA script so everything works like before
Deeply frustrated

Best
Darry

[Kaiii3]

what LUA script, we do not touch any LUA scripts of scenery developers.

[GCRR]

Hi Folks,

unfortunately , i´m having the same issue only with some FLYTAMPA sceneries. In my case it´s LOWW,KBOS and KLAS. When I posted the issue at the FlyTampa-Forum, "Martin" told me the same as to the original poster (LUA-Script issue), also that some other costumers had reported the same behaviour in P3D5.
In my case, i´m on P3Dv4.5HF3 installed from scratch. AIG was the last to install and in fact , that was when i started to see this issue.
I did the test : deactivating AIG, all was good, reactivating (reinstalling) AIG, runway lights were on again. Very strange indeed and never seen before.
Might there be any offending files worth to check ? Anyway, i´m "glad" that i´m not hte only one .

Best regards

Lars Stahmann

[Kaiii3]

do you use payware aircraft from FSPXAI?

[GCRR]

No, only freeware .

Regards, Lars

[Kaiii3]

we are running some tests by internal users, since I do not have the scenery

[GCRR]

Thanks,

that´s great. Will follow this thread. If you need my logs or any other files, please let me know, i´ll be able to provide them a little bit later.

Regards, Lars

[johanfrc]

Testing done in P3Dv4.5HF3.

Here are the results:

1) AIG + FT CYYZ: Runway Lights on.
2) No AIG + FT CYYZ: No Runway Lights on.
3) AIG (minus the AIG LUA scripts) + FT CYYZ: Runway Lights on.

So it's can't be AIG. I (and Kai) would guess it's a P3D bug.

[GCRR]

Hi Johan,

i just saw your post at FlyTampa and indeed it appears to be a bug introduced with HF3, however something during the AIG-installation must trigger it.
As i stated before, i did a complete reinstall and i use to install airport by "batches", then fire up P3D and check every single one of them. Everything was fine untill i began to install AIG-Traffic. So, quite strange, let´s see if FlyTampa comes up with something.

Best regards, Lars

[darrylacw579]

Great news that you were able to replicate this issue.

Is the bug on the AIG side or with FlyTampa to fix? 

if with FlyTampa, i know Martin quite well, Im actually the guy who did the photography for CYYZ scenery so let me know and I can speak with him today

Hoping we can resolve this soon

D

[johanfrc]

I guess the reason why it might be the AIG that have triggered it is because it might be the only other addon using LUA scripts in the area. I know some UI planes do too, like Qualitywings, but otherwise I don't think a lot of addon developers don't use LUA.

Since it appears with both the AIG LUA scripts and no AIG LUA scripts, it seems to me that it's neither AIG nor FT's fault, but a bug in P3D. So we can't do anything else but wait.

If someone is still using P3Dv4.5HF2 and have the CYYZ and AIG AI, would like to test this, it would be awesome. Because if it was something that AIG had introduced then it would have been a problem earlier. But it has only appeared after the HF3 was released (and maybe also v5 , but I don't have v5 installed so can't check there). So that tells me that it's something LM have "bugged" in HF3 and maybe v5 too.

[darrylacw579]

is it worth flagging this on the p3d forums so they are aware of the issue?

[johanfrc]

Well. It's found today so it's still very new found. I'm sure someone will post it there.

[AF082]

I've just posted on the other thread Johan started. I've checked P3D v4.5 HF2 at Fly Tampa Toronto with AIGOCI installed, and the runway lights are on during the daytime.

[sticky1202]

Thought I saw a post somewhere that it may have to do with the latest SODE release. Someone rolled back to 1.6.8 and problems went away. This was for P3Dv4.5

Jim