1 hour ago, Ray Proudfoot said:

I've just had my first flight in Concorde (LPPT-GCLP) and it was fine. As long as you're running v5 it's happy.

I'll try downgrading the Client in case I still get lockups. I had some after v5.4, but I dismissed it, thinking I was just too greedy with my settings.

1 hour ago, Ray Proudfoot said:

Do you have any aircraft parking in buildings? I found that trying to use v3 AFX files (for extra parking positions) with v5 and that was the result. So I gave up and stayed with v5 AFX ones.

Nope, but I extended the method you described once: I didn't only copy the APX*.bgl files, but also the CVX*.bgl (airport backgrounds) and OBX*.bgl (bulidings and other objects) from my P3Dv4 installation, and pasted them into v5. Except for an AFCAD I did for v5 (which I had to adapt and recompile for the v4 scenery), I haven't found yet any aircraft inside buildings or any other showstoppers.

38 minutes ago, Luis Hernandez said:

I'll try downgrading the Client in case I still get lockups. I had some after v5.4, but I dismissed it, thinking I was just too greedy with my settings.

Inflight lockups? If so and you’re using AIG Ai then that’s the problem I was getting. Reverting to v5.3HF2 fixed them.

1 hour ago, Ray Proudfoot said:

Inflight lockups? If so and you’re using AIG Ai then that’s the problem I was getting.

Using their BGL flightplans, right? If so, I'll give 5.3 a try.

20 minutes ago, Luis Hernandez said:

Using their BGL flightplans, right? If so, I'll give 5.3 a try.

Yes, v5.3HF2 specifically. I was able to prove beyond all doubt 5.4 was responsible.

39 minutes ago, Ray Proudfoot said:

Yes, v5.3HF2 specifically. I was able to prove beyond all doubt 5.4 was responsible.

I use v5.4 and have about 150 AI traffic BGLs, yet I've had no issues like you describe.

I wouldn't blame v5.4, but instead would blame some complex aircraft or addon you're using that isn't compatible with v5.4.

Dave

31 minutes ago, dave2013 said:

I use v5.4 and have about 150 AI traffic BGLs, yet I've had no issues like you describe.

I wouldn't blame v5.4, but instead would blame some complex aircraft or addon you're using that isn't compatible with v5.4.

Dave

I have considerably more than 150 BGLs. It’s not any of my aircraft. I flew the same ones on my old computer running 5.3HF2 for ages and no lockups. The lockups didn’t happen on my new one until v5,4 was installed.

Addons are the same as on old computer. Trial and error confirmed 5.4 was the problem for me. And given LM changed things relating to flight planning that’s why I’m sure it’s the problem.

7 minutes ago, Ray Proudfoot said:

Trial and error confirmed 5.4 was the problem for me. And given LM changed things relating to flight planning that’s why I’m sure it’s the problem.

I'm not saying that you're wrong.  Clearly, switching back to v5.3 worked for you, but it's also evident that it's something you specifically are using, like a bad AI traffic BGL, that caused the problem.

IMO it would have been better, although somewhat tedious to be sure, to track down the offending BGL.  Finding the bad traffic BGL could also help others who could either avoid using it, or someone could try to fix it.

Dave

17 minutes ago, dave2013 said:

IMO it would have been better, although somewhat tedious to be sure, to track down the offending BGL.

It wasn’t just one. The lockups happened in Finland, Australia, England, Netherlands and Sardinia. Try finding the offending BGLs in that lot. Impossible. It’s not as though 5.4 has ground-breaking new features.

3 hours ago, dave2013 said:

I use v5.4 and have about 150 AI traffic BGLs, yet I've had no issues like you describe.

I wouldn't blame v5.4, but instead would blame some complex aircraft or addon you're using that isn't compatible with v5.4.

Dave

No problems whatsoever with 5.4.  I absolutely love this edition of P3d.  If I had a choice between 5.4 and AIG, I would dump AIG in the blink of an eye.

Edited January 3, 20242 yr by spilok

1 hour ago, Ray Proudfoot said:

It wasn’t just one. The lockups happened in Finland, Australia, England, Netherlands and Sardinia. Try finding the offending BGLs in that lot. Impossible. It’s not as though 5.4 has ground-breaking new features.

True Ray, but you are blaming V5.4 when we know ( suspect ? ) that a bad BGL in AIG that is/was to blame. Maybe V5.3 handles such ( less than perfect ) BGLs differently ?

