Board index » FlyTampa » FlyTampa-Athens

Post
 maggussje (Fri Aug 11, 2017 12:44 am)

Posts: 16
Just staying at the airport won't give you any CTD. I usually do some flying over and in the vicinity of the airport and it usually crashes within minutes.

As mentioned before, disabling the approach lights seem to have "fixed" the CTD for me, thus I hope the devs could look into this again.
Post
 liveopenskies (Fri Aug 11, 2017 3:05 am)

Posts: 5
maggussje wrote:Just staying at the airport won't give you any CTD. I usually do some flying over and in the vicinity of the airport and it usually crashes within minutes.

As mentioned before, disabling the approach lights seem to have "fixed" the CTD for me, thus I hope the devs could look into this again.


The day i got CTD i was about to prepare a flight then crash, not even got time to start APU :D . Yesterday i did same, had time to prepare my flight till pushback but i didn't go further, will try flying over the airport tonight.
Post
 Siberier (Fri Aug 11, 2017 12:06 pm)

Posts: 2
I have had the same problem with CTD. When i disengaged the approach lights bgl everything started ok.
Post
 CaptainNodrog (Sat Aug 12, 2017 3:12 am)

Posts: 4
I am also having this problem. I've flown several approaches to 03L or R and P3D V4 crashes just over the coast. I will try deleting the bgl files and see if it does the job.....

Have now renamed the following files in ...FlyTampa\Athens\scenery
[*]Alights03L.BGL
[*]Alights03R.BGL
[*]Alights21L.BGL
[*]Alights21R.BGL

Seems to have worked. No more crashes and also I've still got approach lights, because there are newer files likeRwy21Lapprlights.bgl. Will report back if I get any more CTDs but hopefully this is all it takes.
Post
 maggussje (Sat Aug 12, 2017 1:36 pm)

Posts: 16
CaptainNodrog wrote:I am also having this problem. I've flown several approaches to 03L or R and P3D V4 crashes just over the coast. I will try deleting the bgl files and see if it does the job.....

Have now renamed the following files in ...FlyTampa\Athens\scenery
[*]Alights03L.BGL
[*]Alights03R.BGL
[*]Alights21L.BGL
[*]Alights21R.BGL

Seems to have worked. No more crashes and also I've still got approach lights, because there are newer files likeRwy21Lapprlights.bgl. Will report back if I get any more CTDs but hopefully this is all it takes.


Not quite sure why this should help you, the *apprlights.bgl files are actually part of the v4 patch and seemed to have caused my CTD. By disabling these files I got rid of my CTD. ;)
Post
 george[flytampa] (Sat Aug 12, 2017 2:25 pm)

Site Admin | Posts: 3038 | Location: Southampton, UK
The Apprlights.bgls are part of AES Lite. They don't work at all in Prepar3D, so you can safely get rid of them if you make sure the 'Flytampa Runway Lighting' is selected in the config tool beforehand.
Post
 CaptainNodrog (Sat Aug 12, 2017 3:00 pm)

Posts: 4
maggussje wrote:Not quite sure why this should help you, the *apprlights.bgl files are actually part of the v4 patch and seemed to have caused my CTD. By disabling these files I got rid of my CTD. ;)


I hear you maggussje, but it has worked for me. I wonder if the Alights*bgl and the *applights.bgl co-existing is actually the bug? Maybe you could try with the same combination? I will do more flights to LGAV at different times of day, to ensure it really is a fix.
Post
 maggussje (Sat Aug 12, 2017 3:53 pm)

Posts: 16
george[flytampa] wrote:The Apprlights.bgls are part of AES Lite. They don't work at all in Prepar3D, so you can safely get rid of them if you make sure the 'Flytampa Runway Lighting' is selected in the config tool beforehand.


