Actually I just tried Toronto Pearson CYYZ because I have that scenery loaded, and from the screen shot everything looks fine to me, are we seeing what we want too see? :mellow:

 

 

 

Sorry, XP 10.2 B7 64 bit

Win7 Pro 64 bit - Ati 6970 i7 2600k at 4.7ghz

Yep, that one shows both the PAPI and the TDZ :-) I believe it will be the same with LPPT, so, the "apt.dat" trick will certainly do it ;-)

 

Thx!

Yep, that one shows both the PAPI and the TDZ :-) I believe it will be the same with LPPT, so, the "apt.dat" trick will certainly do it ;-)

 

Thx!

 

You tested gregs apt.dat trick? It didn't work for me. I have, for some reason, no lights. Xpx have been a bit of a roller coaster for me so far. Loving it mostly but when stuff like this happens I just want to throw in the towel.

 

Skickat från min GT-I9300 via Tapatalk 2

 

 

You tested gregs apt.dat trick? It didn't work for me.

 

Nope, didn't test it Richard, just commenting on the screen he got from CYYZ and assuming it would probably fix the same at LPPT...

 

I do not even have X-Plane10 installed anymore :-/

 

I keep following this forum though... maybe I will re-install XP10 again some day, should I find it worth the try...

 

it's allways the same with this simulator - I begin with a lot of positive energy and enthusiasm, and somehow allways loose it for the very same reasons...well :-( ...

 