3 hours ago, Ray Proudfoot said:

I was able to prove beyond all doubt 5.4 was responsible.

Hmm.......not too sure I'd agree fully with that. I understood that you concluded that a 'faulty' AI BGL was responsible ?

2 hours ago, Ray Proudfoot said:

Trial and error confirmed 5.4 was the problem for me.

Using V5.4 with a bad BGL is/was the problem for you. Finding a version of a program that accepts faulty data and then stating that a version of the program that complains about same faulty data is responsible for crashes/pauses/bad behaviour/problems is, at the very least, somewhat disingenuous towards V5.4.

10 minutes ago, Sparkrite said:

True Ray, but you are blaming V5.4 when we know ( suspect ? ) that a bad BGL in AIG that is/was to blame. Maybe V5.3 handles such ( less than perfect ) BGLs differently ?

The BGLs were unchanged. They work fine in 5.3HF2. The only thing that changed was a new version of P3D. We know LM don’t enter into discussion about problems users have with their software so whatever the cause it’s never going to be discovered.

I don’t know why you’re having a go at me for pointing the finger at v5.4. What does it matter to anyone else what the problem was and how I resolved it?

8 minutes ago, Ray Proudfoot said:

I don’t know why you’re having a go at me for pointing the finger at v5.4.

Because based purely on what you have said about faulty BGL(s) I don't agree that you have proven that V5.4 is, beyond any doubt, fully to blame.

12 minutes ago, Ray Proudfoot said:

What does it matter to anyone else what the problem was and how I resolved it?

Seriously?

14 pages of a thread started by yourself, in a forum that I thought was setup to discuss and help fellow simmers with, among other things, any problems they may have with their sim prg. and you ask such a question?

@Sparkrite, if 5.4 isn’t to blame then please tell me what is? An AIG BGL that opens with AIFP and looks fine doesn’t show anything untoward.

I make one change and haven’t had a reoccurrence of the problem since despite flying into Schiphol where the problem occurred several times. What conclusion would you draw from that?

8 hours ago, Sparkrite said:

Seriously?

14 pages of a thread started by yourself, in a forum that I thought was setup to discuss and help fellow simmers with, among other things, any problems they may have with their sim prg. and you ask such a question?

Looking back your only contribution was back on page 2 where you also expressed frustration about the OS. Turns out it is nothing to do with that. I believe I’ve found the cause by trial and error.

https://www.avsim.com/forums/topic/640158-p3d-v54-random-lockups-driving-me-mad/?do=findComment&comment=5041252

I believe it is because of changes to airports in 5.4 and a conflict with some BGLs. The long lockups which mostly cleared could be down to the associated aircraft flying out of my 80nm bubble. That seems the most logical reason to me. An airport that exists in 5.3 but doesn’t in 5.4.

Ray, With alI due respect, I don't think you can say at this time that 5.4 is to blame. Your testing has only shown that there is an incompatibility between 5.4 and one or more of the AIG bgls on your system. Whether some bgl or 5.4 has an error in it has yet to be determined. To keep the drama rolling in this thread you will have to find which one (or more) are the incompatible bgls with 5.4 by systematically removing half the bgls and testing again until they are discovered. Then the hard part starts of determining the cause of the incompatibility.

😁 I'm routing for you and putting on another pot of coffee.

Ted

1 hour ago, Ted Striker said:

Ray, With alI due respect, I don't think you can say at this time that 5.4 is to blame. Your testing has only shown that there is an incompatibility between 5.4 and one or more of the AIG bgls on your system. Whether some bgl or 5.4 has an error in it has yet to be determined. To keep the drama rolling in this thread you will have to find which one (or more) are the incompatible bgls with 5.4 by systematically removing half the bgls and testing again until they are discovered. Then the hard part starts of determining the cause of the incompatibility.

😁 I'm routing for you and putting on another pot of coffee.

Ted

Ted, no, it’s not solely 5.4 causing the problem. If it was a lot more people would be affected. It’s a combination of 5.4 and an unknown number of AIG BGLs causing it. But when you have over 1300 BGLs how do you identify the ones causing the problem? It’s impossible. AIG suggested switching to AIGFP files but you cannot edit those so that’s a non-starter.

With no support from LM it’s impossible to resolve the problem. The simplest solution was to revert to the setup I had on my old computer. That’s what I’ve done and further flights over the last couple of days have been problem free.

If anyone has a list of the changes made to 5.4 I’d be grateful.