George, I'm confused now. The files you are obviously referring to are the following:
[*] Rwy21Rapprlights.bgl
[*] Rwy21Lapprlights.bgl
[*] Rwy06Rapprlights.bgl
[*] Rwy06Lapprlights.bgl
Is that correct? They are actually included in the patch for P3D v4 and are therefore supposed to be working in v4 from my point of view... Apart from that, not choosing the AES Lite option in the Configurator leaves these files enabled as well.

Could you please have another look into that?

@CaptainNodrog: going to look into your suggestion now as well
[EDIT] It crashed almost immediately when enabling the *apprlights.bgl files and disabling the Alights* files. So for me it's definitely the *apprlights.bgl files causing the CTD.
Post
 george[flytampa] (Sat Aug 12, 2017 4:39 pm)

Site Admin | Posts: 3038 | Location: Southampton, UK
maggussje wrote:
george[flytampa] wrote:The Apprlights.bgls are part of AES Lite. They don't work at all in Prepar3D, so you can safely get rid of them if you make sure the 'Flytampa Runway Lighting' is selected in the config tool beforehand.


George, I'm confused now. The files you are obviously referring to are the following:
[*] Rwy21Rapprlights.bgl
[*] Rwy21Lapprlights.bgl
[*] Rwy06Rapprlights.bgl
[*] Rwy06Lapprlights.bgl
Is that correct? They are actually included in the patch for P3D v4 and are therefore supposed to be working in v4 from my point of view... Apart from that, not choosing the AES Lite option in the Configurator leaves these files enabled as well.

Could you please have another look into that?

@CaptainNodrog: going to look into your suggestion now as well
[EDIT] It crashed almost immediately when enabling the *apprlights.bgl files and disabling the Alights* files. So for me it's definitely the *apprlights.bgl files causing the CTD.


Get rid of anything called ALights. Those are useless in Prepar3D.
Rwy**Rapprlights.bgl etc are the replacement lights. You need those or they'll be no lights.
Post
 CaptainNodrog (Sat Aug 12, 2017 10:00 pm)

Posts: 4
george[flytampa] wrote:Get rid of anything called ALights. Those are useless in Prepar3D.
Rwy**Rapprlights.bgl etc are the replacement lights. You need those or they'll be no lights.


Further findings today. Removing the Alights*.bgl files seems to have helped me, i.e. I can now take off at night from LGAV 0R circle the airport to KEA and land in the Aerosoft CRJ 900 on 03R or L. However, I am still getting a CTD at dusk or night on an FMS approach to 03R in the PMDG 737, just over the coast. Got this...

Code: Select all
Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: terrain.dll, version: 4.0.28.21686, time stamp: 0x594a71d5
Exception code: 0xc0000005
Fault offset: 0x00000000000e0ee7
Faulting process id: 0x1f78
Faulting application start time: 0x01d313c8806b2260
Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Program Files\Lockheed Martin\Prepar3D v4\terrain.dll
Report Id: 75e63d56-0a01-45c8-b836-c3abbb9b43b0
Faulting package full name:
Faulting package-relative application ID:


So the issue I am seeing could be with P3D or the interaction with the many add-ons I've loaded: ORBX FTX Global Base, openLC Europe & Vector, AS for P3Dv4, UT Live etc.

Daytime landings using the PMDG 737 on an FMS approach to any LGAV runway is not a problem. I'm not up for reinstalling each add-on one-by-one, so I'll just do daytime approaches to this airport for now.

Good luck maggussje. I hope you get your approach lights sorted!
Post
 maggussje (Sun Aug 13, 2017 12:29 pm)

Posts: 16
george[flytampa] wrote:
Get rid of anything called ALights. Those are useless in Prepar3D.
Rwy**Rapprlights.bgl etc are the replacement lights. You need those or they'll be no lights.


George,

Yes, I hear you.