But I certainly hope for the best future for it ;-), after all, I still have my copy (couldn't find a buyer yet...) and, at least should some miracle happen in the future,

I can save yet another buy....

Richard - what airport are you seeing no lights? Are you speaking of runway edge lights, or PAPI/VASI lights... or both?

 

I believe you when you say that you don't see any of course, but I'd like to dig into the airport file to see if perhaps the intensity of that airfield's lights was somehow turned down between apt.dat versions.

Interesting topic and promoted me to look at my local airport. Nav chart says that all approaches should have PAPI or VASI and I don't

have a single one showing up. Reasonably sure that some versions ago they were available. Bug report time.

 

Chuck

Guys, I didn't change apt.dat's or anything. This is vanilla Xplane updated to 10.20 B7 64 bit, no other changes.

 

Edit: If there was some confusion.....

Guys, I didn't change apt.dat's or anything. This is vanilla Xplane updated to 10.20 B7 64 bit, no other changes.

 

True, but at some point during the previous X-Plane update releases, Robin's July 2012 apt.dat update release was injected into the mainstream. Anyone running 10.10 or the .20 beta's has the updated apt.dat file as provided by Laminar Research - you didn't have to get it on your own - they pushed it to you.

 

There does seem to be several issues at play here:

 

First, some of these issues may come from the adjustment of the light intensity in X-Plane overall, as part of Laminar's tweaking and patching. There have been ongoing complaints that the airport lighting as a whole is either too dark, too bright, or just not quite right. This would be a global issue - not isolated to one particular airport.

 

Second, some of the issues ARE coming from the newer apt.dat file. I've validated several instances whereby the "old" apt.dat has VASI/PAPI/Windsocks at an airport, but the "new" apt.dat no longer contains them. This has been validated in the simulation itself, and also by looking at the airport's configuration records in WED. This means that something in Robin's automatic airport generation code got tweaked between releases, causing some discrepancies.

 

There also might be an issue with the apt.dat data which changes the intensity of that particular runway's edge lights, or removes them entirely from a victim airport! This is why I'd like to see an example ICAO code from Swe_Richard to see if his airports in question no longer have runway edge lighting (or VASI/PAPI) defined in the latest apt.dat file.

 

Either way, it's a curious issue no doubt.

 

-Greg

True, but at some point during the previous X-Plane update releases, Robin's July 2012 apt.dat update release was injected into the mainstream. Anyone running 10.10 or the .20 beta's has the updated apt.dat file as provided by Laminar Research - you didn't have to get it on your own - they pushed it to you.

 

There does seem to be several issues at play here:

 

First, some of these issues may come from the adjustment of the light intensity in X-Plane overall, as part of Laminar's tweaking and patching. There have been ongoing complaints that the airport lighting as a whole is either too dark, too bright, or just not quite right. This would be a global issue - not isolated to one particular airport.

 

Second, some of the issues ARE coming from the newer apt.dat file. I've validated several instances whereby the "old" apt.dat has VASI/PAPI/Windsocks at an airport, but the "new" apt.dat no longer contains them. This has been validated in the simulation itself, and also by looking at the airport's configuration records in WED. This means that something in Robin's automatic airport generation code got tweaked between releases, causing some discrepancies.

 

There also might be an issue with the apt.dat data which changes the intensity of that particular runway's edge lights, or removes them entirely from a victim airport! This is why I'd like to see an example ICAO code from Swe_Richard to see if his airports in question no longer have runway edge lighting (or VASI/PAPI) defined in the latest apt.dat file.

 

Either way, it's a curious issue no doubt.

 

-Greg

 

I've so far tested ESNU, ESSA, ESMS, ESMQ in Sweden. No lights. Almost impossible to see the airport when it's dark. 5NM from the airport it's fine. This is in clear weather. However, I've tried EGLL, KJFK and they seem to be ok. Quite odd, I'd say.

Quick check:

 

ESMS - The airport data is the same between the old and new apt.dat file.... runway edge lighting is the same.

 

ESMQ - The old airport has PAPI visual glideslope lights, the new airport does NOT have the PAPI.... runway edge lighting is the same.

 

At least with those two airports, they call for High-Intensity Runway Lighting (HIRL) for the main runway edges... note that at those two example airports, the secondary runways are NOT lit in either apt.dat version.

 

I also just tested at ESMQ... I flew 10 miles out from Runway 16 and can still see the runway lights (when aligned with the runway, of course!) The flashing beacon is still plainly visible as well.

 

I must say - I'm at a loss for your issue, unfortunately. Since you're having more of an overall visibility issue with the airport's lighting, and the WED files are indeed calling for high-intensity lights, perhaps you're one of the users who is going to be displeased with the changes Laminar has made to more realistically represent runways at night...

 

Departing ESMQ Runway 16....

Screenshot shrunk, so the resolution won't be great, but the lights are evident...

 

Quick check:

 

ESMS - The airport data is the same between the old and new apt.dat file.... runway edge lighting is the same.

 

ESMQ - The old airport has PAPI visual glideslope lights, the new airport does NOT have the PAPI.... runway edge lighting is the same.

 

At least with those two airports, they call for High-Intensity Runway Lighting (HIRL) for the main runway edges... note that at those two example airports, the secondary runways are NOT lit in either apt.dat version.

 

I also just tested at ESMQ... I flew 10 miles out from Runway 16 and can still see the runway lights (when aligned with the runway, of course!) The flashing beacon is still plainly visible as well.

 

I must say - I'm at a loss for your issue, unfortunately. Since you're having more of an overall visibility issue with the airport's lighting, and the WED files are indeed calling for high-intensity lights, perhaps you're one of the users who is going to be displeased with the changes Laminar has made to more realistically represent runways at night...

 

Departing ESMQ Runway 16....

Screenshot shrunk, so the resolution won't be great, but the lights are evident...

 

 

This is just plain odd. The lighting as it seems in your screenshot just isn't what I was seeing. However, having recently updated to beta9 the airport lights seem to be back.

 

Really odd.

I don't think this issue was ever resolved. I'm running the latest 64-bit version of 10.20, and I'm definitely missing some lights around the airports. I have a second install that's still at 10.10, and it has all the expected lighting. Moving the 10.10 apt.dat file into 10.20 seems to have done the trick.

 

Is Laminar Research even aware of this problem? Was it ever reported?

Yep, I even used the original version on my disks 10.03rc to get it's apt.dat and paste it over the 10.20 file. It worked. I do have PAPIs, but never had proper TDZ lights on the portuguese rws....

I went ahead and used the X-Plane bug report site and submitted a report describing the problem and linking to this thread. So if they weren't aware of it before, they're aware of it now.