I have understood that the Alights*.bgl files are useless in P3D. I deactivated them before, I deleted them now. However, the replacement lights themselves, namely the Rwy*apprlights.bgl, are leading to the CTD for me. It is pretty simple to reproduce: deactivating the files lets me fly at, over and into LGAV at night four the good part of an hour without any issues, leaving them enabled leads to a CTD within seconds to a few minutes at LGAV.

And yes, with the Rwy*apprlights.bgl now disabled, it leaves me without any approach lights but also without a CTD--what I obviously prefer compared to the situation before. Since I was able to nail it down to these four files I'd kindly like to ask you again for your assistance in order to make your product fully usable during night for me as well.

Thank you
Post
 george[flytampa] (Sun Aug 13, 2017 3:17 pm)

Site Admin | Posts: 3038 | Location: Southampton, UK
maggussje wrote:
george[flytampa] wrote:
Get rid of anything called ALights. Those are useless in Prepar3D.
Rwy**Rapprlights.bgl etc are the replacement lights. You need those or they'll be no lights.


George,

Yes, I hear you.

I have understood that the Alights*.bgl files are useless in P3D. I deactivated them before, I deleted them now. However, the replacement lights themselves, namely the Rwy*apprlights.bgl, are leading to the CTD for me. It is pretty simple to reproduce: deactivating the files lets me fly at, over and into LGAV at night four the good part of an hour without any issues, leaving them enabled leads to a CTD within seconds to a few minutes at LGAV.

And yes, with the Rwy*apprlights.bgl now disabled, it leaves me without any approach lights but also without a CTD--what I obviously prefer compared to the situation before. Since I was able to nail it down to these four files I'd kindly like to ask you again for your assistance in order to make your product fully usable during night for me as well.

Thank you



I spotted a potential problem.

There are two rogue files in the patch.
Rwy06Rapprlights.bgl
Rwy06Lapprlights.bgl


There's no Runway6 at ATH so no idea where these guys came from.
Delete them & please let me know if that fixes it for you?
Post
 maggussje (Mon Aug 14, 2017 2:08 am)

Posts: 16
george[flytampa] wrote:
I spotted a potential problem.

There are two rogue files in the patch.
Rwy06Rapprlights.bgl
Rwy06Lapprlights.bgl


There's no Runway6 at ATH so no idea where these guys came from.
Delete them & please let me know if that fixes it for you?


George,

Thank you very much for looking into this again. Here are my thoughts and findings:
  • I think that the files Rwy06* are just mislabeled. Leaving them enabled actually give you the approach lights for Rwy03L and R at LGAV--well, and CTD ;)
  • Renaming them to Rwy03* doesn't help with the CTD, but I didn't expect that anyway
  • Disabling the Rwy06* files while leaving the Rwy21* enabled seems to have improved the situation, after 10+ minutes I didn't get a CTD
The conclusion I draw from these points is that the problem originates in the--also mislabeled--Rwy06* files.

What do you think?
Post
 george[flytampa] (Mon Aug 14, 2017 3:09 am)

Site Admin | Posts: 3038 | Location: Southampton, UK
maggussje wrote:
george[flytampa] wrote:
I spotted a potential problem.

There are two rogue files in the patch.
Rwy06Rapprlights.bgl
Rwy06Lapprlights.bgl


There's no Runway6 at ATH so no idea where these guys came from.
Delete them & please let me know if that fixes it for you?


George,

Thank you very much for looking into this again. Here are my thoughts and findings:
  • I think that the files Rwy06* are just mislabeled. Leaving them enabled actually give you the approach lights for Rwy03L and R at LGAV--well, and CTD ;)
  • Renaming them to Rwy03* doesn't help with the CTD, but I didn't expect that anyway
  • Disabling the Rwy06* files while leaving the Rwy21* enabled seems to have improved the situation, after 10+ minutes I didn't get a CTD
The conclusion I draw from these points is that the problem originates in the--also mislabeled--Rwy06* files.

What do you think?


Yes, I think they might be the problem. Oddly, they don't crash my system.
I'll ask for the patch to be updated.